Caution: delivery not yet confirmed
Trust assessment for this x402 endpoint, updated every monitoring cycle. Run this endpoint? Get it tested
https://agents.chain.link/v1/register
- Score
- 74 of 100
- Uptime, 7 days
- 90.5%
- Median response
- 1027 ms
- Test payments
- Needs its own sign-in on top of payment (no charge taken)
- Payout-wallet incidents
- 0
- Current price
- 0.002 USDC
Based on 137 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 check your setup: we re-read your paycheck.json and queue a paid re-test.
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? |
|---|---|---|---|---|
| 2026-10-19 17:22:00 | 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: "missing EIP-191 authentication headers"] | No | No (stays C) |
| 2026-10-12 17:16:20 | 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: "missing EIP-191 authentication headers"] | No | No (stays C) |
| 2026-10-05 17:14:50 | 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: "missing EIP-191 authentication headers"] | No | No (stays C) |
| 2026-10-05 15:14:33 | 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 2xx; none of the example's fields (agent_address, agent_id, execution_mode) in the response, at the top level or inside any wrapper (no charge taken) [seller said: "missing EIP | No | No (stays C) |
| 2026-10-05 08:33:50 | 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 2xx; none of the example's fields (agent_address, agent_id, execution_mode) in the response, at the top level or inside data/result | 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.
Recent failed checks
The free checks we run every 30 minutes: uptime and a valid payment quote. Paid tests are in the section above.
13 checks didn't pass in the last 7 days. 13 count against uptime.
| Time (UTC) | What happened | What it means | Affects score? |
|---|---|---|---|
| 2026-10-24 22:07:34 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-24 20:37:19 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-24 04:56:46 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-23 03:09:43 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-22 07:36:04 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-22 00:06:00 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-19 10:51:20 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-18 19:19:09 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-18 14:49:05 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-18 13:19:03 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-18 10:29:49 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-18 09:26:00 | No response | The connection failed (ETIMEDOUT), even after a retry. | Yes |
| 2026-10-18 07:50:54 | 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
Payments that actually settled into this endpoint's payout wallet over the last 30 days.
Settled volume
$259
Payments
21,092
Independent buyers
~12
of 57 buyer wallets
Typical payment
$0.01
Largest payment
$1.00
Last 7 days
▼ 84%
vs the week before
Settled by 0xa32c…d101 (6%), 0x8cda…fa39 (6%), 0x68ef…1164 (6%) · first seen 2026-09-03.
Buyers reviewed 2026-10-24: 86% of the volume comes from independent buyers. We group buyer wallets by the wallets that funded them; payments from groups of 3+ wallets funded by one source, or by the seller itself, aren't counted as independent. We count customers, not wallets.
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://agents.chain.link/.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.