Back to Browse
x402 Agent Suite Pro — Proxy Endpoint
x402
x402 Agent Suite Pro — Proxy Endpoint is a paid API for AI agents from x402-agent-suite-production.up.railway.app, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-14).
Acts as a paid x402-protocol proxy that forwards HTTP GET/HEAD/DELETE requests through the x402 payment infrastructure, returning security analysis and access results after payment settlement.
Price / call$0.08
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), allowed (boolean indicating post-payment access), summary (human-readable explanation), securityGrade (letter grade), riskScore (numeric), and targetProbe object containing the HTTP status, requiresPayment flag, and priceUsdc of the target endpoint.
Example use cases
Pre-flight security check for agent fleet
“Before my agent fleet starts calling that new data API, can you proxy a HEAD request through x402 to check its security grade and risk score so I know if it's safe to route traffic there?”
Gating access behind x402 payment settlement
“My agent needs to access a paid endpoint — run a GET request through the x402 proxy so the payment settles automatically and tell me whether access was allowed and what the response status was.”
Auditing unknown API risk before integration
“I found an HTTP endpoint I want to integrate but I'm not sure if it's trustworthy — can you send a GET through the x402 proxy and give me the security grade and risk score before I commit to using it?”
Technical details
Endpoint
POSThttps://x402-agent-suite-production.up.railway.app/api/x402/proxyWhen to prefer
Choose this endpoint when your AI agent needs to route HTTP read-only requests (GET/HEAD/DELETE) through a payment-settled x402 proxy with built-in security analysis. It is especially useful when you need to audit an unknown endpoint's risk score and security grade before integrating it into an agent fleet, or when the target endpoint itself requires x402 payment to access. Prefer this over raw HTTP calls when payment settlement, security grading, and access control validation are all needed in a single step.
Side effects
- Payment settlement failure — x402 payment header invalid or insufficient USDC balance, returns 402 with payment required details
- Method not allowed — only GET, HEAD, DELETE are accepted; POST or PUT inputs return validation error
- Target unreachable — proxied target URL is offline or times out, returns error in summary field
- Invalid input schema — missing required 'type' or 'method' fields returns 400 bad request
- Access denied — target endpoint blocked even after payment, allowed=false in response
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"