Back to Browse
x402 Identity Gate Check
x402
x402 Identity Gate Check is a paid API for AI agents from x402-agent-suite-production.up.railway.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-23).
Checks whether an agent or request is allowed to proceed through an identity gate, returning a boolean allow/deny decision with a summary, gated behind x402 micropayment.
Price / call$0.05
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 three fields: 'ok' (boolean indicating the call succeeded), 'allowed' (boolean indicating whether the request passed the identity gate), and 'summary' (a short human-readable string explaining the decision). After the x402 micropayment of $0.05 USDC is settled, the response reflects the gate's allow/deny verdict.
Example use cases
Pre-flight agent access check
“Before my agent tries to pull data from the protected endpoint, run an identity gate check on the GET request to confirm it's authorized to proceed.”
Agent fleet access enforcement
“I'm running a fleet of agents and need to verify that this DELETE request is permitted through the identity gate — can you check and tell me if it's allowed?”
Pipeline authorization guard
“At the start of my orchestration pipeline, check whether this HEAD request passes the identity gate so I know if the agent should continue or stop.”
Technical details
Endpoint
POSThttps://x402-agent-suite-production.up.railway.app/api/identity-gate/check?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a lightweight, micropayment-gated identity/access check integrated into an x402-native agent pipeline. It is best suited for agent fleet orchestration scenarios where each gate check is a discrete, pay-per-use operation and you need a simple boolean allow/deny with a human-readable summary. Prefer alternatives if you need rich identity assertions, OAuth flows, or JWT-based auth rather than a simple pass/fail gate decision.
Side effects
- Payment not settled — x402 payment challenge returned instead of gate result
- Invalid HTTP method supplied (only GET, HEAD, DELETE are accepted) — schema validation error
- Missing required 'input' field or 'type'/'method' subfields — 400 bad request
- Network or Railway deployment downtime — 502/503 error
- Disallowed request type — allowed=false with explanatory summary
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"