Back to blog
Crypto Basics

What is an Atomic Swap? - A Comprehensive Guide

Discover what an Atomic Swap is and how it simplifies decentralized crypto trading with this comprehensive guide.
Marcus K
8 Minutes
Want Smarter Crypto Picks—Free?
See unbiased Token Metrics Ratings for BTC, ETH, and top alts.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
 No credit card | 1-click unsubscribe

In the ever-evolving world of cryptocurrencies, new technologies emerge consistently, each playing its part in transforming the landscape. 

One such technology that is currently gaining attention is Atomic Swaps, a concept that promises to improve the way we trade cryptocurrencies.

This article aims to provide a comprehensive understanding of atomic swaps, exploring their definition, working principles, benefits, and potential applications.

What are Atomic Swaps?

Atomic Swaps, also known as atomic cross-chain trading, are smart contracts technology that enables exchange between one cryptocurrency for another without using centralized intermediaries, like exchanges. 

These swaps are 'atomic' because they are indivisible, meaning that the swap either happens entirely or not at all, ensuring that all parties maintain the integrity of their funds during the transaction.

How Do Atomic Swaps Work?

To understand how Atomic Swaps work, it's important to first comprehend two key concepts: Hash Time-Locked Contracts (HTLCs) and Time-Locked Contracts.

Hash Time-Locked Contracts (HTLCs): This is a class of payments that use hash-locks and time-locks that require the receiver of a payment to acknowledge receiving the payment prior to a deadline by generating cryptographic proof of payment or forfeit the ability to claim the payment, returning it to the payer.

Time-Locked Contracts: These contracts, as the name suggests, lock a transaction for a specific period. It's an important aspect of Atomic Swaps as it ensures that the transaction happens as agreed by both parties.

With these fundamentals in place, an Atomic Swap occurs in several steps:

Transaction Proposal: The initiator proposes a trade to the participant, outlining the details of the transaction, including the amount and type of cryptocurrency to be swapped.

HTLC Setup: The initiator creates a HTLC and sends the proposed cryptocurrency. The HTLC generates a hash and a cryptographic puzzle, which the participant needs to solve to access the funds.

Participant Verification: The participant checks the transaction, verifies the details, and creates their own HTLC.

Solution Sharing: The participant solves the initiator's cryptographic puzzle, thus sharing the solution with the initiator. In doing so, they reveal their own puzzle solution, which the initiator can now solve.

Completion of Swap: The initiator uses the participant's puzzle solution to unlock the participant's HTLC, receiving their funds. 

Simultaneously, the participant unlocks the initiator's HTLC using the initially shared puzzle solution. 

If either party cannot solve the puzzle within the time-lock period, the funds are returned to their original owner.

Atomic Swap - Step by Step Process

To carry out an atomic swap, both parties must agree on the exchange rate and amounts to trade. Once these details are agreed upon, the process unfolds in the following steps:

Creation of Contract: The first party (Alice) initiates the process by creating a contract, which is essentially a program that specifies the terms of the transaction, including the amount of cryptocurrency to be traded and a unique cryptographic hash value.

Contract Locking: Alice then locks her funds into this contract. She's the only one who can unlock the funds using her private key, but she also sets a time limit for the transaction to be completed.

Contract Address Sharing: Alice shares the contract address with the second party (Bob). Bob verifies the contract address and the locked funds.

Contract Duplication: Bob then creates a similar contract on his blockchain, using the same hash value as Alice’s contract. Bob locks his funds in this contract.

Transaction Completion: Alice can now unlock Bob's funds using her private key, thus validating the swap. Once Bob sees that his funds have been withdrawn, he can unlock Alice's contract and take the cryptocurrency. 

If either of them fails to unlock the funds within the time limit, the trade is automatically canceled, and the funds return to their original owners.

Benefits of Atomic Swaps

Atomic Swaps offer numerous benefits, including:

  • Decentralization: Atomic Swaps remove the need for a central authority or third-party service like a cryptocurrency exchange, thus enforcing the true essence of blockchain - decentralization.
  • Reduced Costs: Since no intermediaries are involved, Atomic Swaps can help cut down on transaction fees.
  • Increased Privacy: Unlike traditional exchanges that require Know Your Customer (KYC) procedures, Atomic Swaps can be done directly between users, enhancing privacy.
  • Interoperability: Atomic Swaps facilitate cross-chain transactions, fostering interoperability between different blockchains.

Limitations and Challenges

Despite its promising benefits, Atomic Swaps also have their limitations and face several challenges:

  • Liquidity Issues: As Atomic Swaps are peer-to-peer, there may be problems finding a match for the specific swap you want to make, leading to liquidity issues.
  • Technical Complexity: The concept and execution of Atomic Swaps can be technically challenging for many users.
  • Blockchain Compatibility: Not all blockchains are compatible with Atomic Swaps, limiting the range of cryptocurrencies that can be swapped.

Can Atomic Swaps be Tracked?

As atomic swaps happen on the blockchain, all transactions are transparent and can be tracked. However, the identities of the trading parties remain private unless they choose to disclose them. 

The nature of the transaction, whether it's an atomic swap or a regular transaction, can be understood from the way it's processed on the blockchain.

Atomic Swap vs Bridge

While atomic swaps and bridges are both technologies that enable interoperability between different blockchains, they serve different purposes:

Atomic Swaps: As explained above, atomic swaps allow users to directly and securely exchange one type of cryptocurrency for another, without needing an intermediary like an exchange.

Bridges: These are protocols that connect two different blockchains, allowing a token from one blockchain to be used on another and vice versa.

For instance, a user can send Ethereum tokens to a bridge, which then locks up the Ethereum and mints a corresponding amount of a new token on a different blockchain. 

This newly minted token can then be used on the second blockchain as if it were Ethereum. When the user is done, they can send back the token to the bridge, which will burn it and unlock the original Ethereum.

In summary, while atomic swaps focus on exchanging different cryptocurrencies directly, bridges aim to make a single cryptocurrency usable across different blockchains. Both technologies are vital in promoting interoperability in the crypto space.

The Future of Atomic Swaps

Atomic Swaps hold immense potential. They can revolutionize the way we trade cryptocurrencies, making the process more private, secure, and decentralized. 

While the technology is still in its early stages, the active development and growing interest from the blockchain community signal a promising future.

Frequently Asked Questions

Q1. Are Atomic Swaps safe?

Atomic Swaps are considered safe due to the nature of the technology itself. Since the transactions are 'atomic,' they either occur in full or not at all, thus ensuring safety. However, like all technologies, users should do their research and ensure they are dealing with trusted parties.

Q2 Can I perform an Atomic Swap with any cryptocurrency?

No, not all cryptocurrencies currently support Atomic Swaps. Both cryptocurrencies involved in the swap need to support the same hash function and have the ability to create time-locked contracts. 

Bitcoin and cryptocurrencies that forked from Bitcoin's code (like Litecoin) are among those that can engage in Atomic Swaps.

Q3. How long do Atomic Swaps take?

The duration of an Atomic Swap can vary based on a few factors such as network congestion and the time-lock duration set for the transaction. Some swaps could occur in minutes, while others might take hours.

Q4. Do I need to be technically skilled to perform Atomic Swaps?

While the underlying technology of Atomic Swaps can be complex, various platforms have simplified the process. Using Atomic Swap-enabled exchanges, the user interface can guide a user through the process.

Q5. Can Atomic Swaps be reversed?

Once completed, Atomic Swaps cannot be reversed. However, if the swap is not completed within the specified time, the locked funds will be returned to the respective owners.

Q6. Is it necessary to have a wallet to perform Atomic Swaps?

Yes, since Atomic Swaps involve a direct, peer-to-peer exchange of cryptocurrencies, both parties need to have their own wallets for the respective cryptocurrencies.

Q7. What are some of the potential use cases for Atomic Swaps?

Apart from trading, Atomic Swaps can also be used in multi-signature transactions, payment channels, and cross-chain payment routing.

Q8. How does an Atomic Swap differ from trading on a regular crypto exchange?

Traditional crypto exchanges require depositing funds into an exchange wallet, and trades are facilitated by the exchange itself, acting as an intermediary. 

Atomic Swaps, on the other hand, allow users to keep control of their funds in their own wallets until the moment the trade happens, eliminating the need for intermediaries.

Conclusion

Atomic Swaps are transforming the crypto trading landscape by providing a decentralized, secure, and efficient way to exchange cryptocurrencies. 

By understanding and leveraging this technology, crypto enthusiasts can participate more fully in the blockchain revolution.

Remember, while the promise of Atomic Swaps is compelling, it's always crucial to conduct your own research and consider your risk tolerance before diving into any new crypto technology. Stay informed, stay secure, and stay ahead with Token Metrics.

Disclaimer

The information provided on this website does not constitute investment advice, financial advice, trading advice, or any other sort of advice and you should not treat any of the website's content as such.

Token Metrics does not recommend that any cryptocurrency should be bought, sold, or held by you. Do conduct your own due diligence and consult your financial advisor before making any investment decisions.

Build Smarter Crypto Apps &
AI Agents in Minutes, Not Months
Real-time prices, trading signals, and on-chain insights all from one powerful API.
Grab a Free API Key
About Token Metrics
Token Metrics: AI-powered crypto research and ratings platform. We help investors make smarter decisions with unbiased Token Metrics Ratings, on-chain analytics, and editor-curated “Top 10” guides. Our platform distills thousands of data points into clear scores, trends, and alerts you can act on.
30 Employees
analysts, data scientists, and crypto engineers
Daily Briefings
concise market insights and “Top Picks”
Transparent & Compliant
Sponsored ≠ Ratings; research remains independent
Want Smarter Crypto Picks—Free?
See unbiased Token Metrics Ratings for BTC, ETH, and top alts.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
 No credit card | 1-click unsubscribe
Token Metrics Team
Token Metrics Team

Recent Posts

Research

Support and Resistance API: Auto-Calculate Smart Levels for Better Trades

Token Metrics Team
4

Most traders still draw lines by hand in TradingView. The support and resistance API from Token Metrics auto-calculates clean support and resistance levels from one request, so your dashboard, bot, or alerts can react instantly. In minutes, you’ll call /v2/resistance-support, render actionable levels for any token, and wire them into stops, targets, or notifications. Start by grabbing your key on Get API Key, then Run Hello-TM and Clone a Template to ship a production-ready feature fast.

What You’ll Build in 2 Minutes

A minimal script that fetches Support/Resistance via /v2/resistance-support for a symbol (e.g., BTC, SOL).

  • A one-liner curl to smoke-test your key.
  • A UI pattern to display nearest support, nearest resistance, level strength, and last updated time.

Next Endpoints to add

  • /v2/trading-signals (entries/exits)
  • /v2/hourly-trading-signals (intraday updates)
  • /v2/tm-grade (single-score context)
  • /v2/quantmetrics (risk/return framing)

Why This Matters

Precision beats guesswork. Hand-drawn lines are subjective and slow. The support and resistance API standardizes levels across assets and timeframes, enabling deterministic stops and take-profits your users (and bots) can trust.

Production-ready by design. A simple REST shape, predictable latency, and clear semantics let you add levels to token pages, automate SL/TP alerts, and build rule-based execution with minimal glue code.

Where to Find

Need the Support and Resistance data? The cURL request for it is in the top right of the API Reference for quick access.

👉 Keep momentum: Get API Key • Run Hello-TM • Clone a Template

How It Works (Under the Hood)

The Support/Resistance endpoint analyzes recent price structure to produce discrete levels above and below current price, along with strength indicators you can use for priority and styling. Query /v2/resistance-support?symbol=<ASSET>&timeframe=<HORIZON> to receive arrays of level objects and timestamps.

Polling vs webhooks. For dashboards, short-TTL caching and batched fetches keep pages snappy. For bots and alerts, use queued jobs or webhooks (where applicable) to avoid noisy, bursty polling—especially around market opens and major events.

Production Checklist

  • Rate limits: Respect plan caps; add client-side throttling.
  • Retries/backoff: Exponential backoff with jitter for 429/5xx; log failures.
  • Idempotency: Make alerting and order logic idempotent to prevent duplicates.
  • Caching: Memory/Redis/KV with short TTLs; pre-warm top symbols.
  • Batching: Fetch multiple assets per cycle; parallelize within rate limits.
  • Threshold logic: Add %-of-price buffers (e.g., alert at 0.3–0.5% from level).
  • Error catalog: Map common 4xx/5xx to actionable user guidance; keep request IDs.
  • Observability: Track p95/p99; measure alert precision (touch vs approach).
  • Security: Store API keys in a secrets manager; rotate regularly.

Use Cases & Patterns

  • Bot Builder (Headless): Use nearest support for stop placement and nearest resistance for profit targets. Combine with /v2/trading-signals for entries/exits and size via Quantmetrics (volatility, drawdown).
  • Dashboard Builder (Product): Add a Levels widget to token pages; badge strength (e.g., High/Med/Low) and show last touch time. Color the price region (below support, between levels, above resistance) for instant context.
  • Screener Maker (Lightweight Tools): “Close to level” sort: highlight tokens within X% of a strong level. Toggle alerts for approach vs breakout events.
  • Risk Management: Create policy rules like “no new long if price is within 0.2% of strong resistance.” Export daily level snapshots for audit/compliance.

Next Steps

  • Get API Key — generate a key and start free.
  • Run Hello-TM — verify your first successful call.
  • Clone a Template — deploy a levels panel or alerts bot today.
  • Watch the demo: Compare plans: Scale confidently with API plans.

FAQs

1) What does the Support & Resistance API return?

A JSON payload with arrays of support and resistance levels for a symbol (and optional timeframe), each with a price and strength indicator, plus an update timestamp.

2) How timely are the levels? What are the latency/SLOs?

The endpoint targets predictable latency suitable for dashboards and alerts. Use short-TTL caching for UIs, and queued jobs or webhooks for alerting to smooth traffic.

3) How do I trigger alerts or trades from levels?

Common patterns: alert when price is within X% of a level, touches a level, or breaks beyond with confirmation. Always make downstream actions idempotent and respect rate limits.

4) Can I combine levels with other endpoints?

Yes—pair with /v2/trading-signals for timing, /v2/tm-grade for quality context, and /v2/quantmetrics for risk sizing. This yields a complete decide-plan-execute loop.

5) Which timeframe should I use?

Intraday bots prefer shorter horizons; swing/position dashboards use daily or higher-timeframe levels. Offer a timeframe toggle and cache results per setting.

6) Do you provide SDKs or examples?

Use the REST snippets above (JS/Python). The docs include quickstarts, Postman collections, and templates—start with Run Hello-TM.

7) Pricing, limits, and enterprise SLAs?

Begin free and scale as you grow. See API plans for rate limits and enterprise SLA options.

Disclaimer

This content is for educational purposes only and does not constitute financial advice. Always conduct your own research before making any trading decisions.

Research

Quantmetrics API: Measure Risk & Reward in One Call

Token Metrics Team
5

Most traders see price—quants see probabilities. The Quantmetrics API turns raw performance into risk-adjusted stats like Sharpe, Sortino, volatility, drawdown, and CAGR so you can compare tokens objectively and build smarter bots and dashboards. In minutes, you’ll query /v2/quantmetrics, render a clear performance snapshot, and ship a feature that customers trust. Start by grabbing your key at Get API Key, Run Hello-TM to verify your first call, then Clone a Template to go live fast.

What You’ll Build in 2 Minutes

  • A minimal script that fetches Quantmetrics for a token via /v2/quantmetrics (e.g., BTC, ETH, SOL).
  • A smoke-test curl you can paste into your terminal.
  • A UI pattern that displays Sharpe, Sortino, volatility, max drawdown, CAGR, and lookback window.

Next Endpoints to Add

  • /v2/tm-grade (one-score signal)
  • /v2/trading-signals
  • /v2/hourly-trading-signals (timing)
  • /v2/resistance-support (risk placement)
  • /v2/price-prediction (scenario planning)

Why This Matters

Risk-adjusted truth beats hype. Price alone hides tail risk and whipsaws. Quantmetrics compresses edge, risk, and consistency into metrics that travel across assets and timeframes—so you can rank universes, size positions, and communicate performance like a professional.

Built for dev speed

A clean REST schema, predictable latency, and easy auth mean you can plug Sharpe/Sortino into bots, dashboards, and screeners without maintaining your own analytics pipeline. Pair with caching and batching to serve fast pages at scale.

Where to Find

The Quant Metrics cURL request is located in the top right of the API Reference, allowing you to easily integrate it with your application.

Build Smarter Crypto Apps & AI Agents with Token Metrics

Token Metrics provides real-time prices, trading signals, and on-chain insights all from one powerful API. Grab a Free API Key

How It Works (Under the Hood)

Quantmetrics computes risk-adjusted performance over a chosen lookback (e.g., 30d, 90d, 1y). You’ll receive a JSON snapshot with core statistics:

  • Sharpe ratio: excess return per unit of total volatility.
  • Sortino ratio: penalizes downside volatility more than upside.
  • Volatility: standard deviation of returns over the window.
  • Max drawdown: worst peak-to-trough decline.
  • CAGR / performance snapshot: geometric growth rate and best/worst periods.

Call /v2/quantmetrics?symbol=<ASSET>&window=<LOOKBACK> to fetch the current snapshot. For dashboards spanning many tokens, batch symbols and apply short-TTL caching. If you generate alerts (e.g., “Sharpe crossed 1.5”), run a scheduled job and queue notifications to avoid bursty polling.

Production Checklist

  • Rate limits: Understand your tier caps; add client-side throttling and queues.
  • Retries & backoff: Exponential backoff with jitter; treat 429/5xx as transient.
  • Idempotency: Prevent duplicate downstream actions on retried jobs.
  • Caching: Memory/Redis/KV with short TTLs; pre-warm popular symbols and windows.
  • Batching: Fetch multiple symbols per cycle; parallelize carefully within limits.
  • Error catalog: Map 4xx/5xx to clear remediation; log request IDs for tracing.
  • Observability: Track p95/p99 latency and error rates; alert on drift.
  • Security: Store API keys in secrets managers; rotate regularly.

Use Cases & Patterns

  • Bot Builder (Headless): Gate entries by Sharpe ≥ threshold and drawdown ≤ limit, then trigger with /v2/trading-signals; size by inverse volatility.
  • Dashboard Builder (Product): Add a Quantmetrics panel to token pages; allow switching lookbacks (30d/90d/1y) and export CSV.
  • Screener Maker (Lightweight Tools): Top-N by Sortino with filters for volatility and sector; add alert toggles when thresholds cross.
  • Allocator/PM Tools: Blend CAGR, Sharpe, drawdown into a composite score to rank reallocations; show methodology for trust.
  • Research/Reporting: Weekly digest of tokens with Sharpe ↑, drawdown ↓, and volatility ↓.

Next Steps

  • Get API Key — start free and generate a key in seconds.
  • Run Hello-TM — verify your first successful call.
  • Clone a Template — deploy a screener or dashboard today.
  • Watch the demo: VIDEO_URL_HERE
  • Compare plans: Scale with API plans.

FAQs

1) What does the Quantmetrics API return?

A JSON snapshot of risk-adjusted metrics (e.g., Sharpe, Sortino, volatility, max drawdown, CAGR) for a symbol and lookback window—ideal for ranking, sizing, and dashboards.

2) How fresh are the stats? What about latency/SLOs?

Responses are engineered for predictable latency. For heavy UI usage, add short-TTL caching and batch requests; for alerts, use scheduled jobs or webhooks where available.

3) Can I use Quantmetrics to size positions in a live bot?

Yes—many quants size inversely to volatility or require Sharpe ≥ X to trade. Always backtest and paper-trade before going live; past results are illustrative, not guarantees.

4) Which lookback window should I choose?

Short windows (30–90d) adapt faster but are noisier; longer windows (6–12m) are steadier but slower to react. Offer users a toggle and cache each window.

5) Do you provide SDKs or examples?

REST is straightforward (JS/Python above). Docs include quickstarts, Postman collections, and templates—start with Run Hello-TM.

6) Polling vs webhooks for quant alerts?

Dashboards usually use cached polling. For threshold alerts (e.g., Sharpe crosses 1.0), run scheduled jobs and queue notifications to keep usage smooth and idempotent.

7) Pricing, limits, and enterprise SLAs?

Begin free and scale up. See API plans for rate limits and enterprise SLA options.

Disclaimer

All information provided in this blog is for educational purposes only. It is not intended as financial advice. Users should perform their own research and consult with licensed professionals before making any investment or trading decisions.

Research

Crypto Trading Signals API: Put Bullish/Bearish Calls Right in Your App

Token Metrics Team
4

Timing makes or breaks every trade. The crypto trading signals API from Token Metrics lets you surface bullish and bearish calls directly in your product—no spreadsheet wrangling, no chart gymnastics. In this guide, you’ll hit the /v2/trading-signals endpoint, display actionable signals on a token (e.g., SOL, BTC, ETH), and ship a conversion-ready feature for bots, dashboards, or Discord. Start by creating a key on Get API Key, then Run Hello-TM and Clone a Template to go live fast.

What You’ll Build in 2 Minutes

  • A minimal script that fetches Trading Signals via /v2/trading-signals for one symbol (e.g., SOL).
  • A copy-paste curl to smoke-test your key.
  • A UI pattern to render signal, confidence/score, and timestamp in your dashboard or bot.

Endpoints to add next

  • /v2/hourly-trading-signals (intraday updates)
  • /v2/resistance-support (risk placement)
  • /v2/tm-grade (one-score view)
  • /v2/quantmetrics (risk/return context)

Why This Matters

Action over analysis paralysis. Traders don’t need more lines on a chart—they need an opinionated call they can automate. The trading signals API compresses technical momentum and regime reads into Bullish/Bearish events you can rank, alert on, and route into strategies.

Built for dev speed and reliability. A clean schema, predictable performance, and straightforward auth make it easy to wire signals into bots, dashboards, and community tools. Pair with short-TTL caching or webhooks to minimize polling and keep latency low.

Where to Find

You can find the cURL request for Crypto Trading Signals in the top right corner of the API Reference. Use it to access the latest signals!

Live Demo & Templates

  • Trading Bot Starter: Use Bullish/Bearish calls to trigger paper trades; add take-profit/stop rules with Support/Resistance.
  • Dashboard Signal Panel: Show the latest call, confidence, and last-updated time; add a history table for context.
  • Discord/Telegram Alerts: Post signal changes to a channel with a link back to your app.

How It Works (Under the Hood)

Trading Signals distill model evidence (e.g., momentum regimes and pattern detections) into Bullish or Bearish calls with metadata such as confidence/score and timestamp. You request /v2/trading-signals?symbol=<ASSET> and render the most recent event, or a small history, in your UI.

For intraday workflows, use /v2/hourly-trading-signals to update positions or alerts more frequently. Dashboards typically use short-TTL caching or batched fetches; headless bots lean on webhooks, queues, or short polling with backoff to avoid spiky API usage.

Production Checklist

  • Rate limits: Know your tier caps; add client-side throttling and queues.
  • Retries/backoff: Exponential backoff with jitter; treat 429/5xx as transient.
  • Idempotency: Guard downstream actions (don’t double-trade on retries).
  • Caching: Memory/Redis/KV with short TTLs for reads; pre-warm popular symbols.
  • Webhooks & jobs: Prefer webhooks or scheduled workers for signal change alerts.
  • Pagination/Bulk: Batch symbols; parallelize with care; respect limits.
  • Error catalog: Map common 4xx/5xx to clear fixes; log request IDs.
  • Observability: Track p95/p99 latency, error rate, and alert delivery success.
  • Security: Keep keys in a secrets manager; rotate regularly.

Use Cases & Patterns

  • Bot Builder (Headless): Route Bullish into candidate entries; confirm with /v2/resistance-support for risk and TM Grade for quality.
  • Dashboard Builder (Product): Add a “Signals” module per token; color-code state and show history for credibility.
  • Screener Maker (Lightweight Tools): Filter lists by Bullish state; sort by confidence/score; add alert toggles.
  • Community/Discord: Post signal changes with links to token pages; throttle to avoid noise.
  • Allocator/PM Tools: Track signal hit rates by sector/timeframe to inform position sizing (paper-trade first).

Next Steps

  1. Get API Key — create a key and start free.
  2. Run Hello-TM — confirm your first successful call.
  3. Clone a Template — deploy a bot, dashboard, or alerting tool today.

FAQs

1) What does the Trading Signals API return?

A JSON payload with the latest Bullish/Bearish call for a symbol, typically including a confidence/score and generated_at timestamp. You can render the latest call or a recent history for context.

2) Is it real-time? What about latency/SLOs?

Signals are designed for timely, programmatic use with predictable latency. For faster cycles, use /v2/hourly-trading-signals. Add caching and queues/webhooks to reduce round-trips.

3) Can I use the signals in a live trading bot?

Yes—many developers do. A common pattern is: Signals → candidate entry, Support/Resistance → stop/targets, Quantmetrics → risk sizing. Always backtest and paper-trade before going live.

4) How accurate are the signals?

Backtests are illustrative, not guarantees. Treat signals as one input in a broader framework with risk controls. Evaluate hit rates and drawdowns on your universe/timeframe.

5) Do you provide SDKs and examples?

You can integrate via REST using JavaScript and Python snippets above. The docs include quickstarts, Postman collections, and templates—start with Run Hello-TM.

6) Polling vs webhooks for alerts?

Dashboards often use cached polling. For bots/alerts, prefer webhooks or scheduled jobs and keep retries idempotent to avoid duplicate trades or messages.

7) Pricing, limits, and enterprise SLAs?

Begin free and scale as you grow. See API plans for allowances; enterprise SLAs and support are available.

Choose from Platinum, Gold, and Silver packages
Reach with 25–30% open rates and 0.5–1% CTR
Craft your own custom ad—from banners to tailored copy
Perfect for Crypto Exchanges, SaaS Tools, DeFi, and AI Products