Developer documentation

Run your first model request.

InfraCloud Run exposes OpenAI-, Anthropic-, and Gemini-compatible routes behind one account and one API-key workflow.

1. Create a key

Open API keys

2. Pick a contract

Use the SDK format your application already understands.

3. Send a request

Keep the key server-side and pass it with each API call.

Base URLs

OpenAI compatible	https://infracloud.run/api/v1
Anthropic compatible	https://infracloud.run/api/v1
Codex compatible	https://infracloud.run/api/v1/codex
Gemini compatible	https://infracloud.run/api/v1/gemini

Chat completion

curl https://infracloud.run/api/v1/chat/completions \
  -H "Authorization: Bearer ck_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.3-codex",
    "messages": [{"role": "user", "content": "Explain this trace"}]
  }'

Anthropic messages

curl https://infracloud.run/api/v1/messages \
  -H "x-api-key: ck_YOUR_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-sonnet-4-6",
    "max_tokens": 1024,
    "messages": [{"role": "user", "content": "Draft a runbook"}]
  }'

Operational notes

API keys are shown in full only when they are created.
Use server-side environment variables; never ship keys to a browser.
Responses include standard HTTP status codes and structured errors.
Usage and latency are visible in the authenticated dashboard.