Enter a required DefiLlama numeric bridge ID and inspect that one bridge’s transfer volume across chains. Get the ID from DefiLlama’s bridges list first.
Up to 0.00072 credits / call
The final charge is based on confirmed usage. Unused reserved credits return to your available balance.
DefiLlama
One DefiLlama Bridge Volume by Chain
Enter a required DefiLlama numeric bridge ID and inspect that one bridge’s transfer volume across chains. Get the ID from DefiLlama’s bridges list first.
You receive
Receive that bridge’s volume summary and volume breakdown by chain. This page does not transfer tokens, list every bridge, or return DEX volume. The tool is listed with no public execution price. Use one Toolmu account across many tools and pay only for actual use, with no subscription.
Start with your task
Use DefiLlama bridge ID [1] to summarize recent volume and the chain breakdown, keeping the reporting periods distinct.
Inputs & outputs
Inspect the current inputs, availability, and maximum charge before starting.
Input schema
Input schema
Field / Path
Type
Requirement
Meaning
pathParamspathParams
object
Required
Required fields
id
Bridge IDpathParams.id
integer
Required
Required integer ID for one bridge in DefiLlama. Get it from the bridges list; do not enter a bridge name, chain ID or token address. The documented example is 1.
Examples
1
View raw JSON
{
"type": "object",
"required": [
"pathParams"
],
"properties": {
"pathParams": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"examples": [
1
],
"description": "bridge ID, you can get these from /bridges"
}
},
"additionalProperties": true
}
},
"additionalProperties": false
}
Result schema
Output fields have not been documented yet.
Additional notes
Check one bridge before building a cross-chain activity report
Use this tool to retrieve DefiLlama's volume summary for one bridge and inspect how the reported activity is distributed across chains. A researcher can use that snapshot to describe recent bridge usage, prepare a monitoring note or choose what to investigate with a separate historical-data request. The result is a data lookup; it does not move funds or request a transaction from your wallet.
Provide the bridge's numeric ID
Find the required integer ID in DefiLlama's bridges list, then enter it as pathParams.id. A bridge name, a blockchain's chain ID and a token contract address are different identifiers. The official example uses bridge ID 1. This call selects one bridge; there is no date range, chain filter or list-all option in this tool's input.
Read the summary using matching time periods
DefiLlama's documented summary includes bridge identity and hourly, current-day, daily, weekly and monthly volume fields. Transaction-count objects separate deposits and withdrawals for the corresponding periods. Compare values with the same period definition: current-day activity can cover an unfinished day, and a rolling period is not automatically equivalent to the last completed day. The available fields and chain entries should be checked in the returned payload.
Use the chain breakdown as context
The provider documents a chainBreakdown object and destination-chain metadata. Chain names are dynamic keys, so the chains present depend on the selected bridge and its coverage. Read this breakdown alongside the bridge summary. Adding both sides of a cross-chain transfer can count the same movement more than once; a breakdown is not by itself a measure of net capital inflow or unique users.
Turn the snapshot into a useful comparison
Record the bridge ID and the time of the lookup with your report. For a second bridge, make a separate lookup and compare matching completed periods. For an activity timeline, token or address detail, or individual transfer records, use the corresponding historical or transaction endpoint; this summary does not return all of those datasets. Volume alone also does not establish bridge security or available liquidity.
Source and coverage
The summary follows DefiLlama’s official API documentation. The chains and available values depend on the selected bridge and the provider’s coverage. Keep the bridge ID and lookup time alongside any saved comparison.
Summarize recent transfer amounts for [Stargate Finance] across networks.
View [Stargate Finance] transfer amounts by network.
Use the integer ID from DefiLlama's bridges list. Do not substitute a bridge name, chain ID or token address; the current input requires pathParams.id.
No. This summary selects one bridge by its required ID. The bridges list is a separate dataset, and additional bridges need separate lookups.
It returns the selected bridge's recent summary and chain breakdown. DefiLlama documents historical bridge-volume series through a different endpoint; this tool has no date-range input.
They describe different time periods. Current-day activity may cover an incomplete day. Compare the same named period across lookups and check the provider's response rather than treating all daily measures as rolling 24-hour totals.
A chain breakdown describes activity on the included chains. A transfer can appear on more than one side, so summing those values does not by itself establish net inflow or unique capital.
No. This is a bridge-activity data lookup. It has no wallet or transfer input and does not execute cross-chain transactions.
