# tryx402 Agent Payment Layer (x402)

> tryx402 Agent Payment Layer (x402) is a paid API for AI agents from tryx402.fly.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-23).

Executes a paid API call on behalf of an AI agent with hard budget caps, idempotency, cost ledger tracking, and multi-currency fiat billing over the x402 protocol.

## Facts

- Endpoint: POST https://tryx402.fly.dev/v1/x402/call?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tryx402-agent-payment-layer-x402-b530d91c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tpT0rEvLd8xabkKcPz_ay

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-agent-payment-layer-x402-b530d91c -d '<json body>'
```

Example prompt: Make a paid call to the weather API at https://api.example.com/forecast with a hard budget cap of $2.00 USDC, using idempotency key 'weather-run-001', and log the cost to my ledger.

## When to prefer this

Choose this endpoint when an AI agent needs to make paid API calls with strict spending controls, idempotency guarantees, and per-call cost tracking. Ideal for agent fleets where overspending is a risk, or when you need an auditable cost ledger across multiple paid tool calls. Prefer over raw x402 implementations when you need budget enforcement and multi-currency fiat billing without building that infrastructure yourself.

## Known failure modes

- Budget cap exceeded — call rejected before execution with a budget error
- Invalid or malformed x402 payment header — authentication/payment failure
- Target API unreachable — upstream error propagated back
- Duplicate idempotency key with mismatched payload — conflict error
- Insufficient USDC balance — payment cannot be authorized
- Target API returns non-2xx — payment may still be deducted depending on protocol semantics

## 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 response from the target paid API call along with a payment receipt, transaction ID, cost ledger entry showing amount spent, and remaining budget balance. If idempotency key matches a prior call, returns cached result without a new charge.

## More

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