Integrations
CLI
tollex plans and buys from a shell. With --json it prints one JSON document; diagnostics go to standard error.
tollex resolve "ETH-USD spot price" --input '{"pair":"ETH-USD"}' --json
tollex do "ETH-USD spot price" --input '{"pair":"ETH-USD"}' --max-cost 0.005 --json
tollex await <operationId> --until included --json
tollex receipt verify <receiptId> --jsonConfiguration
TOLLEX_URL names the service. Paying needs TOLLEX_POLICY_FILE (your policy as JSON) and TOLLEX_WALLET_KEY_FILE, a file readable only by you; the CLI refuses a key file other users can read. There is no flag that skips the policy, raises a budget or enables mainnet.
Exit codes
| Code | Meaning |
|---|---|
| 0 | success |
| 1 | failed |
| 2 | usage error |
| 3 | no eligible capability |
| 4 | refused by policy |
| 5 | transport error |
| 6 | verification failed (receipt, quote, overcharge) |
| 7 | outcome not final yet: await the operation, do not pay again |
| 8 | already completed: that operation id was paid before |
tollex mcp runs the MCP server on stdio with the same configuration, and tollex provider inspect or validate checks a provider source without importing it.
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.