Skip to main content
Every adapter wraps your framework’s normal call surface and inserts a check() step that returns an HTTP 402 challenge when payment is missing. The client pays on-chain, retries with proof, and the call goes through. Same shape across all 13 frameworks.

Available adapters

Common shape

Every adapter has the same three-method surface:

Picking a protocol

Each adapter supports x402, MPP, and AP2 on the same code path. Pick the one that matches your client:
  • x402 for HTTP-fronted endpoints. The most common case for LangChain or Vercel AI SDK servers.
  • MPP for JSON-RPC or MCP-server-backed tools. Use when the call is method-shaped, not URL-shaped.
  • AP2 for autonomous agents acting on a signed mandate.
See the protocol pages for detail: x402, MPP, AP2.

Chains

All 13 framework adapters support all 7 chains: Algorand, VOI, Hedera, Stellar, Base, Solana, and Tempo. Pass the network key when constructing the adapter (e.g. network="base-mainnet").

Versioning

All adapters are at v1.1.0 of the shared client surface. Behaviour and method names are identical across frameworks; only the wrapping layer changes. If you switch frameworks you keep the same AlgoVoi configuration.

ElizaOS plugin

@algovoi/plugin-elizaos is a native ElizaOS plugin (not a wrapping adapter). It registers three actions on the Eliza runtime so your agent can ask for, verify, and poll crypto payments across all 7 chains without holding any keys or fiat. Agent Trust Bench Passed the AlgoVoi Agent Trust Bench — 71/71 correct (100%) across adversarial payment profiles. Zero adversarial profiles settled.

Actions

Setup

Set environment variables:
Get an API key at dash.algovoi.co.uk/signup. The $1,000 free mainnet trial applies.

What it does not need

The plugin is a thin HTTP wrapper around api.algovoi.co.uk. Your agent needs no wallet, no private key, and no fiat custody — only the API key. Settlement goes direct on-chain customer-wallet → your merchant wallet. Source: github.com/chopmob-cloud/elizaos-plugin-algovoi