Back to Browse
x402 Agent Escrow
x402
x402 Agent Escrow is a paid API for AI agents from x402-agent-suite-production.up.railway.app, paid per call via x402, $0.12/call, status unknown (last checked 2026-10-01).
Creates or manages an agent escrow arrangement, verifying that an HTTP GET/HEAD/DELETE action is allowed and returning an approval decision after x402 payment settlement.
Price / call$0.12
Success—
StatusUnknown
How this service works
24 paid x402 infrastructure APIs for AI agent fleets: buy advisor, audition coach, guard, proxy, MPP, attestations, and pipeline orchestration.
Output
Returns a JSON object with 'ok' (boolean indicating request success), 'allowed' (boolean indicating whether the action is permitted), and 'summary' (a plain-text explanation of the escrow decision after x402 payment settlement).
Example use cases
Gate agent data deletion with escrow
“Before my agent deletes those records, run it through the x402 escrow system and tell me if the deletion is approved after payment clears.”
Verify agent read access within budget
“I need you to check if my agent can fetch this data via GET while staying within its escrow spending limits.”
Authorize fleet HEAD requests via payment
“Validate whether my agent fleet is permitted to run these HEAD requests through x402 escrow and settle any required payments.”
Technical details
Endpoint
POSThttps://x402-agent-suite-production.up.railway.app/api/agent-escrow?utm_source=zero.xyzWhen to prefer
Use this endpoint when an AI agent needs to gate a read-only or destructive HTTP action (GET, HEAD, DELETE) behind an escrow and payment-authorization layer using the x402 protocol. It is most appropriate for agent fleet infrastructure scenarios where spending limits and action approval must be enforced before a request proceeds, rather than just checking limits passively.
Side effects
- Payment not settled — returns 402 with payment-required details
- Invalid HTTP method supplied (only GET, HEAD, DELETE accepted) — validation error
- Missing required 'type' or 'method' fields — schema validation failure
- Escrow condition not met — allowed returns false with summary explanation
- Network or Railway deployment downtime — connection error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"ok": true,
"allowed": true,
"summary": "Paid response after x402 settlement"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"