Not enough data yet
Trust assessment for this x402 endpoint, updated every monitoring cycle. All of this seller's endpoints · Run this endpoint? Get it tested
Bulk listing. market.datapackvibe.com lists 74,580 endpoints, 54% of the whole catalog, most with near-identical names. We monitor all of them, but this one hasn't had enough checks for a grade of its own yet. Judge it by the seller's graded endpoints and by how many independent buyers stand behind the seller (below).
https://market.datapackvibe.com/x402/assistant-schema-artifacthub-repo-yml-8d808449-validate
- Score
- 20 of 100
- Uptime, 7 days
- 0%
- Median response
- Unknown
- Test payments
- Paid and delivered
- Payout-wallet incidents
- 0
- Current price
- Unknown
Based on 2 checks over the last 7 days. How scores are made
Run this endpoint? Get it tested
This endpoint is within our automatic test budget ($0.05 per call), so we pay-test it ourselves at no cost to you. Fixed something, or think the grade is wrong? Request a free re-test: a bot replies on GitHub with the current score and queues a paid re-test.
Seller guide: payout wallets, known-answer tests and more. Changed your paycheck.json? Check my setup.
Recent paid tests
The latest counted paid test delivered.
| Time (UTC) | Result | Details | Money taken | Counts? | Receipt |
|---|---|---|---|---|---|
| 2026-10-22 06:07:20 | Delivered (HTTP 200) | Yes | Yes (passed) | — | |
| 2026-10-15 05:19:07 | Confirmed failure (HTTP 500) | confirmed on re-test: status 500, expected 2xx; none of the example's fields (order_id, sku, status, result, files) in the response, at the top level or inside any wrapper (no charge taken) [seller said: "nothing was charged: Money ledger write failed; reload and reconcile before further changes"] | No | Yes | — |
| 2026-10-15 03:14:14 | First failure, re-test scheduled (HTTP 500) | first failure, re-test scheduled: status 500, expected 2xx; none of the example's fields (order_id, sku, status, result, files) in the response, at the top level or inside any wrapper (no charge taken) [seller said: "nothing was charged: Money ledger write failed; reload and reconcile before further | No | Not unless the re-test fails too | — |
Each paid test sends your listing's own example input (or your declared test request). Fixed something? Use the Get it tested box above.
Paid tests since Nov 7, 2026 come with a signed receipt: the exact payment terms and response (as hashes), amount, result and time, signed with our published key. How to check a receipt · All receipts for this endpoint (JSON)
Recent failed checks
The free checks we run every 30 minutes: uptime and a valid payment quote. Paid tests are in the section above.
2 checks didn't pass in the last 7 days. 2 count against uptime.
| Time (UTC) | What happened | What it means | Affects score? |
|---|---|---|---|
| 2026-11-10 15:57:30 | No payment quote (HTTP 530) | The endpoint answered, but not with the x402 payment request it's listed with. | Yes |
| 2026-11-08 06:07:55 | No payment quote (HTTP 530) | The endpoint answered, but not with the x402 payment request it's listed with. | Yes |
What each result means
- Blocked
- The endpoint's protection (such as Cloudflare) rate-limited or challenged our monitor. That's about our monitor, not the endpoint, so it never affects the score.
- Request mismatch
- The endpoint rejected the format of our test request (HTTP 400, 405, 415, or 422) before quoting a price. That's about our request, so it never affects the score.
- Network not supported yet
- The endpoint asked for payment on a network our monitor can't read yet. That's our limitation, so it never affects the score.
- Monitor problem
- Our own network had an issue during that check. Never affects the score.
- No response
- The endpoint didn't answer within 10 seconds, even after a retry. Counts as downtime.
- No payment quote
- The endpoint answered, but not with the x402 payment request it's listed with. Counts as downtime.
- Unreadable quote
- It asked for payment, but the payment details were malformed, so an agent couldn't pay it. Counts as downtime.
Think this grade is wrong? Dispute it on GitHub. The form is pre-filled with this endpoint; a bot replies with its current score and queues a paid re-test.
We check every endpoint every 30 minutes from Render (US East), user agent lumiere-paycheck-prober/1.0 (+https://lumierepaycheck.org). Operators can allowlist it. Raw data: /v1/failures
Real usage
No x402 payments into this endpoint's payout wallet in our index yet.
Counted from public USDC payments on Base and Solana submitted by recognized x402 facilitators, the services that settle x402 payments. It's a floor: payments on other networks, or before our index started, aren't counted. Daily data: /v1/usage?url=…
Payout-wallet changes
No payout-wallet changes in the last 7 days.
Every change is checked against the seller's own declaration, the seller's earlier wallets, and direct transfers between the old and new wallet on Base. Confirmed rotations don't affect the grade; a change nobody can confirm is "avoid" for 24 hours, then "caution". Run this endpoint? Publish your wallets at https://market.datapackvibe.com/.well-known/paycheck.json as {"payTo": ["0x…"]} so future rotations are recognized instantly. Raw data: /v1/wallet-changes?url=…
Buyer reports
No buyer reports in the last 7 days.
Agents that pay through Lumière PayCheck report whether the response was usable, one vote per buyer. Reports don't change the grade by themselves: problem reports from several buyers trigger our own paid re-test, and only that can change the score.
Run this endpoint?
Show buyers and their agents that your endpoint is monitored. The badge updates on its own.