# tryx402 x402 Agent Payment Proxy

> tryx402 x402 Agent Payment Proxy is a paid API for AI agents from www.tryx402.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Proxies a paid HTTP call to any target service with hard budget caps, idempotent payment, cost ledger tracking, and multi-currency fiat billing over the x402 protocol

## Facts

- Endpoint: POST https://www.tryx402.app/v1/x402/call
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tryx402-x402-agent-payment-proxy-aa21d7e8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VCAeuhSsOjLF7wWXP1MGp

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 tryx402-x402-agent-payment-proxy-aa21d7e8 -d '<json body>'
```

Example prompt: Use tryx402 to call the paid weather API at https://api.weatherservice.com via GET /forecast with a hard budget cap, and log the cost to my ledger — I need idempotent payment so I'm not double-charged if it retries.

## When to prefer this

Choose tryx402 when your AI agent needs to call paid third-party APIs with strict spending controls, idempotent payment semantics (safe retries without double-charging), and a persistent cost ledger across multiple calls. It is the right choice when you need a unified payment proxy that handles x402-native services or wraps non-x402 services with budget enforcement — especially in multi-agent fleets where per-agent cost attribution matters. Prefer it over direct API calls when financial accountability, retry safety, or cross-service billing aggregation is a requirement.

## Known failure modes

- Insufficient USDC balance — payment rejected before upstream call is made
- Budget cap exceeded — call blocked to protect spending limit
- Upstream service unreachable — network error after payment already processed (idempotency key allows safe retry)
- Invalid origin URL — target service origin fails validation
- Duplicate call detected via idempotency key — returns cached prior response without re-charging
- x402 facilitator unavailable — payment layer down, call cannot proceed

## How this service works

tryx402 is the payment layer for AI agents: hard budget caps, idempotent paid calls, a cost ledger and multi-currency fiat billing over x402.

## Output

Returns the upstream service's response body wrapped in a tryx402 envelope, along with payment confirmation details, cost ledger entry, and idempotency metadata. The agent receives both the actual API result and a record of what was charged, enabling budget tracking across multiple calls.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "origin"
 ],
 "properties": {
  "body": {
   "type": "object",
   "description": "Request body for upstream call"
  },
  "path": {
   "type": "string",
   "description": "Target endpoint path"
  },
  "method": {
   "type": "string"
  },
  "origin": {
   "type": "string",
   "description": "Target service origin URL"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tryx402-x402-agent-payment-proxy-aa21d7e8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.tryx402.app](https://www.zero.xyz/host/www.tryx402.app/llms.txt)