GET that needs no API key. The info routes serve all four networks. Transaction history and volume cover evm-mainnet and evm-sepolia.
Every response uses
camelCase field names. Deployment info also repeats each multi-word field it published before under its older snake_case name, such as swap_contract beside swapContract, for older SDKs that still read it. Newer fields, such as unorderedNonceFromBlock, have only the camelCase name. New clients read the camelCase names.Deployment info
The info routes give an integration the addresses, asset identifiers, decimals, delegates, and pricing sources it needs. Withnetwork, a route returns that network’s deployment object directly. Without it, GET /v1/info returns every deployment keyed by runtime (evm, svm) and then chain (mainnet, sepolia, devnet), and GET /v1/info/evm and GET /v1/info/svm return their runtime’s deployments keyed by chain.
GET /v1/info still accepts the deprecated runtime filter, and GET /v1/info/evm and GET /v1/info/svm the deprecated chain filter; Network keys lists their values. Any other query parameter is rejected with 400.
An EVM deployment contains:
An SVM deployment contains:
Each SVM asset gives its
token, mintAddress, decimals, and priceSource, so you can convert on-chain amounts without reading the mint account. Every EVM address and hex ID is lowercase 0x hex, so it matches the same value on the swap routes.
stablecoinDelegateContracts lists the configured delegates followed by the completed, automatically deployed delegates. A deployed delegate whose stablecoin Multiliquid no longer lists is left out. Field names such as lpInfo and lpAdminName keep their released spelling; each refers to a capital provider.
For swap integrations, discovery gives the same tokens with their names, issuers, and kinds, and the pairs each network can swap.
Transaction history
GET /v1/transactions returns canonical EVM economic transactions for one network. Each transaction includes its inclusion data, receipt outcome, decoded top-level call when available, submitted swap bounds, and realized swap or Treasury allowlist activity.
network, chainId, the transactions in descending canonical chain order, nextCursor (null on the last page), and coverage. Each transaction contains:
The interactive reference lists every field of
directCall and activities. directCall.submittedSwapLegs holds the bounds supplied in calldata, as amountInBound and amountOutBound in whole tokens. Realized amounts and fees are in activities; submitted bounds never replace event results. A successful nested swap can have activities without a top-level directCall, and a reverted decoded call can have a directCall without realized activities.
Pagination
Rows use descending keyset order. For the next page, send the same request withcursor set to the previous page’s nextCursor.
The cursor is opaque, and valid only with the network and filters it was issued for; another limit is fine. A cursor sent with another network or other filters answers 400 with code INVALID_REQUEST, details.field cursor, and details.location query, as does a malformed cursor.
Canonicality and precision
Transactions become visible at first inclusion and can be replaced if the chain reorganizes. Asuccess outcome describes receipt execution; it is not a finality indicator.
Token amounts are whole tokens as decimal strings: a submitted leg’s amountInBound and amountOutBound, and a swap activity’s amountIn and amountOut in the tokens of its assetInId and assetOutId, and its fees in the stablecoin the swap charges them in. The decimals come from the RWAs and stablecoin delegates that deployment info lists for the network. An amount whose asset is not listed, such as an RWA no longer listed or an ID that a reverted call submitted, is null, and its asset ID is still given. A transaction’s value and effectiveGasPrice stay in wei, and gasUsed in gas units. Gas values, block positions, nonces, and timestamps are decimal strings, so JSON consumers do not lose integer precision. Addresses, hashes, selectors, and byte-valued asset IDs are lowercase 0x-prefixed hex. A field that does not apply, such as directCall.decodedCall.allowlistWallet on a swap call, is null; each activity carries only the fields of its type.
The endpoint does not infer token symbols, prices, business direction, pending state, or total result counts.
Protocol volume
GET /v1/volume aggregates canonical realized swap legs across one half-open UTC range and returns the protocol total and a breakdown by capital provider.
If
to is omitted, it defaults to the request time. If from is omitted, it defaults to 30 days before the resolved to. The range can span at most 365 days. from must be earlier than to, and neither may be before 1970-01-01T00:00:00Z. A timestamp with another offset, such as +02:00, is converted to UTC.
lpAddress is the stablecoin delegate contract used by the swap, and it accepts any delegate that /v1/info lists for the network. With lpAddress, the top-level volume and counts cover that capital provider only, and lpVolumes holds its one entry, even with no legs. unattributedLegCount and unattributedStablecoinDelegateIds still cover the whole network. An address that is not one of the network’s delegates is rejected with 400 and details.field lpAddress.
Volume calculation
Every realized swap event is counted once, including automatic prefund or sweep legs. Each leg is valued by the first rule that applies:- A stablecoin input:
amountInat $1. - Otherwise, a stablecoin output:
amountOutplus all stablecoin-denominated event fees, at $1. - Otherwise, an RWA input:
amountInat the RWA’s latest price.
lpVolumes splits the same result by capital provider. Each capital provider’s volume is rounded once to six decimals, and the top-level value is the sum of those displayed values.
RWA prices are refreshed about once a day, and usedPrices gives each price’s fetchedAt and blockNumber. Every leg uses the latest price, so historical RWA-valued volume changes when a price changes. If an RWA has no nonzero price, the endpoint still returns 200 with the known priced volume, pricingComplete: false, the unpriced leg count, and the missing asset IDs.
A leg whose stablecoin delegate is not listed, such as a newly deployed delegate that /v1/info does not list yet, has no known capital provider. It is left out of every other count and volume and reported in unattributedLegCount and unattributedStablecoinDelegateIds.
A completed deployed delegate whose stablecoin Multiliquid no longer lists stays attributed: its legs count toward its capital provider, and lpAddress accepts it. Its stablecoin’s decimals are unknown, so such a leg is valued from its other side: a listed stablecoin at $1, or an RWA at its latest price. If that RWA has no price, the leg is unpriced and the RWA’s ID goes in missingPriceAssetIds. A leg between two such stablecoins is unpriced, with its input stablecoin’s ID.
Response
USD volume values are decimal strings with six fractional digits. In
usedPrices, priceUsd is the RWA’s USD price as a decimal string with 18 fractional digits, such as 1.250000000000000000, fetchedAt is when it was read, and blockNumber is the block it was read at.
Coverage
Transaction-history and volume responses both includecoverage:
historicalBackfill gives the complete contiguous range from startBlock. lastMatchingStreamObservation is the most recent block seen live with matching activity; it does not mean every later block was seen. Block numbers are decimal strings.
For volume, coverage and pricing completeness are separate: coverage describes how much chain history the response covers, and pricingComplete describes whether every leg in it could be valued.
Errors
Errors use the standard error body. A bad parameter, address, hash, range, limit, or cursor, or an unknown query parameter, is a400 with code INVALID_REQUEST; details.field names the parameter when one is at fault. Past your allowance, a route answers 429 with code RATE_LIMITED; a busy service answers 503 with code SERVICE_UNAVAILABLE. Retry both after Retry-After. Errors lists every code.