API reference
Public API reference.
Inspect only the approved protocol capabilities, then select a Published endpoint for the model and Delivery Lane you plan to use.
Docs menu
Connection
Send requests with the public base URL and bearer key.
All request examples use the same public base URL and bearer key. The selected protocol determines the route and request body.
POST https://api.1api.club/v1/chat/completions
Authorization: Bearer $API_KEY
Content-Type: application/json- Base URL
- https://api.1api.club/v1
- Authentication
- Authorization: Bearer $API_KEY
- Publication coverage
- Select a model and Delivery Lane whose endpoint is Published before sending a request.
OpenAI-compatible
OpenAI-compatible API capabilities.
These OpenAI-compatible routes are listed from the public capability inventory. Their publication coverage remains specific to the selected model and Delivery Lane.
- Models list and retrieve
- /v1/models or /v1/models/{model}
- Chat Completions JSON and SSE
- /v1/chat/completions
- Responses JSON and SSE
- /v1/responses
- Responses compact
- /v1/responses/compact
- Responses input token counting
- /v1/responses/input_tokens
- Responses WebSocket
- /v1/responses
- Legacy Completions
- /v1/completions
- Embeddings
- /v1/embeddings
- Moderations
- /v1/moderations
- Image generation and edit
- /v1/images/generations or /v1/images/edits
- Audio transcription, translation, and speech
- /v1/audio/transcriptions or /v1/audio/translations or /v1/audio/speech
- Realtime WebSocket
- /v1/realtime
Anthropic
Anthropic API capabilities.
These Anthropic routes are listed from the public capability inventory. Their publication coverage remains specific to the selected model and Delivery Lane.
- Models list and retrieve
- /v1/models or /v1/models/{model}
- Messages JSON and SSE with client-defined tools
- /v1/messages
Gemini
Gemini API capabilities.
These Gemini routes are listed from the public capability inventory. Their publication coverage remains specific to the selected model and Delivery Lane.
- Models list and retrieve
- /v1beta/models or /v1beta/models/{model}
- generateContent JSON
- /v1beta/models/{model}:generateContent
- streamGenerateContent SSE
- /v1beta/models/{model}:streamGenerateContent
- countTokens
- /v1beta/models/{model}:countTokens
- Function calling
- /v1beta/models/{model}:generateContent
- Google Search and Maps Grounding
- /v1beta/models/{model}:generateContent or /v1beta/models/{model}:streamGenerateContent
Request and response
Match the response form to the endpoint action.
Use the response form documented for the endpoint you selected. Streaming is an endpoint action, not a protocol-wide promise.
Errors and limits
Check the request boundary before retrying.
Use the response error as the client contract and avoid retrying a configuration error as though it were a transient request failure.
- Authentication
- Send a workspace API key in the Authorization bearer header.
- Publication coverage
- Choose a model, Delivery Lane, and endpoint that are marked Published before sending the workload request.
- Credits
- Ensure the workspace has Credits before sending a request that can incur a charge.
- Request limits
- Keep the request within the endpoint schema and handle documented HTTP errors in the client.
Next
Turn an endpoint choice into a verified request.
Open Quickstart to make a small request, then use Usage records to verify its model, Delivery Lane, tokens, and charge.