DominusNode for Google Gemini / Vertex AI

Gives agents the DominusNode AI-agent relay network: fetch public web pages through exit IPs contributed by other agents' nodes, pay per GB from a prepaid crypto wallet, and earn by contributing your own IP with the node agent. Built on the official DominusNode SDK v2; HTTP, SSRF/DNS-rebinding protection, OFAC refusal and credential scrubbing all come from the SDK.

Install

npm install @dominusnode/gemini-functions   # TypeScript
pip install dominusnode-gemini              # Python

Configuration

Usage

This package has a TypeScript part (@dominusnode/gemini-functions, on @dominusnode/sdk v2) and a Python part (dominusnode-gemini, on the dominusnode SDK v2). Both expose the same 19 declarations, kept identical to functions.json by tests in each language. Declarations use Gemini's schema subset (uppercase types, enum with format: "enum").

TypeScript (@google/genai)

import { GoogleGenAI } from "@google/genai";
import { createDominusNodeFunctionHandler, functionDeclarations } from "@dominusnode/gemini-functions";

const ai = new GoogleGenAI({});
const handle = createDominusNodeFunctionHandler();          // key from DOMINUSNODE_API_KEY
const res = await ai.models.generateContent({
  model: "gemini-2.5-flash",
  contents: "Fetch https://example.com from a German exit",
  config: { tools: [{ functionDeclarations }] },
});
for (const call of res.functionCalls ?? []) {
  const result = await handle(call.name!, call.args ?? {});
  // reply with { functionResponse: { name: call.name, response: JSON.parse(result) } }
}

Python (google-genai)

from google import genai
from google.genai import types
from dominusnode_gemini import create_dominusnode_function_handler, function_declarations

handle = create_dominusnode_function_handler()      # key from DOMINUSNODE_API_KEY
tool = types.Tool(function_declarations=function_declarations())
resp = genai.Client().models.generate_content(
    model="gemini-2.5-flash", contents="What does residential relay traffic cost per GB?",
    config=types.GenerateContentConfig(tools=[tool]))
for call in resp.function_calls or []:
    result = handle(call.name, call.args or {})

Handlers return JSON strings; errors are {"error": "..."} with credentials scrubbed.

Tools (v2 standard set, 19)

Notes for agents:

• Prices are never hardcoded: call network_pricing for the live per-GB price by IP class (residential, dc, mobile).
• fetch is GET/HEAD only on ports 80/443, follows no redirects and caps bodies at 10 MB. Plaintext http:// needs allow_http and is visible to the exit node.
• Routing: country (ISO code; sanctioned countries refused), ip_class, session_id (sticky exit).
• Signing flows (node register, withdraw, payout wallet) are deliberately not tools here; use the node agent CLI, the DominusNode MCP server, or the SDK with a signer key file.

Development (JS part)

@dominusnode/sdk 2.x may not be on npm yet; link the in-repo SDK for local builds and tests:

(cd ../../sdks/node && npm ci && npm run build)
npm install && npm run link-sdk
npx tsc && npx vitest run

functions.json is generated from core.ts; after changing a spec rebuild and regenerate it (node -e 'import("./dist/handler.js").then(m=>require("fs").writeFileSync("functions.json", JSON.stringify(m.functionDeclarations,null,2)+"\n"))'). Tests in both languages fail if it is stale.

Testing

pip install -e ../../sdks/python -e '.[dev]'   # or npm install for the JS part
python -m pytest -q python_tests

License

MIT