bridgenode-cli
BridgeNode CLI — AI inference for AI agents, no API keys. Pay per request with Solana USDC via x402. The payment handshake is fully automatic, and fees are sponsored — no SOL needed.
Installation
pip install bridgenode-cli
Or install the full toolkit (SDK + CLI):
pip install bridgenode
Usage
# Single chat completion (payment handshake fully automatic)
bridgenode chat "Hello!" --model deepseek-v4-flash
# Smart routing: auto / eco / premium
bridgenode chat "Analyze this code" --mode auto
# Model list + prices (no payment)
bridgenode models
Options
| Option | Description |
|---|---|
--model |
Explicit model id (see bridgenode models) |
--mode |
auto / eco / premium (smart routing) |
--max-tokens |
Max output tokens (billed upfront) |
--base-url |
Base URL (default: BRIDGENODE_BASE_URL / https://bridgenode.cc/v1) |
--max-per-call / --daily-cap |
Spending policy (fail-closed) |
Configuration (.env)
# Required — your Solana wallet private key (base58)
BRIDGENODE_WALLET_KEY=...
# Optional: BRIDGENODE_BASE_URL, BRIDGENODE_MAX_PER_CALL, BRIDGENODE_DAILY_CAP
Security
- Receipt verification: every response receipt is verified — invalid receipt → error.
- Spending policy (fail-closed): max USD per call / per day — checked BEFORE signing.
Why BridgeNode (vs API keys)
| BridgeNode CLI | Traditional AI APIs | |
|---|---|---|
| Sign-up | None | Account + verification |
| API key | Not needed | Required |
| Billing | Pay-per-request (USDC) | Subscription / credits |
| Fees | Gas sponsored | On you |
| Spending caps | Fail-closed per call/day | Account-level |
FAQ
Do I need SOL? No — fees are sponsored; only the USDC request amount is paid.
Is there an API key? No — your wallet signature (SIWX) is the identity.
Can I cap spending? Yes — --max-per-call / --daily-cap (fail-closed, checked before signing).
Which models? See bridgenode models or https://bridgenode.cc/v1/models.
Requirements
- Python ≥ 3.11
- A Solana wallet with a USDC token account (ATA)
Links
- Website: https://bridgenode.cc
- Models & prices: https://bridgenode.cc/v1/models
- Documentation: https://bridgenode.cc/llms.txt
- Protocol: x402 V2 (https://docs.x402.org)
1 maintainer
Release files for bridgenode-cli 0.1.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bridgenode_cli-0.1.11.tar.gz | 10.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bridgenode_cli-0.1.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.1 kB
Release files / bridgenode_cli-0.1.11.tar.gz
| Download URL | bridgenode_cli-0.1.11.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26409d3cce5e9f3f12fc272f45efc3f976312cec72988f739bbfb45ae60828a1
|
|
BLAKE2b-256 checksum How to use checksums |
4d28b864df44f7fceafee134499ef62b149ef7ed9018b73b9bb59a0c4dfecc60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logRelease files / bridgenode_cli-0.1.11-py3-none-any.whl
| Download URL | bridgenode_cli-0.1.11-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
128e11190c336881f2d4ff033177a2b9185f15b5c80970a246e9fcd19c8244eb
|
|
BLAKE2b-256 checksum How to use checksums |
0e8d70cfe6503783fe760f986b53cce0054138d4cf6becba6dd5bd662647b908
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency log
