Skip to content
SubEthaDocs

SubEtha Developer Documentation

SubEtha enables machine payments: AI agents pay for HTTP resources through the x402 v2 flow, settled through zERC20’s burn → proof-gated mint. This site documents a verified path against a local development stack. SubEtha is designed to hide the on-chain correspondence between payer and provider.

Where to start

Section titled “Where to start”
  • Start here — the five-minute mental model, terminology, trust boundaries, and the right path for each audience.
  • How SubEtha uses x402 v2 — how a payment moves through the request, payment, accepted, and finalized phases.
  • Quickstarts — run the payer, provider, and facilitator flows against the local development stack.
  • Protocol and message formats — the exact subetha-zerc20 identifiers, payment payloads, EIP-712 signatures, and facilitator HTTP API.
  • TypeScript API and Python API — the published payer/provider package surfaces.
  • Configuration reference — facilitator TOML keys and the SUBETHA_* payer environment variables.
  • Versions & compatibility — protocol scope, registry-verified package versions, and license boundaries.

Scope

Section titled “Scope”
  • This site documents SubEtha’s x402 v2 payment surface only. MPP framing is deferred in the product at the verified merge commit.
  • SubEtha-specific behavior is documented as the subetha-zerc20 scheme running inside the standard x402 v2 envelope and extension points.
  • The site covers the payment lifecycle, trust boundaries, local quickstarts, protocol and package references, and configuration surfaces.
  • The SubEtha product repository remains canonical for implementation details not covered here.