Back to Browse
Argos Bot CTS Bridge API – Direct Lookup
x402
Argos Bot CTS Bridge API – Direct Lookup is a paid API for AI agents from bridge-api.argosbot.io, paid per call via x402, $0.007/call, status unknown (last checked 2026-10-13).
Look up the bridge relationship of an ERC-20 token address between Arc and Base chains, returning wrapper and original token details via Circle's CTS infrastructure.
Price / call$0.007
Success—
StatusUnknown
How this service works
Look up bridges, create ownerless wrappers and bridge tokens between Arc and Base using Circle’s CTS and CCTP infrastructure.
Output
Returns a JSON object with requestId, payment details, and a result object containing: bridge status (complete, ambiguous, or unavailable), cache info (cached flag and age in milliseconds), and a candidates array. Each candidate includes source token details (address, chainId, chain, role, symbol, decimals, explorerUrl, isBridgedRepresentation) and wrapped token details, plus a per-candidate verification status (verified, not_registered, wrapper_missing, not_a_contract, verification_failed, or unavailable).
Example use cases
Verify bridged token on Base
“Check whether 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Base has a corresponding original token registered on Arc — tell me the source and wrapped token details if they exist.”
Resolve Arc token's bridge counterpart
“I have this Arc token address 0x1234567890abcdef1234567890abcdef12345678 — can you find out what its wrapped version looks like on Base using finalized block finality?”
Audit bridge registration for a DeFi token
“Look up the bridge status of ERC-20 token 0xdAC17F958D2ee523a2206206994597C13D831ec7 across both Arc and Base — I need to know if it's registered, what its role is, and whether any wrapper is missing.”
Technical details
Endpoint
GEThttps://bridge-api.argosbot.io/v1/lookup/direct?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need to programmatically resolve whether an ERC-20 token has a bridge relationship between Arc and Base chains, specifically using Circle's CTS infrastructure. Prefer this over generic block explorers when you need structured, machine-readable bridge status including wrapper addresses, roles, and verification states. Best suited for DeFi agents that need to validate token bridgeability before initiating cross-chain transfers.
Side effects
- Invalid token address format (must match ^0x[0-9a-fA-F]{40}$) returns validation error
- Token not found on specified chain returns status 'not_registered'
- Token address is not a contract returns status 'not_a_contract'
- Wrapper contract missing returns status 'wrapper_missing'
- CTS/CCTP infrastructure unavailable returns status 'unavailable'
- Ambiguous result when token appears on both chains in conflicting states returns status 'ambiguous'
- Payment failure (insufficient USDC) blocks request under x402 protocol
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json"
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"