# Argos Bot CTS Bridge API – Submit Bridge Job

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

Submit a signed bridge job to transfer tokens or set up ownerless wrapper connections between Arc (chain 5042) and Base (chain 8453) using Circle's CTS and CCTP infrastructure.

## Facts

- Endpoint: POST https://bridge-api.argosbot.io/v1/jobs?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/argos-bot-cts-bridge-api-submit-bridge-job-7722e9b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tTTgm9hkRQR3Uz1lxlRgl

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-submit-bridge-job-7722e9b8 -d '<json body>'
```

Example prompt: Bridge 50.0 USDC from my account 0xABCD...1234 on Arc (chain 5042) to Base — allow setup if needed, set max gas budget to 5000000000000000 atomic units and max forwarding fee to 1000000000000000 atomic units, and I acknowledge the transfer risks.

## When to prefer this

Choose this endpoint when you need to bridge tokens specifically between Arc (chain 5042) and Base (chain 8453) using Circle's CTS/CCTP infrastructure, particularly when ownerless wrapper deployment may be needed. Prefer it over generic bridge aggregators when you require deterministic fee caps (maxForwardingFeeAtomic, maxGasBudgetAtomic), EIP-712 signed authorization flows, and idempotent retry support via clientRequestId.

## Known failure modes

- Invalid or expired signature — EIP-712 signature does not match the authorization payload
- Chain ID not supported — must be 5042 (Arc) or 8453 (Base)
- riskAcknowledged not true — request rejected if risk flag is missing or false
- allowSetup false but wrapper not deployed — transfer fails if setup is required but not authorized
- Max gas budget exceeded — transaction reverted because on-chain gas cost exceeded maxGasBudgetAtomic
- Forwarding fee exceeded — job aborted because fee exceeded maxForwardingFeeAtomic
- Account is not an EOA — contract wallets rejected for both signer and recipient
- Duplicate clientRequestId with different parameters — conflict error returned
- Expired expiresAt timestamp — authorization window has passed
- Payment required (402) — $0.01 USDC payment not yet completed

## 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

A JSON response containing the bridge job result, including job status, transaction hashes, gas used, forwarding fees applied, and any errors encountered during setup or transfer execution.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "intent": {
   "type": "object",
   "required": [
    "clientRequestId",
    "chain",
    "token",
    "account",
    "mode",
    "amount",
    "allowSetup",
    "riskAcknowledged",
    "maxForwardingFeeAtomic",
    "maxGasBudgetAtomic"
   ],
   "properties": {
    "mode": {
     "enum": [
      "setup",
      "transfer"
     ],
     "type": "string",
     "description": "Setup only or transfer after optional setup"
    },
    "chain": {
     "enum": [
      5042,
      8453
     ],
     "type": "integer",
     "description": "Chain containing the input token and paying network gas"
    },
    "token": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{40}$",
     "description": "Nonzero EVM address"
    },
    "amount": {
     "type": "string",
     "description": "Exact decimal token amount; 0 for setup. Never use floating-point arithmetic."
    },
    "account": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{40}$",
     "description": "External EOA signer and destination recipient; must be an EOA on both chains"
    },
    "allowSetup": {
     "type": "boolean",
     "description": "Explicit authorization to register and deploy a missing ownerless connection"
    },
    "clientRequestId": {
     "type": "string",
     "format": "uuid",
     "description": "Unique ID for this intended operation; retain it across payment retries"
    },
    "riskAcknowledged": {
     "type": "boolean",
     "const": true,
     "description": "Acknowledges original-token transfer risks; simulations are not certification"
    },
    "maxGasBudgetAtomic": {
     "type": "string",
     "pattern": "^(0|[1-9][0-9]*)$",
     "description": "Unsigned decimal integer in native atomic units (18 decimals), per transaction"
    },
    "maxForwardingFeeAtomic": {
     "type": "string",
     "pattern": "^(0|[1-9][0-9]*)$",
     "description": "Unsigned decimal integer in native atomic units (18 decimals), per transaction"
    }
   },
   "additionalProperties": false
  },
  "expiresAt": {
   "type": "integer",
   "description": "Unmodified millisecond deadline from authorization endpoint"
  },
  "signature": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{130}$",
   "description": "EOA signature of returned EIP-712 typed data"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/argos-bot-cts-bridge-api-submit-bridge-job-7722e9b8/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)