B3IQ keeps hand-authored endpoint contracts for its supported HTTP surface. These specs are not SDKs, adapters, or client libraries.

Specs

SpecFileCovers
Hosted Gateway API./openapi/hosted-gateway.openapi.yamlPublic /v1/api/models, /v1/api/stats, /v1/api/pricing, authenticated OpenAI-compatible chat, plus B3IQ-native private jobs, receipts, and public settlement/payout read APIs
Local Host-Agent API./openapi/local-host-agent.openapi.yamlLocal health, OpenAI-compatible chat, models and model profiles, embeddings, image, audio, and rerank endpoints, receipts, and receipt submission

Generated API reference

HolyDocs reads both OpenAPI files and generates endpoint pages under /api/hosted-gateway and /api/local-host-agent. They are listed under the API Documentation tab by tag, method, and endpoint summary.

Use the hand-written developer guides first when you need context, safe key handling, or product-level explanation. Use generated reference pages when you need exact request/response schemas.

Contract scope

Endpoint contracts only

The OpenAPI specs describe HTTP contracts. They do not promise maintained SDKs, product adapters, or generated clients.

API Overview

Start with the high-level API map.

Learn More
Hosted Gateway

Use hosted OpenAI-compatible examples.

Learn More
Local API

Call local host-agent endpoints.

Learn More
Ask a question... ⌘I