Caution: delivery not yet confirmed
Trust assessment for this x402 endpoint, updated every monitoring cycle. All of this seller's endpoints · Run this endpoint? Get it tested
https://mcp.soundside.ai/mcp
- Score
- 74 of 100
- Uptime, 7 days
- 99.5%
- Median response
- 581 ms
- Test payments
- Needs its own sign-in on top of payment (no charge taken)
- Payout-wallet incidents
- 0
- Current price
- 0.01 USDC
- Browser agents
- Can't pay it yet: CORS headers missing (server-side agents are fine)
- x402 version
- v2
For the seller: make it payable from browser agents
- The 402 response has no Access-Control-Allow-Origin header, so a browser can't read the price quote. Fix: send Access-Control-Allow-Origin: * on 402 responses.
Checked 2026-11-07. This doesn't affect the grade.
Based on 201 checks over the last 7 days. How scores are made
Run this endpoint? Get it tested
This endpoint answers our paid call with a sign-in requirement (no money taken), so it stays C with a "needs its own sign-in" note until a test gets in. That isn't counted as a failure.
- Let our tester in: give it a test account (a short private form; results are labeled "tested with a seller-provided account"), or set up a wallet sign-in (it signs in with its own wallet, like any agent).
- Then Verify your endpoint (our automatic paid tests are paused for now, so you can fund one test at your own price and our tester pays it back to your payout wallet).
Seller guide: payout wallets, known-answer tests and more. Changed your paycheck.json? Check my setup.
Recent paid tests
No paid test has confirmed delivery yet.
| Time (UTC) | Result | Details | Money taken | Counts? | Receipt |
|---|---|---|---|---|---|
| 2026-10-18 03:56:47 | Refused: needs sign-in, wallet refused or customers only (HTTP 401) | needs its own sign-in on top of payment (HTTP 401); no charge taken [seller said: "invalid_token"] | No | No (stays C) | — |
| 2026-09-29 23:47:48 | Refused: needs sign-in, wallet refused or customers only (HTTP 401) | needs its own sign-in on top of payment (reclassified v1.42.5); was: confirmed on re-test: status 401, expected 200; missing fields from example: resource_id, status, success | Yes | No (stays C) | — |
| 2026-09-29 21:33:39 | Refused: needs sign-in, wallet refused or customers only (HTTP 401) | needs its own sign-in on top of payment (reclassified v1.42.5); was: first failure, re-test scheduled: status 401, expected 200; missing fields from example: resource_id, status, success | Yes | No (stays C) | — |
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. 1 counts against uptime; the other 1 was on our side and doesn't count.
| Time (UTC) | What happened | What it means | Affects score? |
|---|---|---|---|
| 2026-11-06 17:51:10 | Monitor problem | Our monitor had a network problem during this check. Not the endpoint's fault. | No |
| 2026-11-02 13:21:51 | No response | The connection failed (ETIMEDOUT), even after a retry. | 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://mcp.soundside.ai/.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.