OpenOpen8 uses a single token for all endpoints. Pass it as a Bearer token, x-api-key, or x-goog-api-key depending on the API format you are using.
Every request to OpenOpen8 must include a token to identify your account and authorize access. You create tokens in the dashboard, and the same token works across all endpoint formats — OpenAI, Anthropic Claude, and Google Gemini. The only difference is which header you use to send it.
OpenOpen8 supports three authentication styles to match the native format of each API family. All three use the same token value — only the header name changes.
Pass your token as a Bearer token 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
Pass your token in the x-api-key header and include the anthropic-version header. OpenOpen8 uses these headers to identify requests that should be handled in Claude Messages format.Applies to:POST /v1/messages
Never include your token in client-side code, browser JavaScript, or public repositories. If a token is exposed, delete it immediately in the dashboard and create a new one.
Store tokens in environment variables or a secrets manager, and pass them to your application at runtime. On the server side, treat your OpenOpen8 token with the same care as any other API credential.