Lumière PayCheck
Check an x402 endpoint before your agent pays it.
에이전트 강화
게시자의 자체 URL입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
https://lumierepaycheck.org/mcp?plans=1위의 Claude 버튼을 누르면 이름과 URL이 채워진 상태로 Claude가 열립니다. 확인은 Claude에서 직접 해야 합니다.
claude mcp add --transport http io.github.book0feli-paycheck https://lumierepaycheck.org/mcp?plans=1Run in a terminal.
{ "mcpServers": { "io.github.book0feli-paycheck": { "command": "npx", "args": [ "-y", "mcp-remote", "https://lumierepaycheck.org/mcp?plans=1" ] } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행AI agents now pay for APIs on their own with x402: an endpoint answers 402 Payment Required with a price, the agent pays in USDC, and gets the data. Nothing in that flow tells the agent whether the endpoint works, whether the price is right, or whether the payout wallet is the real one.
Lumière PayCheck answers those questions. It monitors every endpoint listed in the x402 Bazaar, grades each one, and gives your agent a plain verdict: proceed, caution, or avoid.
🌐 Live: https://lumierepaycheck.org · 🔌 MCP: https://lumierepaycheck.org/mcp?plans=1 · 📜 Terms
This repository is the public home for docs, examples, and feedback. The monitoring service itself is hosted and closed-source; the scoring formula is public (below).
Monitors every endpoint in the x402 Bazaar (the badge above shows the live count, which grows as new endpoints are listed) every 30 minutes: price quote, payout wallet, uptime, response time.
Flags hijack risk, without punishing normal rotations. Every payout-wallet change is checked against the seller's own wallet declaration, the seller's earlier wallets, and direct transfers between the old and new wallet. Confirmed rotations don't affect the grade; unexplained changes are avoid, then caution with human review. Sellers that use a new address per request are recognized automatically. How it works.
Spending rules for agents. Before paying, an agent asks "may I pay this endpoint this amount to this wallet?" and gets allow or deny with reasons.
Plans for teams. Scoped agent keys, daily/monthly spend limits, signed receipts your wallet verifies before paying, a replayable audit trail, and human review for anomalies. Details.
Identity and access for agents that pay. Like Entra ID and Intune, for AI agents:
Screening for facilitators. x402 facilitators can screen each payment before they settle it: OFAC sanctions on payer and payee, a payTo that isn't the seller's monitored or declared wallet, a price above the quote. 10,000 checks a month free. Details.
Wallet risk. Before paying any wallet: OFAC sanctions screening, payout-wallet history, and possible-hijack signals in one paid call.
Alerts. Watch an endpoint and get signed webhook alerts when it breaks, changes wallet, or raises its price.
Paid delivery checks: small real payments that confirm an endpoint returns what it advertises. A failure only counts if a re-test about two hours later fails too, and requests an endpoint rejects for missing input never count.
Known-answer tests: values, not just shape. Uptime and schema checks can pass while an API returns the wrong number. For endpoints with a knowable answer, the verifier pays for a call with a known correct result, or compares against an independent live source, and checks the value itself. Sellers can add their own tests. How it works.
Real usage from on-chain data: actual x402 payments (USDC on Base and Solana) into each endpoint's payout wallet over 30 days: volume, distinct buyers, typical and largest payment, trend, and how concentrated the buyers are, counting only payments submitted by recognized facilitators.
Buyer reports: after paying, any agent answers five short questions (with a receipt, or the payment transaction, verified on-chain; one line with the npm package: reportOutcome({ url, response, answers })). Confirmations move an endpoint up our paid-test queue and serious problems trigger a re-test; grades change only when our own paid test confirms.
No accounts, no API keys. Free checks are free; paid features are paid per call with x402, the same way agents pay everything else.
Add the remote MCP server:
https://lumierepaycheck.org/mcp?plans=1
mcp.json):
{ "mcpServers": { "lumiere-paycheck": { "url": "https://lumierepaycheck.org/mcp?plans=1" } } }
Tools: check_payment, check_endpoint, report_outcome, top_endpoints, catalog_stats, get_full_report.
Prefer a local stdio server? packages/mcp-server runs the same tools on your machine (node server.js, or the repo's Dockerfile).
npm i x402-paycheck @x402/fetch
import { x402Client, wrapFetchWithPayment } from "@x402/fetch";
import { withPayCheck } from "x402-paycheck";
const fetchWithPay = wrapFetchWithPayment(fetch, withPayCheck(new x402Client().register(/* your scheme */)));
Every payment is checked by PayCheck before it's signed; a "no" aborts it with the reason. Details: packages/x402-paycheck.
Then add one rule to your agent's instructions:
Before paying any x402 endpoint, call the Lumière PayCheck
check_paymenttool with the endpoint URL, the amount, and the payTo wallet from its 402 quote. Only pay ifallowis true. If it returnsallow: false, tell me the reasons instead of paying. After paying, callreport_outcomewith the receipt (or the url and payment tx) and short answers about whether you got what you paid for.
// Before paying any x402 endpoint, ask Lumière PayCheck.
const res = await fetch("https://lumierepaycheck.org/v1/check-payment", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({ url: target, amount: quote.amount, payTo: quote.payTo }),
});
const decision = await res.json();
if (!decision.allow) throw new Error(`Not paying ${target}: ${decision.reasons.join("; ")}`);
// ...then pay with your x402 client as usual
More in examples/: TypeScript, Python, curl, webhook and receipt verification, a guarded payer, and plan purchase.
Free routes allow 60 requests per minute per client, or 300 with a free API key sent in the x-paycheck-key header. The MCP server allows 300 tool calls per minute. Paid routes use x402 with USDC on Base or Solana (same price on both; on Solana the facilitator pays the fee). Lookups for endpoints we don't monitor return 404 and are never charged. Full reference: docs/api.md.
Free checks stay free. Plans add authorization for agents that spend money:
Subscribe on the website with a card at lumierepaycheck.org/subscribe: billed monthly by Stripe, cancel anytime, and your account is set up automatically. Then manage everything (agent keys, limits, approvals, billing) at lumierepaycheck.org/account. Developers can also pay with USDC via x402 (prepaid 30 days, no auto-renewal).
The agent calls POST /v1/authorize before every payment and gets allow, deny, or review, with reasons. On allow it gets an Ed25519-signed receipt bound to that exact payment, and examples/guarded-pay.ts shows a payer that refuses to sign without one. Every decision can be replayed later to prove why it was made.
Want it set up for you? The setup service ($750 one-time) configures your agents, limits and approval rules, runs them for a 7-day watch-only week so nothing is blocked by surprise, then hands them over with a guide for your team. An optional monthly review is $250/month.
Full guide: docs/subscriptions.md · Subscribe: lumierepaycheck.org/subscribe · Pay with USDC: examples/subscribe.ts
Deterministic and public. No one can pay for a better grade.
What each grade means: A we paid and it delivered, cleanly and reliably · B we paid and it delivered, with a caveat (reshaped vs its listing, a value warning, 80–95% uptime) · C probably works but unconfirmed (not paid-tested yet, needs its own sign-in, 50–80% uptime, an unconfirmed wallet change) · D doesn't work as listed, but you won't lose money (an error after payment with no charge, or the listing's own example input gets "not found") · F costs money or unsafe (took the money and failed, a payout-wallet incident, under 50% uptime). A/B = proceed, C/D = caution, F = avoid.
data/result, or a list of the listed items, count). Endpoints failing a paid check are re-tested dailyproceed means a real paid test delivered and the endpoint is reliable. Healthy endpoints not yet paid-tested are caution (delivery not yet confirmed), kept current by our free checks every 30 minutesblocked; requests the endpoint rejects before quoting (400/405/415/422) are mismatch; failures caused by our own network are monitor_error. Quotes on payment networks we can't read yet (e.g. nano:mainnet) are unsupported_network. None of these count. Network errors and 502/503/504 are retried once. We send at most 2 requests at a time and about 1 per second to any one host, and pause a host that asks us to slow down/v1/failures, with timestamps. Our user agent is lumiere-paycheck-prober/1.0 (+https://lumierepaycheck.org) if you want to allowlist itEvery monitored endpoint has a public page and a badge that updates on its own:
[](https://lumierepaycheck.org/e?url=YOUR_ENDPOINT_URL_ENCODED)
Declare your payout wallets so a rotation is never mistaken for a hijack, and a hijack is caught on the first check: publish {"payTo": ["0xYourWallet"]} at https://<your-host>/.well-known/paycheck.json (or a DNS TXT record at _paycheck.<your-host>: payto=0xYourWallet), then POST /v1/declaration with your endpoint URL. Details.
Think a grade is wrong? Open a Grade dispute with the endpoint URL. A bot replies within a minute with the endpoint's current score and failure log, and queues a paid re-test automatically. When the re-test has run, the bot posts the result (grade before and after) and closes the issue if the grade is fixed. Free re-tests cover endpoints priced at $0.05 or less; for pricier ones the bot posts a link to fund a test at the endpoint's own price. Rules and limits: seller guide.
From the team behind PayCheck: done-for-you follow-up for small businesses. agents.lumierepaycheck.org
Most small businesses aren't short on work; they're short on follow-up. Lumière Agents does the chasing, in the owner's name and voice:
How it stays safe
Lumière Agents is a separate, hosted product from Lumière LLC; its code isn't in this repository.
Lumière PayCheck is an independent project operated by Lumière LLC (Connecticut, USA). It is not affiliated with Coinbase, the x402 Foundation, the Bazaar, or any seller. Scores are automated assessments, not guarantees, endorsements, or financial advice.
Questions, feature requests, and grade disputes: open an issue and pick the matching form. Building an agent that pays with x402? I'd love to hear what it needs.
Guides for evaluating and running Lumière PayCheck: overview, features, pricing, getting started, administrator guide, integration guide, and FAQ. PDFs: Enterprise plan guide (everything included) and 4-page overview.
What personal information we collect and who else handles it: PRIVACY.md (also at lumierepaycheck.org/privacy). Live usage numbers: lumierepaycheck.org/stats. Service status and uptime: lumierepaycheck.org/status.
How keys, payments, and data are protected, including current limitations: SECURITY.md (also at lumierepaycheck.org/security). Report vulnerabilities privately via GitHub security advisories or [email protected].
The documentation, example code and packages in this repository are MIT licensed. The Lumière PayCheck hosted service and its source code are not part of this repository and are not covered by this license.
"Lumière PayCheck", "Lumière" and the Lumière PayCheck logo are trademarks of Lumière LLC. The MIT license covers the code, not the names or logo: forks are welcome, but please give them a different name.
Check x402 endpoints before your AI agent pays: grades, payment checks, refunds, receipts.
{ "mcpServers": { "io.github.book0feli-paycheck": { "url": "https://lumierepaycheck.org/mcp?plans=1", "headers": {} } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 http 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
게시자가 등록한 환경 변수: LUMIERE_PAYCHECK_URL.
Lumière PayCheck에는 HTTP로 연결합니다.
마지막 확인: 2026-11-18. Check x402 endpoints before your AI agent pays: grades, payment checks, refunds, receipts.