llms.txt
+10 −3
https://x402lint.something-agent.workers.dev/llms.txt
− - POST https://x402lint.something-agent.workers.dev/mcp Remote MCP (Streamable HTTP, stateless): tools lint_x402_endpoint, lint_payment_required− {verdict: ok|warn|fail, counts, summary{x402_version, accepts, prices, extensions, method, challenge_in}, probes, findings[{id, severity: error|warn|info, message, fix?, where?}], not_tested[]}− verdict is fail if any finding is an error, warn if any is a warning.+ - GET https://x402lint.something-agent.workers.dev/v1/directories?url=<paid URL> Same lint plus directory readiness: what x402dash (GET must return 402), x402scan (openapi x-payment-info or /.well-known/x402, input schema), the402 (validator "payable") and the CDP/PayAI Bazaar (bazaar extension, description <= 500 chars, non-tunnel host, then one settled payment) check before listing. Also: /v1/lint?...&directories=1+ - POST https://x402lint.something-agent.workers.dev/mcp Remote MCP (Streamable HTTP, stateless): tools lint_x402_endpoint, lint_payment_required, check_directory_readiness+ For the paid path (settlement, on-chain transfer, delivery, replay and underpayment rejection) run paidpath against your own endpoint with your own key: https://github.com/something-agent/paidpath+ {verdict: ok|warn|fail, counts, summary{x402_version, accepts, prices, extensions, method, challenge_in}, probes, findings[{id, severity: error|warn|info, message, fix?, where?}], not_tested[], scope: "unpaid_path_only", verdict_meaning, paid_path_checks[{id, name, risk, how_to_test}]}+ verdict is fail if any finding is an error, warn if any is a warning. verdict ok is about the unpaid path only: paid_path_checks lists the seller-side failures only a paid call can show (P001 paid-replay, P002 settle-not-called, P003 paid-200-cacheable, P004 paid-response-delivered), each with a do-it-yourself test.+ ## Use in CI+ curl -s -A 'ci/1.0' 'https://x402lint.something-agent.workers.dev/v1/lint?url=<paid URL>' | jq -e '.verdict != "fail"'+ (jq -e exits non-zero on fail; use '.verdict == "ok"' to also fail on warnings.)+ ## Cache note+ 402 is not heuristically cacheable under RFC 9111, so X007 fires only when the 402 explicitly allows caching (usually framework error-page defaults or an edge rule adding public/max-age). The risk is a stale challenge, not a leaked body: a cached payTo/amount can outlive a rotation. A paid 200 is heuristically cacheable: see P003.