BSV intelligence.
In your application.

1. Keep the key on your server. Create a key in your account, then supply it through BITGENIUS_API_KEY.
2. Discover the model. Use GET /v1/models before choosing a model alias. This preview defines bitgenius.
3. Start with text. Send a request, inspect the output and usage, then add streaming or your own tools.

# BitGenius developer API preview.
curl https://api.bitgenius.net/v1/responses \
  -H "Authorization: Bearer $BITGENIUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "bitgenius",
  "input": "Explain BRC-100 wallet permissions with sources.",
  "store": false
}'

JavaScript and Python examples use the OpenAI client’s custom base URL. Contract compatibility is bounded by the matrix below; these are integration recipes, and live SDK interoperability remains a release check.

Corpus retrieval supplies grounding and provenance. Built-in web search is unavailable in this preview; current facts require separate verification. The model is instructed to disclose when current confirmation is unavailable. Check cited sources before relying on an answer.

Responses uses flat function definitions and function_call_output items. Chat Completions nests definitions under function and returns tool outputs as role: "tool" messages. Return each call’s exact ID and retain the previous messages and output items.

const tools = [{
  type: "function",
  name: "lookup_protocol",
  description: "Read a protocol description from my approved local index.",
  parameters: {
    type: "object",
    properties: { number: { type: "integer" } },
    required: ["number"],
    additionalProperties: false,
  },
}];

const first = await client.responses.create({
  model: "bitgenius",
  input: "Find BRC-100 in my protocol index.",
  tools,
  tool_choice: "auto",
  store: false,
});

// Keep the original input and every output item in client-owned history.
// Validate the tool name and arguments before running your own function.
const calls = first.output.filter(item => item.type === "function_call");
const outputs = [];
for (const call of calls) {
  if (call.name !== "lookup_protocol") throw new Error("Unexpected tool");
  const args = JSON.parse(call.arguments);
  if (!Number.isInteger(args.number)) throw new Error("Invalid arguments");
  const output = await lookupApprovedProtocol(args.number);
  outputs.push({ type: "function_call_output", call_id: call.call_id,
    output: JSON.stringify(output) });
}
if (calls.length) {
  const next = await client.responses.create({
    model: "bitgenius",
    input: [
      { role: "user", content: "Find BRC-100 in my protocol index." },
      ...first.output,
      ...outputs,
    ],
    tools,
    store: false,
  });
  console.log(next.output_text);
}

This example assumes your application supplies lookupApprovedProtocol. In production, constrain allowed arguments and output size, and obtain user approval for consequential actions. A tool declaration does not grant permission.

Unsupported input is rejected explicitly. The preview does not silently discard unknown options or substitute a hosted tool for your function.

Key management, credit enforcement, rate limits, and production privacy behavior must pass the release gate before live use. store: false controls this API’s response persistence contract; it is not a guarantee about all provider processing. Do not send secrets in prompts or expose a key in a generated frontend.

Download developer toolkit ↓ · Download developer skill ↓

Extract the toolkit locally, review its included tooling guide, and follow the install instructions. These packages contain only public developer guidance and local tooling; downloading them does not install a skill or grant API access.

tar -xzf bitgenius-developer-toolkit.tar.gz
node bitgenius-developer-toolkit/tools/developer-mcp/server.mjs

{
  "mcpServers": {
    "bitgenius-developer": {
      "command": "node",
      "args": ["/absolute/path/bitgenius-developer-toolkit/tools/developer-mcp/server.mjs"]
    }
  }
}

• Both generation surfaces pass text, function round trip, validation, and SSE contract tests.
• Account ownership, expiry, revocation, reservation, finalization, and cancellation are verified with synthetic credits.
• JavaScript and Python client recipes are exercised against the same API contract.
• Operational limits, privacy details, developer hostname, and release approval are confirmed.