Should an agent pay this x402 endpoint? One read-only call (never pays): validates the 402 + accepts[] (will it settle), labels liveness LIVE|ZOMBIE|DEAD, flags an absolute price-trap (>=$1000 honeypot => AVOID), scans resource + MCP tools for LLM01/LLM08 injection, screens payTo vs OFAC/scam, verifies price (live vs advertised: MATCH|OVERCHARGE|UNDERCHARGE), and flags Attack-III cache-leakage posture (is the paid route non-cacheable or does a shared cache leak the paid body). Returns PAY|CAUTION|AVOID + fix hints. Not a settlement guarantee.
0 endpoints · $0.001–$0.001
About Should an agent pay this x402 endpoint on PayAPI Market
What APIs does Should an agent pay this x402 endpoint offer?
Should an agent pay this x402 endpoint has 1 live API on PayAPI Market with 0 endpoints in total, in Finance: Should an agent pay this x402 endpoint.
Are Should an agent pay this x402 endpoint's APIs verified?
1 of 1 have at least one settlement-verified route: PayAPI Market paid for a real call from its own wallet, received real data back and recorded the USDC payment on-chain. Each listing page shows which routes were paid and links the receipt.
How do I pay for Should an agent pay this x402 endpoint's APIs?
Per request, in USDC, over the x402 protocol. An agent calls the endpoint, receives HTTP 402 with the price and wallet, pays and retries. There is no API key, account or subscription, and Should an agent pay this x402 endpoint keeps 100% of each payment.