Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ai-stats.phaseo.app/llms.txt

Use this file to discover all available pages before exploring further.

Use this page when you want to get moving quickly and do not yet know which part of the docs you need. You can think of AI Stats in one sentence:
  • one API for models, providers, routing, pricing, and async AI workflows

​
Fastest path

If you only want the shortest route to first success:
  1. Create an API key in the dashboard.
  2. Send one request to a :free model.
  3. Confirm the response shape.
  4. Then choose the integration path that matches your app.
Free models can be used with zero deposited credits. Paid models require available wallet balance.

​
First request

curl https://api.phaseo.app/v1/responses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "google/gemma-3-27b:free",
    "input": "Reply with: docs ready",
    "temperature": 0
  }'
If that works, go to the Quickstart and keep building from there.

​
Choose your starting point

If you already have an integration or toolchain, start from the closest match instead of reading the docs from the top.

I'm coming from OpenAI

Keep the OpenAI-compatible shape, swap the base URL and key, and verify model support.

I'm coming from OpenRouter

Move your existing routing setup over with parity checks and staged rollout guidance.

I'm sending raw HTTP requests

Start from cURL and the Responses API, then move into the endpoint reference when needed.

I'm using the TypeScript SDK

Use the TypeScript client as your main entry point for Responses, chat, images, audio, and more.

I'm using the Python SDK

Start from the Python client if your integration lives in scripts, workers, backends, or notebooks.

I'm using the AI SDK

Connect Vercel AI SDK apps to AI Stats without rebuilding your prompt or model flow.

I'm using Codex or Claude Code

Set up the gateway, Docs MCP, and coding-agent integrations from one place.

I just need examples

Jump straight to copy-paste requests and sample projects if you already know the basics.

​
What are you trying to do?

Make my first request

Start with one successful text request, then learn where to read output and debug failures.

Use an SDK

Pick the client SDK that matches your stack and start from real wrapper examples.

Connect a coding agent

Set up Codex, Claude Code, OpenCode, or Docs MCP against AI Stats.

Migrate an existing integration

Move from OpenAI, OpenRouter, Anthropic, Vercel, LiteLLM, or another gateway.

Control routing and providers

Choose provider order, ranking, regional offers, presets, and failover behavior.

Run async jobs

Build video, music, and batch workflows with polling, webhooks, and status retrieval.

​
Most useful pages

Quickstart

The shortest path from signup to first successful request.

API Reference

Base URL, auth, endpoint families, and endpoint-by-endpoint request details.

Examples

Copy-paste requests and sample projects across common workflows.

Cookbook

Scenario-driven recipes for routing, presets, async jobs, search, and agent workflows.

Authentication

Key format, bearer headers, and common auth mistakes.

Error Handling

Understand failed requests quickly and fix the common causes.

​
If you are using agents

AI Stats is set up to work well with coding agents and AI tools, not just humans reading docs in a browser. Start here:

Docs MCP

Let Codex, Claude Code, Cursor, or VS Code search the live AI Stats docs while they work.

skill.md

Capability summary for agents that need to understand what AI Stats can do and how requests work.

Integrations

Set up coding tools and editor workflows around the gateway.

Agent SDK

Build tool-using, gateway-backed agent loops across the supported SDK languages.

​
Explore models and providers

Use the data surfaces when you need to choose before you build:

Browse Models

Find models, pricing, context windows, capabilities, and provider offers in one place.

Compare Models

Compare performance, cost, and metadata side by side before you commit to one route.
Last modified on May 19, 2026