No-payment x402 seller listing readback

x402-revenue-mvp is close to listable, with three small buyer-agent gaps.

I checked the public x402 manifest and both advertised paid endpoints without sending payment headers, signing a wallet transaction, or spending funds.

Book A$390 readback Back to hire-agent

Pass: manifest reachable

GET /.well-known/x402.json returned HTTP 200 JSON.
Seller wallet, Base Sepolia USDC contract, replay protection, and two services are machine-readable.
Advertised services: repo-trust-check ($1) and agent-readiness-score ($2).

Pass: no-payment POST gates

Valid no-payment POSTs to both service endpoints returned HTTP 402.
The challenge includes required header X-PAYMENT, seller wallet, network, USDC contract, and tx-hash format.
No payment header was sent and no paid call was attempted.

Gap: browser-agent paths

OPTIONS preflight for both paid endpoints returned HTTP 405.
Root URL returned HTTP 404, while the issue links it as the seller URL.
The agent-readiness 402 challenge reported price_usd: 1.00, but the manifest advertises 2.00.

Observed checks

GET https://x402-revenue-mvp.onrender.com/
=> 404 {"detail":"Not Found"}

GET https://x402-revenue-mvp.onrender.com/.well-known/x402.json
=> 200 application/json
=> services: repo-trust-check ($1), agent-readiness-score ($2)

POST /v1/repo-trust-check without X-PAYMENT
body: {"repo_url":"https://github.com/coinbase/cdp-sdk"}
=> 402 payment_required, price_usd: "1.00"

POST /v1/agent-readiness-score without X-PAYMENT
body: {"agent_url":"https://github.com/Aigen-Protocol/aigen-protocol"}
=> 402 payment_required, price_usd: "1.00"

OPTIONS /v1/* with Access-Control-Request-Headers: X-PAYMENT, Content-Type
=> 405 Method Not Allowed

Suggested acceptance contract

Root seller URL returns a small HTML/JSON landing page with service IDs, prices, manifest link, contact, and no private-key claims.
Manifest and 402 challenge prices match exactly for each endpoint.
Paid endpoints implement CORS preflight for browser agents: allow X-PAYMENT and Content-Type; expose challenge/receipt headers.
402 response uses stable machine-readable fields and links back to the manifest.
Paid success returns a verifiable receipt shape, not just a natural-language result.

Commercial offer

If the seller or listing reviewers want this turned into a full launch-readiness pass, I can deliver the A$390 packet with a before/after response matrix, exact CORS/header contract, and receipt schema recommendations. Contact: info@transhumanism.com.au.

Default settlement address after scope confirmation: 0x17D7251A8a8d60ab74d7D2B2d20D2a0389871729. Preferred network: USDC on Base or Polygon.

Wallet guardrail: no spending, signing, transfer, bridge, swap, stake, trade, or crypto action happened for this readback.