x402 interop

Install

pip install "openmoe-bft[x402]"

How it works

1. Your agent calls an openmoe-bft endpoint (a hosted BFT route or validate_agent_card).
2. Server replies 402 with an x402 payment envelope (amount, asset, pay-to address).
3. The agent’s wallet signs payment; the retry carries the X-PAYMENT header.
4. The response includes a hash-chained cryptographic receipt (HMAC-SHA256 / Ed25519) — payment AND routing decision are both tamper-evident.

Why x402 + BFT belong together

A quorum decision you paid for is only worth something if you can prove it happened. Every paid call returns a receipt chained into the hive ledger — auditable offline, EU AI Act Articles 9–15 checks included.

Free vs paid

• Free / Apache-2.0: the entire core library, stdlib-only. Self-host everything.
• Starter £29/mo · Pro £199/mo · Enterprise £1,499/mo: hosted endpoints + CSOAI governance — see pricing.
• x402 PAYG: per-call on any tier, no signup.
• £4,950 one-time: CSOAI Watchdog Certification assessment.

Interop targets

• A2A: agent card at /.well-known/agent.json; validate_agent_card is the fleet CI check.
• MCP: pip install "openmoe-bft[mcp]" → streamable-HTTP server.
• x402 facilitators: any facilitator speaking the open spec.