Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.anyone.ai/llms.txt

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

Every request to Anyone must include an API key to identify your account and authorize access. You create tokens in the dashboard, and the same API key works across all endpoint formats — OpenAI, Anthropic Claude, and Google Gemini. The only difference is which header you use to send it.

​
Get your API key

1

Open the dashboard

Navigate to Anyone in a browser, for example https://anyone.ai.
2

Go to API Keys

Click API Keys in the sidebar.
3

Create an API key

Click Add API Key, give it a name, configure any model restrictions or quota limits, then click Submit.
4

Copy the API key

Copy the API key value shown. Anyone only displays the full API key once, so save it somewhere secure.

​
Authentication styles

Anyone supports three authentication styles to match the native format of each API family. All three use the same API key value — only the header name changes.

​
OpenAI-compatible (most endpoints)

Pass your API key as a Bearer API key in the Authorization header. Use this style with all standard endpoints. Applies to: POST /v1/chat/completions, POST /v1/completions, POST /v1/responses, POST /v1/embeddings, POST /v1/audio/*, POST /v1/images/*, POST /v1/rerank, GET /v1/realtime, GET /v1/models 
curl https://api.anyone.ai/v1/chat/completions \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.4",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

​
Anthropic Claude

Pass your API key in the x-api-key header and include the anthropic-version header. Anyone uses these headers to identify requests that should be handled in Claude Messages format. Applies to: POST /v1/messages 
curl https://api.anyone.ai/v1/messages \
  -H "x-api-key: YOUR_TOKEN" \
  -H "anthropic-version: 2023-06-01" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-sonnet-4-6",
    "max_tokens": 1024,
    "messages": [{"role": "user", "content": "Hello"}]
  }'

​
Google Gemini

Pass your API key in the x-goog-api-key header, or as a key query parameter. Both are equivalent. Applies to: POST /v1beta/models/{model}:generateContent 
curl "https://api.anyone.ai/v1beta/models/gemini-3.1-pro-preview:generateContent" \
  -H "x-goog-api-key: YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "contents": [{"parts": [{"text": "Hello"}]}]
  }'

​
Authentication errors

CodeCauseFix
401 UnauthorizedAPI key is missing, malformed, or has been deleted.Check that you are sending the correct header and that the API key value is complete.
403 ForbiddenAPI key exists but does not have access to the requested model.In the dashboard, edit the API key and check its allowed models list.

​
Security

Never include your API key in client-side code, browser JavaScript, or public repositories. If an API key is exposed, delete it immediately in the dashboard and create a new one.
Store API keys in environment variables or a secrets manager, and pass them to your application at runtime. On the server side, treat your Anyone API key with the same care as any other API credential.