x402fix by AgentGate
Paid API · api.youraitools.co · found in a public list · checked since 2026-10-23
Live, payment required · latest check
Probes a seller's x402 paid URL unpaid and grades its payment setup with a fix list.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Check a service works as described: Probe a paid API, MCP server or A2A agent for whether it answers, conforms, asks for payment correctly, and how its tools change.
POST https://api.youraitools.co/x402fix/v1/lite$0.005 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 28 endpoints from youraitools.co.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
2 passed, 0 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-23 | 2 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-23 | 2 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing an unpaid request answered with a payment request (HTTP 402). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Payment terms
- Price per call
- $0.005
- Protocols
- x402
- Networks
- eip155:8453eip155:137eip155:42161solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
- Terms changes, 90 days
- 0 in 2 days tracked
Price from the registry's payment terms; protocols and networks from its payment request at our checks. Current terms first seen 2026-10-23; 0 receiving-address changes. Definitions
Access
- Our latest check
- Asked for payment (x402)
- Stated
- not stated
- Payment model
- Per call (asked for payment for our request)
- Currency
- USD (USDC, in its payment terms)since
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Calls it declares
GET url
From the payment request it sent our check (request-shape/1). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Identity, security and compliance / Security / Check agent services before use / Check a service works as described (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-24. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Purpose tags: developer-toolsx402lintbazaarcheck-x402-endpoint
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453eip155:137eip155:42161solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp | 256 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453eip155:137eip155:42161solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp | 115 ms |
What these figures do not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_30ca7d1f02c44cd9