Bridge status, cross-chain transfer tracker
Status of a cross-chain transfer by its source transaction hash, for transfers made through LI.FI and the bridges it routes (Stargate, Across, CCTP, Hop, Polymer and more): DONE, PENDING, FAILED or NOT_FOUND, the sub-status and its message, sending and receiving transaction hashes, chains, tokens, amounts and explorer links. Use to check whether funds arrived before an agent continues.
Inputs
| Name | Type | Description |
|---|---|---|
txHash (required) | string | Hash of the transaction on the source chain |
fromChain | string | Optional source chain name or id, to speed up the lookup |
Request
Over HTTP, with a card key from /credits:
curl -H "Authorization: Bearer adt_…" "https://agent-data-tools.revmesh2074.workers.dev/bridge/status?txHash=0x8f9e2c2a7a6e0f5b1c3d4e5f60718293a4b5c6d7e8f90123456789abcdef0123"
Or one of your 25 free calls, no key:
curl "https://agent-data-tools.revmesh2074.workers.dev/bridge/status?txHash=0x8f9e2c2a7a6e0f5b1c3d4e5f60718293a4b5c6d7e8f90123456789abcdef0123&trial=1"
Without a key, the same URL answers 402 Payment Required with x402 and MPP terms, so an agent with a wallet pays per call in USDC (Base, Polygon, Arbitrum or Solana over x402; Base or Tempo over MPP) and retries.
Example result
{
"txHash": "0x8f9e…0123",
"status": "NOT_FOUND",
"substatus": null,
"message": "Transaction hash is not found in any chain.",
"bridge": null,
"sending": null,
"receiving": null,
"explorer": null,
"source": "LI.FI (li.quest)"
}
From an AI agent (MCP)
Add the MCP server to Claude, Cursor or any MCP client. This tool is bridge_status, and the first 25 successful calls are free:
https://agent-data-tools.revmesh2074.workers.dev/mcp