Integration options
The public Ambient API page describes three supported integration paths. The first is the official OpenAI SDK, pointed at Ambient as the base URL. This is the cleanest option if your codebase already assumes OpenAI client semantics and you want minimal integration friction.
The second is the official Anthropic SDK, again pointed at Ambient as the base URL. This keeps the Anthropic Messages API shape while routing execution through Ambient infrastructure.
The third is direct HTTP against the Ambient endpoint. This is the most flexible option and the one the docs call out for advanced control, especially when you want to tune reasoning behavior or work directly with the interactive docs and playground.
Reuse the OpenAI client shape.
Ideal when your application already speaks OpenAI natively and you only want to swap the base URL while keeping the rest of the integration familiar.
from openai import OpenAI
client = OpenAI(
base_url="https://api.ambient.xyz/v1",
api_key=AMBIENT_API_KEY,
)Use the Messages API format.
Ideal when your stack already relies on Anthropic-style message payloads and you want the same interface style against Ambient infrastructure.
from anthropic import Anthropic
client = Anthropic(
base_url="https://api.ambient.xyz",
api_key=AMBIENT_API_KEY,
)Full request control.
Best when you want explicit control over the raw request surface, tighter tuning, or easier interoperability outside the canonical SDKs.
curl https://api.ambient.xyz/v1/chat/completions \
-H "Authorization: Bearer $AMBIENT_API_KEY" \
-H "Content-Type: application/json"Reference resources
The public docs link to both the interactive API documentation and a ReDoc-rendered reference, along with implementation examples. This page keeps the stable overview on-site and routes endpoint-level detail to the live sources.
Interactive API documentation
Browse endpoints, inspect request and response schemas, and try requests directly in the browser.
Reference rendering
Use the ReDoc view when you want a cleaner linear pass through the API surface and schema details.
Provision access
Create and manage API credentials before integrating any of the SDK or direct-call paths.
Implementation notes
- The docs recommend direct calls when you want more explicit control over reasoning tokens, speed, and latency tradeoffs.
- The API page links to a worked Python demo and a condensed markdown reference for faster implementation handoff.
- The on-site reference is intended as the overview layer; evolving endpoint detail lives in the live interactive docs.