Platform API

Every product surface that the dashboard uses is also on the gateway under /v1, authenticated with the same Authorization: Bearer opd_… key. Chat, assistants, and workflow LLM steps debit that key and the org’s prepaid credits.

GET /v1/catalog

Returns the live endpoint list, grouped. Start there when you add a new integration — new features show up on this catalog instead of a second undocumented API.

Auth and usage

GET /v1/account returns the org, plan, add-ons, spendable credit buckets, and the calling key’s spend cap. GET /v1/account/balance is the short form. GET /v1/usage is the daily rollup billed to this org.

A 402 means the key or org cannot cover the estimated cost. Top up on Billing, or raise the key spend cap.

Build on top

tsCopy
import { OpenDoor } from "@opendoor/sdk";

const client = new OpenDoor({
  apiKey: process.env.OPENDOOR_API_KEY,
  baseURL: "https://opendoor-gcp.web.app",
});

const catalog = await client.catalog.list();
const account = await client.account.get();

const assistant = await client.assistants.create({
  name: "Support",
  modelId: "opendoor/auto",
  systemPrompt: "You answer from the product docs.",
});

const reply = await client.assistants.chat(assistant.id, {
  messages: [{ role: "user", content: "How do I create an API key?" }],
});

Python:

pythonCopy
from opendoor import OpenDoor

client = OpenDoor(base_url="https://opendoor-gcp.web.app")  # OPENDOOR_API_KEY
print(client.account.balance())
print(client.assistants.chat(assistant_id, messages=[{"role": "user", "content": "Hello"}]))

CLI:

bashCopy
bun run od -- catalog
bun run od -- account
bun run od -- assistants create --name Support --model opendoor/auto
bun run od -- assistants chat --id "$ID" --message "Hello"

Groups

Dashboard session routes stay for login, Stripe checkout, and SSO. Everything a builder needs to ship on top of OpenDoor is on this key.

Related

• Assistants
• Agents
• Usage
• Chat completions
• TypeScript SDK