Docs

Developer docs for a small, verifiable request.

Choose one small request path, verify its Usage record, then expand only after the configuration is clear.

Docs menu

Tasks

Choose the next task.

Use Quickstart for the first request or API Reference to inspect an approved protocol capability.

OverviewChoose a small request path and verify its Usage record.Current QuickstartCreate a key, choose a Published request, and verify it.Open API referenceApproved capability routes, request shapes, and limits.Open

Request check

Confirm the connection with a small read.

Keep the base URL and bearer key in your server-side configuration. Begin with a model lookup before workload traffic.

List models

curl https://api.1api.club/v1/models \
  -H "Authorization: Bearer $API_KEY"

Base URL: https://api.1api.club/v1
Authorization: Authorization: Bearer $API_KEY
First check: Use a Published model, Delivery Lane, and endpoint before sending a small request.

Protocol scope

Start from the protocol your workload already uses.

The reference lists only protocol capabilities from the shared public inventory. Endpoint publication coverage remains specific to the selected model and Delivery Lane.

OpenAI-compatible

12 approved capability groups. See the API Reference for routes, request shapes, and client-facing limits.

Anthropic

2 approved capability groups. See the API Reference for routes, request shapes, and client-facing limits.

Gemini

6 approved capability groups. See the API Reference for routes, request shapes, and client-facing limits.

Verify

Keep the first request observable.

Use Pricing to select the model and Delivery Lane, then compare its prices before sustained traffic.

Before sending: Confirm the endpoint is Published and the workspace has Credits.
After sending: Review the Usage record for model, Delivery Lane, tokens, and charge.