# intent402 Bridge Intent Resolver

> intent402 Bridge Intent Resolver is a paid API for AI agents from intent402.dylan-caponi.workers.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-13).

Accepts a natural-language or structured bridge intent and returns an unsigned, ready-to-sign transaction for cross-chain token bridging.

## Facts

- Endpoint: POST https://intent402.dylan-caponi.workers.dev/intent/bridge
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/intent402-bridge-intent-resolver-a8a54daa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CQaUYzMKr-fPTxcpC1j58

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 intent402-bridge-intent-resolver-a8a54daa -d '<json body>'
```

Example prompt: I want to bridge 100 USDC from Base to Arbitrum — can you get me an unsigned transaction ready to sign so I can move the funds cross-chain?

## When to prefer this

Choose this endpoint when an AI agent needs to programmatically construct cross-chain bridge transactions without manually encoding calldata or integrating directly with bridge SDKs. It is ideal for agentic workflows where the agent describes an intent in plain or structured terms and needs a ready-to-sign transaction back — especially when bridging between EVM-compatible L2s and mainnet. Prefer this over raw bridge protocol integrations when speed of integration and intent-based abstraction matter more than fine-grained control.

## Known failure modes

- Unsupported source or destination chain — returns error indicating chain is not supported
- Insufficient liquidity on the bridge route — may return error or degraded estimate
- Malformed or ambiguous intent input — returns validation error
- Payment not received (x402 flow) — request rejected before processing
- Bridge protocol temporarily unavailable — timeout or upstream error from Stargate

## How this service works

Transaction intent resolution for AI agents: describe what you want, get back unsigned ready-to-sign transactions.

## Output

Returns a JSON object containing the bridge protocol used (e.g. Stargate), the resolved intent type, an unsigned EVM transaction object (to, data, value, chainId) ready for the caller to sign and broadcast, an estimated transfer time in seconds, and the expected output amount and destination chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "example": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "bridge": "Stargate",
  "intent": "bridge",
  "transaction": {
   "to": "0x...",
   "data": "0x...",
   "value": "0",
   "chainId": 8453
  },
  "estimatedTime": "120 seconds",
  "expectedOutput": "99.5 USDC on Arbitrum"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/intent402-bridge-intent-resolver-a8a54daa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from intent402.dylan-caponi.workers.dev](https://www.zero.xyz/host/intent402.dylan-caponi.workers.dev/llms.txt)