Docs
API docs for your first working integration.
Start with the available OpenAI-compatible API, a bearer key, and a public model id.
Connection
Use one public base URL and one bearer key.
Keep these values close while wiring an SDK, agent runtime, or workflow.
- Base URL
- https://api.1api.club/v1
- Auth header
- Authorization: Bearer $API_KEY
- Available today
- OpenAI-compatible API.
- First endpoint
- GET /v1/models
Availability
Start from the endpoint that is ready for your workload.
The public API reference separates ready endpoints from limited and unavailable workloads.
First check
Confirm the key and base URL before sending workload traffic.
Use the model list to confirm connectivity, then move to Quickstart for a completion request.
curl https://api.1api.club/v1/models \
-H "Authorization: Bearer $API_KEY"Integration path
Wire the integration in small, observable steps.
The docs stay close to operational checks: key, endpoint, model id, request result, usage, and credits.
- 01Create a scoped keyGenerate an API key in the console and keep the secret out of client-side code.
- 02Choose a supported endpointStart with the OpenAI-compatible API and confirm any workload-specific endpoint in the API reference.
- 03Verify usageCheck the usage and credits views before sustained automation traffic.
Integration patterns
Built for API-heavy automation.
Start from the client shape your automation already uses, then verify usage before scaling traffic.
- Agent clients
- Point OpenAI-compatible SDKs or agent runtimes at the API base URL and keep the bearer key pattern.
- n8n workflows
- Use HTTP request or OpenAI-compatible nodes with the API base URL and a scoped API key.
- Scripts and jobs
- Keep curl and SDK calls small: base URL, bearer key, model id, and the endpoint your job already uses.
Boundaries
The docs describe public behavior only.
Unavailable resources return documented errors instead of being treated as available product behavior.
- Use
- OpenAI-compatible endpoints that the API reference marks as ready or limited.
- Check
- Model availability, endpoint status, pricing, usage, and credits before sustained workload traffic.
- Avoid assuming
- Files, batches, resource storage, uptime guarantees, or endpoints marked not available.
Pages
Move through the docs by task.
These static pages are the first public docs set and stay separate from project planning documents.