# Coding Agent Context APIs – Intent Resolver

> Coding Agent Context APIs – Intent Resolver is a paid API for AI agents from x402-canary.nicolas-x402-16f380a7.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-16).

Routes a natural-language coding intent to the correct tool (e.g. json-inspect, sha256, dns-lookup) and returns the canonical API route for that tool

## Facts

- Endpoint: POST https://x402-canary.nicolas-x402-16f380a7.workers.dev/v1/intent/resolve
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/coding-agent-context-apis-intent-resolver-603bb42c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ED8O9kWiCqwdR1du3HsF5

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 coding-agent-context-apis-intent-resolver-603bb42c -d '<json body>'
```

Example prompt: I need to validate some JSON — can you figure out which tool to route this to and give me the canonical API route I should call?

## When to prefer this

Use this endpoint when an AI coding agent needs to dynamically resolve which specific tool or API route to invoke for a given task, rather than hard-coding tool selection. Ideal for agents that receive open-ended coding or developer-utility intents and need authoritative need-to-tool routing before making downstream calls. Prefer over static routing tables when the tool landscape may change or when the agent needs to discover canonical routes at runtime.

## Known failure modes

- Invalid or unsupported intent enum value — endpoint returns an error or null route
- Malformed input object — request body validation failure
- Payment not included or insufficient — x402 payment required error (HTTP 402) for pay-per-call tools
- Cloudflare Worker cold start or timeout — transient 5xx error
- Intent string submitted as free-text instead of exact enum value — routing fails or returns unexpected match

## How this service works

Free need-to-tool routing plus pay-per-call npm docs and TypeScript API signatures, npm breaking-change diffs, JavaScript-rendered browser snapshots and deterministic coding-agent checks via AgentCash/x402.

## Output

Returns a JSON object with a 'data' field containing the matched tool name, the resolved intent string, the canonical gateway route (e.g. /v1/gateway/run), and any initial result data; plus a 'meta' field indicating the routing engine used.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object"
  },
  "intent": {
   "enum": [
    "exchange rate",
    "currency conversion",
    "recent earthquakes",
    "explain cron",
    "domain preflight",
    "domain enrichment",
    "mail security",
    "email validation",
    "dns lookup",
    "normalize url",
    "inspect json",
    "json validation",
    "sha256",
    "text fingerprint"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "tool": "json-inspect",
   "intent": "json validation",
   "result": {},
   "canonical_route": "/v1/gateway/run"
  },
  "meta": {
   "engine": "gateway"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/coding-agent-context-apis-intent-resolver-603bb42c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-canary.nicolas-x402-16f380a7.workers.dev](https://www.zero.xyz/host/x402-canary.nicolas-x402-16f380a7.workers.dev/llms.txt)