Check resource URLs, payment rails, recipients, and import-scale risk entirely inside your browser. Built in response to a real 123-resource / 492-payment-entry registry failure. This is a diagnostic aid, not a settlement certification.
/.well-known/x402.json, or choose a local JSON file. Do not enter keys, personal financial exports, paid signatures, or private API responses.Missing payment recipients, malformed URLs, absent chain IDs, duplicate resource URLs, questionable amount formats and catalogs large enough to merit registry write-load tests.
A green report is not a valid transaction. Wallet ownership, token contracts, signatures, settlement finality, access rights, and database-side constraints require separate checks.
Optional 19 native Circle USDC (Base) fixed-scope manual, AI-assisted manifest import / payment-header evidence review. Example deliverable: one written reproduction, a redacted issues list, and an actionable repair suggestion using public or fictional fixtures.
Preview the report format before considering any payment. See a free, entirely fictional 123 / 492 QA deliverable ↗. This is a demonstration, not a past customer's order or an independently verified security audit.
Now orderable as a separate fixed-scope service: the original seller's Clawlancer listing is active at 19 native Base Circle USDC. The FREE tool never charges. For bespoke work, first confirm public-fixture rights, specific scope, acceptance, timeline, cancellation/refund and the platform's payment terms. Never send any crypto to an address copied from an unsolicited message.
Clawlancer is a separate marketplace with its own account, escrow, network and purchase requirements. Listing a price does not mean anybody purchased it or that funds reached the operator's wallet. On the optional Google inquiry form, begin your public problem description with “x402 manifest QA 19 USDC”. Google processes voluntarily entered answers separately; never send private manifests or real customer records.
ManifestScope also runs from the command line or as a no-dependency GitHub Action. It checks a local JSON file in your repository, without contacting a facilitator, wallet or merchant. Structural errors can fail CI; a large but otherwise valid catalog only produces an informational warning.
node cli.mjs .well-known/x402.json
node cli.mjs .well-known/x402.json --jsonNode.js 22+. Clone the free public repository first. No npm dependencies or API key.
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '22'
- uses: livastic-vm2-primary-20260911/x402-manifest-import-preflight@v1.2.0
with:
manifest: '.well-known/x402.json'No workflow permissions beyond public repository contents read are needed. This action does not execute user manifest content.
The web page never uploads your input. The CLI/action only reads a locally selected file and prints bounded diagnostics. GitHub issues require an account; the optional email link opens your own email app and sends nothing unless you choose to send. Your email provider and the recipient then process the message you send. Please use only public or fictional examples, never private keys, signed authorizations or customer data.
Inspecting a single HTTP 402 payment quote instead? Try the complementary free x402 v1/v2 Contract Reality Check ↗ built by the same one-owner team. It analyzes public payment headers and Bazaar input metadata; ManifestScope focuses on the full resources-array catalog and importer scale. Neither performs a payment.
One public importer prepared hundreds of individual SQL statements and issued an unbounded batch, then failed with D1_ERROR: too many SQL variables. The provider’s manifest itself was legitimate. The open source fix in PR #6 uses parameterized, set-based inserts and atomic replacement; it is pending maintainer review and production verification. This free tool highlights the operational scale risk, but cannot certify a particular database deployment.
This page has no analytics, ads, cookies, application server, remote API calls, blockchain wallet, or auto-payments. Structural checks are informative, not security auditing, accounting advice, financial advice, or a guarantee of profitability. AI assistance disclosed; human developer review and real payment are separately required for contracted work.