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

FrameworkWhat it gatesSource
LangChainLLMs, chains, agent tool endpointslangchain
LangGraphCompiled StateGraph executionlanggraph
CrewAICrews, tasks, agent toolscrewai
AutoGenConversations, callable toolsautogen
AG2Multi-agent flows(via AutoGen)
DSPyModules, programs, chainsdspy
LlamaIndexLLMs, query engines, chat engines, ReAct agent toolsllamaindex
Pydantic AIAgents, model callspydantic-ai
Vercel AI SDKModel calls, tool callsvercel-ai-sdk
Semantic KernelChat completions, KernelFunction, pluginssemantic-kernel
Hugging FaceInferenceClient, transformers pipelines, smolagents toolshuggingface
AgnoAgno agentsagno
Google A2AA2A endpoints (server side)a2a

​
Common shape

Every adapter has the same three-method surface: 
from algovoi_<framework> import AlgoVoi<Framework>

adapter = AlgoVoi<Framework>(
    api_base="https://api.algovoi.co.uk",
    api_key="algv_…",
    tenant_id="…",
    webhook_secret="algvw_…",
)

# 1. Check payment status before invocation
status = adapter.check(resource_id="premium-call")

# 2. If unpaid, surface a challenge to the client
if not status.paid:
    raise adapter.PaymentRequired(status.challenge)

# 3. Run the wrapped call
result = adapter.run(...)  # framework-specific

​
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. 
npm install @algovoi/plugin-elizaos

​
Actions

ActionTrigger phrase examplesReturns
CREATE_PAYMENT_REQUEST”invoice £9.99”, “ask for $20 on Solana”checkout_url, token, chain, expires_at
VERIFY_PAYMENT”verify tx abc123”, “confirm payment”on-chain verification result
CHECK_PAYMENT_STATUS”has token xyz been paid?”, “poll checkout”paid, status, tx_id

​
Setup

import { algovoiPlugin } from "@algovoi/plugin-elizaos";

const character = {
  name: "PayAgent",
  plugins: [algovoiPlugin],
  // rest of character config
};
Set environment variables: 
ALGOVOI_API_KEY=algvk_live_...            # required — from dash.algovoi.co.uk
ALGOVOI_DEFAULT_NETWORK=algorand_mainnet  # optional
ALGOVOI_DEFAULT_CURRENCY=GBP             # optional
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