API Reference - Multiliquid Protocol

The Multiliquid REST API provides read-only access to live deployment metadata, canonical EVM transaction activity, and protocol volume analytics.

https://api.multiliquid.xyz

All documented endpoints use GET, require no request body, and are publicly accessible without an API key.

Interactive API

Explore the live API with Swagger UI

OpenAPI Specification

Download the machine-readable OpenAPI schema

Quick Start

Retrieve the current Ethereum mainnet deployment:

curl "https://api.multiliquid.xyz/v1/info/evm?chain=mainnet"

const response = await fetch(
  "https://api.multiliquid.xyz/v1/info/evm?chain=mainnet",
);

if (!response.ok) {
  throw new Error(`Multiliquid API request failed: ${response.status}`);
}

const deployment = await response.json();
console.log(deployment.swap_contract);

Deployment metadata uses snake_case. Transaction-history and volume responses use camelCase.

Endpoints

Method	Endpoint	Description
`GET`	`/`	API metadata and endpoint index
`GET`	`/health`	Service health check
`GET`	`/v1/status`	Current API status
`GET`	`/v1/info`	EVM and SVM deployment metadata
`GET`	`/v1/info/evm`	EVM contracts, assets, delegates, and adapters
`GET`	`/v1/info/svm`	SVM programs, assets, LPs, pairs, and vaults
`GET`	`/v1/transactions`	Canonical EVM economic transaction history
`GET`	`/v1/volume`	Protocol swap volume over a selected time range, split by LP

GET /api/status remains available as a legacy alias for GET /v1/status.

Deployment Metadata

Deployment endpoints provide the addresses, asset identifiers, decimals, delegates, and pricing infrastructure needed by an integration.

All Deployments

GET /v1/info

Parameter	Required	Values	Description
`runtime`	No	`evm`, `svm`	Return only the selected runtime

When runtime is omitted, the response contains both evm and svm. When it is provided, the response contains only the selected runtime, keyed by chain.

curl "https://api.multiliquid.xyz/v1/info"
curl "https://api.multiliquid.xyz/v1/info?runtime=evm"

EVM Deployment

GET /v1/info/evm

Parameter	Required	Values	Description
`chain`	No	`mainnet`, `sepolia`	Return one EVM deployment

Omitting chain returns all EVM deployments keyed by chain. Supplying it returns the selected deployment object directly. An EVM deployment contains:

Field	Description
`chain_id`	EVM chain ID
`swap_contract`	`MultiliquidSwap` contract address
`treasury_contract`	Liquid Treasury token address
`stablecoin_delegate_contracts`	LP delegate addresses, stablecoin IDs, tokens, administrators, and optional guardrails
`stable_assets`	Stable-asset names, token addresses, and decimals
`rwa_assets`	RWA names, IDs, tokens, decimals, price adapters, and optional delegates

curl "https://api.multiliquid.xyz/v1/info/evm?chain=mainnet"

The EVM SDK uses this endpoint through loadEvmDeployment() to merge current deployment metadata into its chain presets.

SVM Deployment

GET /v1/info/svm

Parameter	Required	Values	Description
`chain`	No	`mainnet`, `devnet`	Return one SVM deployment

Omitting chain returns all SVM deployments keyed by chain. Supplying it returns the selected deployment object directly. An SVM deployment contains:

Field	Description
`program_id`	Multiliquid Solana program ID
`rwa_assets`	RWA mints and their price sources
`stable_assets`	Stable-asset mints and their price sources
`lp_info`	LP administrators, vault authorities, pairs, mints, and vaults

curl "https://api.multiliquid.xyz/v1/info/svm?chain=mainnet"

Transaction History

GET /v1/transactions

Returns canonical EVM economic transactions for one network. Each transaction includes its inclusion data, receipt outcome, optional decoded top-level call, submitted swap bounds, and realized swap or Treasury allowlist activity.

Query Parameters

Parameter	Required	Description
`network`	Yes	Runtime-prefixed network, currently `evm-mainnet` or `evm-sepolia`
`wallet`	No	Match the sender or an indexed user, operator, receiver, or allowlist wallet
`outcome`	No	Receipt outcome: `success` or `revert`
`activity`	No	Economic activity: `swap` or `allowlist`
`entrypoint`	No	Exact decoded top-level Solidity entrypoint
`transactionHash`	No	Exact `0x`-prefixed EVM transaction hash
`limit`	No	Page size from `1` to `100`; defaults to `50`
`cursor`	No	Opaque `nextCursor` value from the previous page

curl "https://api.multiliquid.xyz/v1/transactions?network=evm-mainnet&limit=25"

Filters can be combined:

curl "https://api.multiliquid.xyz/v1/transactions?network=evm-mainnet&wallet=0x1111111111111111111111111111111111111111&outcome=success&activity=swap&limit=50"

Response

Field	Description
`network`	Selected runtime-prefixed network
`chainId`	EVM chain ID
`transactions`	Transaction rows in descending canonical chain order
`nextCursor`	Opaque continuation cursor, or `null` when no next page exists
`coverage`	Historical-backfill and latest relevant stream-observation metadata

Each transaction contains:

Field	Description
`transactionHash`	EVM transaction hash
`inclusion`	Block number, block hash, transaction index, and timestamp
`sender`, `recipient`, `nonce`, `value`, `selector`	Transaction envelope data
`receipt`	`outcome`, `gasUsed`, and `effectiveGasPrice`
`directCall`	Decoded top-level call and submitted swap legs, when available
`activities`	Realized swap and Treasury allowlist events ordered by `logIndex`

directCall.submittedSwapLegs contains the bounds supplied in calldata. Realized amounts and fees remain in activities; submitted bounds never replace event results. A successful nested swap can have activities without a top-level directCall. A reverted decoded call can have a directCall without realized activities.

Pagination

Rows use descending keyset order. To request the next page, pass nextCursor back with the same network and filters:

const query = new URLSearchParams({
  network: "evm-mainnet",
  limit: "50",
});

const firstPage = await fetch(
  `https://api.multiliquid.xyz/v1/transactions?${query}`,
).then((response) => response.json());

if (firstPage.nextCursor) {
  query.set("cursor", firstPage.nextCursor);

  const secondPage = await fetch(
    `https://api.multiliquid.xyz/v1/transactions?${query}`,
  ).then((response) => response.json());
}

The cursor is tied to the original filters and must be treated as opaque.

Canonicality and Precision

Transactions become visible at first inclusion and may be replaced if the indexed chain reorganizes. A success outcome describes receipt execution; it is not a finality indicator. Native amounts, swap bounds, fees, 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. The endpoint intentionally does not infer token symbols, decimal-formatted token amounts, 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 both the protocol total and an LP breakdown.

Query Parameters

Parameter	Required	Description
`network`	Yes	Runtime-prefixed network, currently `evm-mainnet` or `evm-sepolia`
`from`	No	Inclusive whole-second RFC 3339 UTC lower bound
`to`	No	Exclusive whole-second RFC 3339 UTC upper bound
`lpAddress`	No	One EVM stablecoin delegate address

If to is omitted, it defaults to the request time. If from is omitted, it defaults to 30 days before the resolved to. The maximum range is 365 days.

curl "https://api.multiliquid.xyz/v1/volume?network=evm-mainnet&from=2026-06-01T00:00:00Z&to=2026-07-01T00:00:00Z"

Filter the result to one LP:

curl "https://api.multiliquid.xyz/v1/volume?network=evm-mainnet&lpAddress=0x0630582db5a1949509f21B315677C40b9aEb7bDA"

On EVM, lpAddress is the stablecoin delegate used by the swap. Future SVM transaction support will use the LP vault authority.

Volume Calculation

Every realized swap event is counted once, including automatic prefund or sweep legs:

Stablecoin input is valued from amountIn using a $1 proxy.
Stablecoin output is valued from amountOut plus all stablecoin-denominated event fees using a $1 proxy.
RWA-to-RWA input is valued using the latest cached input-RWA adapter price.

The endpoint aggregates the complete selected range; it does not return time buckets. lpVolumes splits the same result by LP.

Response

Field	Description
`network`, `chainId`	Selected network and EVM chain ID
`from`, `to`	Resolved half-open UTC range
`pricedVolumeUsd`	Total priced volume with six fractional digits
`totalLegCount`	All realized legs in the range
`pricedLegCount`	Legs included in `pricedVolumeUsd`
`unpricedLegCount`	Legs lacking a required RWA price
`pricingComplete`	Whether every leg was priced
`missingPriceAssetIds`	RWA IDs whose prices were unavailable
`lpVolumes`	The same volume and pricing fields grouped by LP
`usedPrices`	Cached RWA prices used for RWA-to-RWA legs
`coverage`	Indexed historical and stream-observation coverage

USD volume values are decimal strings with six fractional digits. Adapter prices in usedPrices are 18-decimal USD-WAD strings and include their fetch time and observation block. If a required adapter price has not populated the cache, the endpoint still returns 200 with the known priced volume, pricingComplete: false, the unpriced leg count, and the missing asset IDs. Current RWA prices are refreshed at startup and every 24 hours. Historical RWA-to-RWA volume is therefore revalued when the cached adapter price changes.

Coverage

Both transaction-history and volume responses include:

Field	Description
`coverage.historicalBackfill.startBlock`	First block in the configured historical range
`coverage.historicalBackfill.nextBlock`	Next block scheduled for historical ingestion
`coverage.historicalBackfill.indexedThroughBlock`	Last contiguously indexed historical block, or `null`
`coverage.lastMatchingStreamObservation`	Most recent relevant streamed block and hash, or `null`

historicalBackfill describes contiguous historical progress. lastMatchingStreamObservation identifies the most recent relevant stream delivery and does not imply that every intervening block was observed. For volume responses, ingestion coverage and pricing completeness are separate:

coverage describes how much chain history has been indexed.
pricingComplete describes whether all indexed swap legs could be valued.

Errors

Invalid parameters return a JSON error:

{
  "error": "error description",
  "status": 400
}

Status	Meaning
`200`	Request completed successfully
`400`	Unsupported or invalid parameter, address, hash, range, limit, or cursor
`500`	Internal indexed-data or database error

Always check the HTTP status before reading a response as a successful payload.

Service Endpoints

curl "https://api.multiliquid.xyz/health"
curl "https://api.multiliquid.xyz/v1/status"

/health and /v1/status return plain text. The root endpoint returns API metadata and a JSON index of currently exposed endpoints.

EVM Integration Guide

Use live deployment metadata with the TypeScript SDK

EVM Deployments

Review deployed contracts, assets, IDs, and adapters

Interactive API

OpenAPI Specification

​Quick Start

​Endpoints

​Deployment Metadata

​All Deployments

​EVM Deployment

​SVM Deployment

​Transaction History

​Query Parameters

​Response

​Pagination

​Canonicality and Precision

​Protocol Volume

​Query Parameters

​Volume Calculation

​Response

​Coverage

​Errors

​Service Endpoints

EVM Integration Guide

EVM Deployments

Quick Start

Endpoints

Deployment Metadata

All Deployments

EVM Deployment

SVM Deployment

Transaction History

Query Parameters

Response

Pagination

Canonicality and Precision

Protocol Volume

Query Parameters

Volume Calculation

Response

Coverage

Errors

Service Endpoints