{"uid":"cap_VCAeuhSsOjLF7wWXP1MGp","slug":"tryx402-x402-agent-payment-proxy-aa21d7e8","name":"tryx402 x402 Agent Payment Proxy","description":"tryx402 is the payment layer for AI agents: hard budget caps, idempotent paid calls, a cost ledger and multi-currency fiat billing over x402.","url":"https://www.tryx402.app/v1/x402/call","method":"POST","headers":{},"bodySchema":{"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"}}},"responseSchema":{"type":"object"},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_ISjbml_6wyEBcvCWQ8suU","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"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","exampleAgentPrompt":"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.","exampleUseCases":[{"title":"Budget-capped agent API shopping","prompt":"My AI agent needs to call a paid product search API at https://api.shopdata.io using POST /search with the query body — route it through tryx402 with a spending cap so it can't overspend, and track what it costs in my ledger."},{"title":"Idempotent paid data enrichment","prompt":"I'm enriching company records by calling a paid firmographics API at https://data.clearbit.com — use tryx402 to proxy the GET /enrich call idempotently so if my agent retries on a timeout I won't get charged twice."},{"title":"Multi-agent cost ledger tracking","prompt":"I'm running a fleet of AI agents that each call different paid APIs — can you route this POST call to https://api.newscatcher.io/search through tryx402 so each agent's spend is recorded separately in the cost ledger and no single agent can blow the budget?"}],"resultDescription":"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.","failureModes":["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"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T18:38:51.448Z","isFirstParty":false}