Argos Bot CTS Bridge Lookup

Find ownerless token connections between Arc and Base through Circle’s Crosschain Token Standard (CTS) and CrossChainTokenService. Identify the original token, its wrapped counterpart, outstanding wrapped supply and the contracts connecting them.

Available for 0.005 USDC per lookup.

Choose how to pay

Gateway: 0.005 USDC per lookup from a funded Circle Gateway balance on Arc.

Direct: 0.007 USDC per lookup from your Arc wallet, using a signed USDC authorization settled by CRA’s facilitator. No Gateway deposit is needed. Available while CRA settlement capacity allows.

GET /api/v1/bridge/lookup/direct?token=0x…&chain=arc

CRA currently pays direct-settlement gas within its allowances. If direct payment is unavailable before authorizing a payment, you may choose Gateway. Never switch payment methods while an earlier payment is unresolved; recover that request first.

Circle infrastructure, identified

The lookup inspects CrossChainTokenService registrations and the associated token managers for connections using Circle’s Cross-Chain Transfer Protocol (CCTP). It checks contract identities, token bindings, ownerless configuration and pause state against the deployments supported by Argos Bot.

Bridge lookup and API payment use separate infrastructure: CTS and CCTP provide the token connection being inspected; Circle Gateway handles the default x402 payment rail for this API. This lookup does not register tokens, create wrappers or execute bridge transfers.

Both directions, clearly identified

Submit an original token or its wrapper. Every token is labeled Arc or Base, original or wrapped. Arc originals can have Base wrappers; Base originals can have Arc wrappers. Returning a wrapper to its original chain is reported as burn and unlock.

GET /api/v1/bridge/lookup?token=0x…&chain=arc

Use chain=base for an address on Base, or omit chain to inspect both. Use finality=finalized for finalized snapshots instead of the latest observed blocks.

What you receive

Original and wrapped addresses, token roles, direction, setup and operational status, outstanding wrapped supply, CrossChainTokenService and token-manager addresses, explorer links, and block evidence. Existing pairs are remembered; cached observations are explicitly timestamped and expire after 30 seconds.

A missing registration is a valid result. Network failures are not reported as missing bridges. Verification confirms the contract connection; it does not certify the original token’s transfer behavior, liquidity or redemption safety.

Pay per request with x402

When enabled, an unpaid request returns HTTP 402 with payment requirements. An x402 client handles the authorization and retries. The default payment rail uses Circle Gateway with the @circle-fin/x402-batching SDK, accepting USDC on Arc. This service does not request token approvals, bridge funds or need your private key.

Keep the signed payment private. If the response is interrupted, retry the identical query with the same Payment-Signature to recover the result for 24 hours. A pending or uncertain payment must not be replaced automatically. Successful no-bridge results are charged; lookups that fail before settlement are not submitted for payment.

Official infrastructure references

Argos Bot is an independent project and is not affiliated with or endorsed by Arc or Circle. Official infrastructure references identify the underlying protocols; they do not imply endorsement of this service or any token.

Argos Bot CTS Bridge Lookup