API

Keyless, read-only, and reproducible

No account and no key — none is accepted. Every response is derived from contract storage, so you can check any number against an RPC endpoint yourself.

Base URL

https://aquifer.markets

The API holds no funds, signs nothing and broadcasts nothing. It answers what a trade would be worth; making the trade is entirely yours.

GET/api/v1/quotePrice an order across every venue

Parameters

tokenIn
Ticker or address you are paying with, e.g. USDG
tokenOut
Ticker or address you want, e.g. SPY
amountIn
Decimal amount of tokenIn, e.g. 250000

The best single-venue fill, a per-venue breakdown, a split route when one beats it, a depth ladder, and the pools that could not answer with the reason why.

GET/api/v1/boardThe equity board

No parameters.

One row per instrument, with the mid computed from that instrument's deepest pool read at the current block.

GET/api/v1/poolsPools discovered for a token

Parameters

token
Ticker or address, e.g. SPY

Every pool the indexer knows for the token, across all venues and both pool families.

GET/api/v1/venuesVenue coverage

No parameters.

Each venue, its pool family, and its share of the equity book.

GET/api/v1/healthChain head and RPC latency

No parameters.

Block number and how long the node took to answer.

Reading a quote

Fields worth understanding before you rely on one

best.amountOut
Output from the single best venue, in token units.
best.priceImpactBps
How far the fill sits below that pool's mid, in basis points.
best.crossedTicks
Initialized ticks the order consumed. Zero means it fit inside one range.
best.capped
True when the pool ran past the loaded depth window — treat amountOut as a floor.
best.hooked
True for a Uniswap v4 pool with a hook attached; the quote is indicative.
split.improvementBps
What splitting gains over the best single venue. Absent when splitting does not help.
depth[]
Output and impact at a ladder of sizes, with the winning venue at each.
excluded[]
Pools left out, and why. A pool that cannot answer is never estimated.

Rate limits and stability

Responses are cached for a few seconds and served stale rather than failing when an upstream node is slow. This is unaudited software on a young chain: treat the API as a research tool, not as infrastructure to route real size against unverified.