Skip to content
Terms of Service updated — arbitration, class action waiver, and assignment terms effective August 18, 2026.

From decision to evidence

Complete one AI API job, then verify what happened.

These guides start with the workload intent, use current product and model records, and end at a response plus an Activity check—not a generic signup screen.

Four curated workflows

Choose the job you need to finish.

Each page has a bounded outcome, execution steps, and a verification checklist.

Model implementation guide

Call Kimi K3 through one OpenAI-compatible endpoint

Move from model evaluation to a verified Kimi K3 response, then confirm the matching request record before integrating a larger workload.

Operator job
You want to test Kimi K3 without building a provider-specific client path first.
Intended audience
Application developers evaluating a single model path before integration.
Open guide

Coding-agent gateway guide

Put Claude Code behind a governed Anthropic-compatible path

Validate a coding-agent request path, keep credentials out of project files, and inspect the resulting usage before rolling the configuration across a team.

Operator job
You want a compatible Claude Code path with centralized key, policy, and usage controls.
Intended audience
Platform engineers setting up a governed coding-agent workflow.
Open guide

Reliability workflow

Design multi-provider fallback without hiding the decision path

Separate model choice, provider routing, and failure policy so fallback behavior can be tested, observed, and changed without rewriting the client.

Operator job
You need a fallback path but still want to know which model and route served each request.
Intended audience
Reliability owners designing explicit multi-provider failure handling.
Open guide

Spend-control workflow

Attribute LLM spend by workspace before budgets blur

Create an ownership boundary that connects keys, model requests, usage records, and quota decisions to the workload that caused them.

Operator job
Multiple teams or applications share model access and the monthly total no longer explains who consumed it.
Intended audience
Engineering and finance owners who need a reviewable workspace boundary.
Open guide

Put the guide into production

Choose the product surface for the next step.

Start with the API Gateway for a governed multi-provider path, then use the model catalog to verify the exact model before you send a production request.