How is the API used in trading and swaps?

Products can read market and blockchain state, compare routes, check transaction status and support operational workflows around swaps from the same integration layer.

Can an operation be checked before it completes?

Yes. Simulate the call, verify balances and allowance, then follow the signed transaction through pending and confirmed states before updating your internal workflow.

Why use a dedicated endpoint for market operations?

It isolates critical flows from shared-resource contention and gives capacity planning a boundary of its own. That matters when a traffic spike cannot be allowed to widen the latency tail.

Which risks matter most under high load?

Timeouts with an unknown outcome, duplicate broadcasts, stale quotes, endpoint lag and missing operational alerts. Each needs an id or a measurable signal beside the operation itself.

Is market data a separate integration?

It uses the same project key and can sit beside blockchain reads in one product workflow. The market-data endpoints expose quotes, candles and fee context; RPC and transaction checks cover the chain side.

For trading and swaps

Market infrastructurefor decisions in motion.

Quotes are only the beginning. Compare routes, verify the transaction and keep watching the chain through the same operating layer.

Explore market data Read the docs

56 ms: Average response
99.99%: Service uptime
100M: API requests a day
4: Checks in one decision

Swap intent

BTC USDT

live routes

RouteYou receiveLatency

edge-017,498.4238 ms

edge-027,502.6358 ms

edge-037,499.8848 ms

tx simulation · allowance · balance · route

Selected path

edge-02

7,502.63

USDT

Edge captured

+4.21 USDT

Market operation

One decision. Four live checks.

The useful answer is not a price in isolation. It is a path from the first quote to a transaction your product can safely follow.

0100 ms

Read the quote

Fresh price and fee context arrive together, with an age you can measure.

GET /quotes

0218 ms

Choose the route

Compare expected output, slippage and response time before committing.

POST /route

0341 ms

Verify the operation

Simulate balances, allowance and execution before asking for a signature.

POST /simulate

0456 ms

Watch the chain

Follow pending, confirmed and reverted states without blind polling.

WS /status

Decision context

A price is useful only while its context is still true.

Bring quote freshness, chain state, transaction status and endpoint health into the same decision envelope.

See the Market Data API

decision envelope

BTC / USDT

Quote age

42 ms

Chain head

#21 882 104

Transaction

pending

Endpoint

healthy

Every field can be logged with the decision id — the operation can be explained later, not merely observed now.

Under load

Market failures rarely announce themselves clearly.

The dangerous failures are plausible answers delivered late, twice or without enough context to trust them.

The signal belongs beside the operation, not in a dashboard found afterwards.

Timeout without outcome

The client stops waiting, but the broadcast may already have reached the network.

Watch · request id + tx hash

Duplicate broadcast

A retry repeats an operation whose first response was lost, not whose first attempt failed.

Control · idempotency key

Stale market state

A valid quote can still be unusable once its block, fee or liquidity context has moved.

Watch · quote age + block

Endpoint lag

A healthy HTTP response can come from a node that is already behind the chain head.

Watch · block lag

Shared or dedicated

The shared endpoint stays right there — it is the easy place to start and to test.

Both run on the same API and the same key, so you can keep part of the traffic on the shared pool and move only the critical part to your own node.

Criterion	Shared RPC	Dedicated nodes
Capacity	Shared pool, scaled by us	Reserved node, yours alone
Noisy neighbours	Fair queue per key	None — single tenant
Rate limits	Per plan, burst-friendly	Whatever the node can serve
Archive	Included	Included, custom retention
Placement	Nearest healthy region	Pinned to your region
Setup	Instant	Provisioned within a day
Best for	Wallets, apps, bursty traffic	Exchanges, indexers, steady load

Capacity

Shared RPC: Shared pool, scaled by us
Dedicated nodes: Reserved node, yours alone

Noisy neighbours

Shared RPC: Fair queue per key
Dedicated nodes: None — single tenant

Rate limits

Shared RPC: Per plan, burst-friendly
Dedicated nodes: Whatever the node can serve

Placement

Shared RPC: Nearest healthy region
Dedicated nodes: Pinned to your region

Setup

Shared RPC: Instant
Dedicated nodes: Provisioned within a day

Best for

Shared RPC: Wallets, apps, bursty traffic
Dedicated nodes: Exchanges, indexers, steady load

See plans Shared RPC endpoints

Questions

What market teams ask

Infrastructure shouldn't be the thing slowing you down.

Free to start. No credit card required.

Get a free endpoint Talk to an expert