api.paystage.xyz
● LiveEvaluate MCP payment against spend policy
Claim this service- Price
- $0.002
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 1 of 1 check
Endpoint
POSThttps: //api.paystage.xyz /v1 /evaluate_mcp_payment
$0.002 asked in its payment challenge on 14 Nov 2026
curl -i -X POST 'https://api.paystage.xyz/v1/evaluate_mcp_payment' \
-H 'Content-Type: application/json' \
-d '{"type":"object","required":["payment_required","policy"],"properties":{"policy":{"type":"object","description":"The spend policy to evaluate it against"},"agent_id":{"type":"string","description":"Optional identifier for per-agent budgets"},"payment_required":{"type":"object","description":"The decoded x402 challenge the agent is considering signing"}}}'Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/api.paystage.xyz
Recent checks
14 Nov 2026Taller is slower; grey is not live.14 Nov 2026
- Median response
- 291 ms
- Last checked
- 14 Nov, 12:29 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 1 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 14 Nov, 12:29 UTC | Live | 402 | 291ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 14 Nov, 12:29 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does api.paystage.xyz advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.