Documentation for AI
Give an AI assistant the links below to help it integrate your personal application with the AI gateway. The assistant still needs a tool that can make HTTP requests or run code, network access to your instance, and your explicit authorization to use its token. Reading documentation alone does not grant access, install a skill, or make a model capable of calling tools.
| Resource | Purpose |
|---|---|
| AI gateway guide | Human-readable setup, exact request fields, streaming, quotas and recovery |
| AI gateway Markdown | The same guide and runnable examples, without page chrome or scripts |
| OpenAPI 3.1 | Machine-readable inference endpoints, bearer authentication, requests, responses and errors |
| Integration skill | A portable SKILL.md entrypoint explaining model discovery and safe calls |
| Documentation index | Links to the public human/Markdown documentation |
| Full public documentation | The published user guides in one plain-text document |
Every public guide has a Markdown address: append .md to its canonical
documentation URL. The full document contains public user guides, not private
instance data or internal operator files. The API guide and examples are built
from the same sources used by the human page and application.
Give an assistant the right context
Copy this instruction into an assistant that has the necessary tools:
Read https://aircodezero.com/skills/aircode-ai-gateway/SKILL.md
and https://aircodezero.com/docs/ai-gateway.md.
Integrate my personal application with my own AI gateway.
Read AIRCODE_AI_BASE_URL and AIRCODE_AI_TOKEN from its secret environment.
Do not display those values or send them to the documentation website.
List the available models and use the exact model I select.
Use text-only Chat Completions and disable automatic generation retries.
Explain the current buffered-streaming behavior accurately.For an assistant supporting skill folders, save the linked file as
aircode-ai-gateway/SKILL.md in the skill directory supported by that assistant.
No automatic installation is performed by this website. Other assistants can
read it directly as instructions without installing anything.
Required integration decisions
The base URL and token must come from the same instance. Query /models before
selecting a model; never invent an engine ID or promise access to every model
in a subscription. The user chooses the model and any non-default effort.
Keep credentials in the calling backend. This website has no API playground, token form or proxy to the owner’s instance. Never place a credential in the OpenAPI server URL, a query string or a shared skill file. Configure OpenAPI tools with the user’s instance URL and bearer secret in their private settings.
The current API supports text-only Chat Completions and buffered SSE. It does not expose project tools, interactive coding sessions, Anthropic Messages or Responses. Do not configure a coding agent that requires those protocols as though this text gateway were a complete provider endpoint.