dominusnode-camel
CAMEL-AI tools for the DominusNode AI-agent relay network (v2). Agents fetch the web through
exit IPs contributed by other operators, pay per GB from a prepaid wallet (live prices from
dominusnode_network_pricing, nothing hardcoded), and can earn by contributing their own IP
with the DominusNode node agent.
Built on the official dominusnode Python SDK v2: all HTTP, SSRF and
DNS-rebinding checks, gateway username flags and validation come from the SDK.
pip install dominusnode-camel
export DOMINUSNODE_API_KEY=dn_live_... # read from the environment, never a tool argument
Defaults: API https://api.dominusnode.daedalusdevelopmentgroup.com, relay gateway proxy.dominusnode.daedalusdevelopmentgroup.com. Override with DOMINUSNODE_BASE_URL / DOMINUSNODE_PROXY_HOST.
Usage
from camel.agents import ChatAgent
from dominusnode_camel import DominusNodeToolkit
agent = ChatAgent(
system_message="You browse through the DominusNode relay network. Check pricing first.",
tools=DominusNodeToolkit().get_tools(), # 19 camel FunctionTools
)
print(agent.step("Fetch https://example.com from a residential exit in the US").msgs[0].content)
DominusNodeToolkit is a camel.toolkits.BaseToolkit; each tool is a FunctionTool whose
OpenAI schema comes from the method signature and Google-style docstring. Errors come back
as scrubbed Error: ... strings.
The 19 tools
| # | Tool | What it does | SDK call |
|---|---|---|---|
| 1 | dominusnode_fetch |
Fetch a public URL through the relay (GET/HEAD; country, ip_class, session_id, allow_http) | proxy.fetch |
| 2 | dominusnode_proxy_url |
Gateway proxy URL/username for your own client (key shown as a placeholder) | proxy.build_username |
| 3 | dominusnode_network_policy |
Relay policy: ports, blocked targets, sanctioned countries | network.policy |
| 4 | dominusnode_network_pricing |
Live per-GB prices by IP class and node earning shares | network.pricing |
| 5 | dominusnode_network_stats |
Online nodes, countries, IP classes | network.stats |
| 6 | dominusnode_balance |
Prepaid wallet balance | wallet.get_balance |
| 7 | dominusnode_transactions |
Wallet transactions | wallet.get_transactions |
| 8 | dominusnode_topup_crypto |
Crypto top-up invoice ($10-$1,000) | wallet.top_up_crypto |
| 9 | dominusnode_check_payment |
Crypto invoice status | wallet.get_crypto_status |
| 10 | dominusnode_usage |
Bandwidth usage and cost | usage.get |
| 11 | dominusnode_active_sessions |
Active sessions (no IPs) | sessions.get_active |
| 12 | dominusnode_report_session |
Report a bad session | sessions.report |
| 13 | dominusnode_node_list |
Your relay nodes | nodes.list |
| 14 | dominusnode_node_tier |
Node-operator tier and share | nodes.tier |
| 15 | dominusnode_node_setup_guide |
Steps to earn by running the node agent | static text |
| 16 | dominusnode_credits_balance |
Earned node credits | credits.balance |
| 17 | dominusnode_credits_convert |
Convert credits into wallet balance | credits.convert |
| 18 | dominusnode_payouts_list |
On-chain payouts | payouts.list |
| 19 | dominusnode_x402_info |
x402 micropayment info | x402.get_info |
Security
- The API key comes from
DOMINUSNODE_API_KEY(or constructor config). It is never a tool argument, never in a tool schema and never in tool output;dominusnode_proxy_urlreturns a<DOMINUSNODE_API_KEY>placeholder. - Every result and error is scrubbed of
dn_live_/dn_test_/dn_node_/dn_proxy_keys and JWTs. dominusnode_fetch(via the SDK): GET/HEAD only, ports 80/443, private/local hosts and DNS-rebinding refused, redirects not followed, 10 MB cap, sanctioned countries refused. Plaintexthttp://needsallow_http=trueand is visible to the exit node.- Signed flows (node registration, withdrawals, payout wallet) are not LLM tools: use the DominusNode MCP server, the node agent, or the SDK with a signer key file.
Configuration env vars: DOMINUSNODE_API_KEY, DOMINUSNODE_BASE_URL, DOMINUSNODE_PROXY_HOST,
DOMINUSNODE_PROXY_PORT.
Development
pip install -e ../../sdks/python -e '.[dev]'
pytest
License
MIT
Metadata
Release files for dominusnode-camel 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dominusnode_camel-2.0.0.tar.gz | 12.7 kB | Without provenance | Details for dominusnode_camel-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dominusnode_camel-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for dominusnode_camel-2.0.0-py3-none-any.whl |
Total release size: 24.2 kB
Release files / dominusnode_camel-2.0.0.tar.gz
| Download URL | dominusnode_camel-2.0.0.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
54434a0db40e34bac929d9dd98b5f1012d510c52367b7471dc627fb6908189e9
|
|
BLAKE2b-256 checksum How to use checksums |
ab197ec860038f2f9128fcc90b34bb0caadaf94ba89500ff7bb0f22775660e91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.18
|
Release files / dominusnode_camel-2.0.0-py3-none-any.whl
| Download URL | dominusnode_camel-2.0.0-py3-none-any.whl |
|---|---|
| Size | 11.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fde04989dc23dfe7e3be31e317f39bb1255c44221f98d153844e2819a56b301a
|
|
BLAKE2b-256 checksum How to use checksums |
4d6b506777503b2db92e4b8157fb320909810808e4ace0325514fe173e881b5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.18
|
Security for dominusnode-camel 2.0.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.