# Argos Bot CTS Bridge API – Token Lookup

> Argos Bot CTS Bridge API – Token Lookup is a paid API for AI agents from bridge-api.argosbot.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-17).

Look up whether an ERC-20 token on Arc or Base has a bridged wrapper registered via Circle's CTS/CCTP infrastructure.

## Facts

- Endpoint: GET https://bridge-api.argosbot.io/v1/lookup?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/argos-bot-cts-bridge-api-token-lookup-1698ff8a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_De8xHBCEhwXzr9qC-lnTx

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability argos-bot-cts-bridge-api-token-lookup-1698ff8a
```

Example prompt: Can you check if the token at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Base has a bridged wrapper on Arc using the Argos Bot CTS bridge lookup?

## When to prefer this

Use this endpoint when you need to resolve the bridge registration status of a specific ERC-20 token between Arc and Base networks using Circle's CTS/CCTP infrastructure. Prefer it over generic bridge UIs or on-chain queries when you need structured, programmatic metadata about whether a token has a counterpart wrapper, its exact addresses on both chains, and its role (original vs wrapped) — especially within automated agent workflows that need to decide whether to initiate bridging or wrapper creation.

## Known failure modes

- Invalid or malformed token address (not matching 0x + 40 hex chars) returns a validation error
- Token not deployed as a contract on the specified chain returns status 'not_a_contract'
- Token not registered in the CTS bridge registry returns status 'not_registered'
- Wrapper contract missing on the destination chain returns status 'wrapper_missing'
- Bridge registry temporarily unavailable returns status 'unavailable'
- Ambiguous results when token appears on both chains without clear role returns status 'ambiguous'
- Payment of 0.005 USDC not provided via x402 protocol results in 402 Payment Required

## How this service works

Look up Arc/Base original and wrapped token addresses, bridged supply and ownerless verification. Arc Gateway or direct Base USDC: 0.005 USDC.

## Output

A JSON object containing the bridge lookup result with a status (complete, ambiguous, or unavailable), an array of candidate entries each describing the source token (address, chain, symbol, decimals, role, explorer URL, whether it is a bridged representation) and its paired wrapped token on the other chain, plus cache metadata indicating whether the result was served from cache and its age in milliseconds.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "token"
     ],
     "properties": {
      "chain": {
       "enum": [
        "arc",
        "base",
        "5042",
        "8453"
       ],
       "type": "string",
       "description": "Chain containing the input address; omit to inspect both Arc and Base."
      },
      "token": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{40}$",
       "description": "Original or wrapped ERC-20 contract address to check. Replace the example with any Arc or Base token address."
      },
      "finality": {
       "enum": [
        "latest",
        "finalized"
       ],
       "type": "string",
       "default": "latest",
       "description": "Block finality used for the lookup."
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "required": [
      "requestId",
      "result",
      "payment"
     ],
     "properties": {
      "result": {
       "type": "object",
       "properties": {
        "cached": {
         "type": "boolean"
        },
        "status": {
         "enum": [
          "complete",
          "ambiguous",
          "unavailable"
         ]
        },
        "cacheAgeMs": {
         "type": "integer"
        },
        "candidates": {
         "type": "array",
         "items": {
          "type": "object",
          "properties": {
           "error": {
            "type": "string"
           },
           "source": {
            "type": "object",
            "required": [
             "address",
             "chainId",
             "chain",
             "role",
             "isBridgedRepresentation"
            ],
            "properties": {
             "name": {
              "type": "string"
             },
             "role": {
              "enum": [
               "original",
               "wrapped"
             
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/argos-bot-cts-bridge-api-token-lookup-1698ff8a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bridge-api.argosbot.io](https://www.zero.xyz/host/bridge-api.argosbot.io/llms.txt)