Integrations
Integrations
Every surface below calls the same client and the same five operations, with the same reason codes. Pick the one your agent already speaks.
| Your agent runs on | Use | Spending boundary |
|---|---|---|
| TypeScript or JavaScript code | TypeScript SDK | Policy in your code |
| Python code | Python SDK | Policy in your code |
| A shell, CI job or coding agent | CLI | Policy file and key file |
| An MCP host (desktop assistants, IDEs, LangChain, CrewAI, ElizaOS) | MCP server | Policy held by the server |
| The AI SDK | AI SDK tools | Policy in your code; tool approval for buying |
| Coinbase AgentKit | AgentKit actions | Policy in your code; wallet used only for signing |
| Another agent over A2A | A2A skills | The calling agent signs each payment |
| Agents that load skills | Agent Skill | Through the CLI or MCP server |
| Anything that speaks HTTP | HTTP API | Your own x402 client |
The five operations
| Operation | Spends | What it does |
|---|---|---|
tollex_resolve | never | The capability Tollex would buy, its route and maximum price, and a reason code for each rejected candidate |
tollex_do | within policy | Buys and runs it; returns the result, the charge, the operation id and the signed receipt |
tollex_operation | never | Execution, settlement and reconciliation state of a purchase |
tollex_verify_receipt | never | Signature and binding checks for a receipt |
tollex_discover | never | Categories, indicative prices and the limits that apply |
Request limits can only narrow the policy. When nothing fits, the answer names the main reason and the single change that would help, and says whether the agent can make that change or only the operator can.
The packages are not on public registries yet. During onboarding you receive tarballs and a wheel; install them from the files, for example
npm install ./tollex-client-0.2.0.tgz.