wodan-posture

Ask one question about one URL: can an agent treat this page as a machine-readable data source, and what stands in the way?

Machine-payable: $0.01 per call in USDC on Base, over x402. No signup, no API key, no invoice.

Endpoints

• GET /v1/page/posture?url=... - paid, $0.01. The full report.
• GET /v1/page/posture/preview?url=... - free. Verdict, field schema and one evidence line.
• GET /v1/catalog - free. Machine-readable price list.
• GET /llms.txt - free. Description written for agents.
• GET /openapi.json - free. Schema with the payment terms embedded.
• GET /.well-known/x402 - free. Payment terms at the conventional location.
• GET /health - free. Liveness, price, network.
• GET /check - free, for people. Paste a URL, see the verdict.

Try the free one: /v1/page/posture/preview?url=https://example.com · or in a browser at /check

Paying, in three requests

curl -i "https://wodan-posture.app.goedvps.com/v1/page/posture?url=https://example.com"
# -> 402, read the PAYMENT-REQUIRED header: price, asset, network, receiving address
# sign the payment, then repeat the same request with PAYMENT-SIGNATURE
# -> 200 with the report, and PAYMENT-RESPONSE carrying the settlement receipt

Facilitator: https://facilitator.payai.network
Network: eip155:8453 · Asset: USDC · Pay to: 0x675E8c0463B2bDC0927904c9FB231573CcCc1827

What comes back

• posture - open, machine_readable, robots_disallowed, bot_walled, auth_required, js_rendered, thin_content, unreachable
• confidence, recommended_action - how much the signals agree, and what to do instead
• robots - whether robots.txt allows this exact path for an agent
• bot_wall - vendor fingerprint · rendering - does it need JavaScript
• content, structured_data, licensing - title, word count, JSON-LD types, licence hint
• evidence - the specific lines that led to the verdict · provenance - fetched-at, schema version