# wodan-posture

Machine-payable access-posture reports. Pay per call in USDC on Base (x402).
No signup, no API key.

## Free
GET /v1/catalog            machine-readable price list
GET /v1/page/posture/preview?url=https://example.com   verdict + schema + one evidence line
GET /health                liveness, price, network

## Paid ($0.01 per call)
GET /v1/page/posture?url=https://example.com

## MCP (the same tool, on the protocol agents speak)
POST /mcp               streamable HTTP, JSON-RPC
  tool page_posture     paid, $0.01: the full report
  tool posture_preview  free, rate-limited: verdict + schema + one evidence line
Discovery: /.well-known/mcp.json

Answers: is this page safe and practical to treat as a data source?
  posture              open | machine_readable | robots_disallowed | bot_walled | auth_required | js_rendered | thin_content | unreachable
  confidence           how much the signals agree
  recommended_action   what an agent should do instead, when the page is closed
  robots               whether robots.txt allows this exact path for an agent UA
  bot_wall             vendor fingerprint (cloudflare, perimeterx_human, datadome, akamai, ...)
  rendering            whether the HTML needs JavaScript to hold any content
  content              title, canonical, visible-word count, main-content hint
  structured_data      JSON-LD @types present
  licensing            licence hint found on the page
  evidence             the specific lines that led to the verdict
  provenance           fetched-at, schema version, robots URL

## Payment
Call the paid route with no payment and read the PAYMENT-REQUIRED header:
it carries the price, the asset, the network and the receiving address.
Sign, retry the same request with PAYMENT-SIGNATURE, read PAYMENT-RESPONSE
for the settlement receipt.

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