Skip to main content
1API Club

Quickstart

Make a small request, then verify the record.

Make a small request, then verify the record before sending sustained workload traffic.

LoginChoose model & pricing
Docs menu

Four steps

Follow four linear steps.

The steps are deliberately linear so the model choice, request, and Usage review stay easy to compare.

  1. 01Login and create a dedicated API keyLogin, open the console, and create a key for this workload. Keep it in a server-side environment variable.
  2. 02Choose a Published model, Delivery Lane, and endpointUse Pricing to choose the request combination, then make sure the workspace has Credits before calling it.
  3. 03Send one small requestSet the base URL and bearer key, replace the model placeholder, and use a short prompt before real traffic.
  4. 04Verify the Usage recordCheck the model, Delivery Lane, input and output tokens, and charge after the request completes.

Prepare

Set the endpoint and credentials.

Begin with a Published combination from Pricing. The selected model and Delivery Lane determine which endpoint can receive the request.

Base URL
https://api.1api.club/v1
Authorization
Authorization: Bearer $API_KEY

Request

Send a small request for the selected endpoint.

Use the request shape for the selected Published model and endpoint. Keep the first request small before you move real traffic.

Chat Completions request
curl https://api.1api.club/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "YOUR_PUBLIC_MODEL_ID",
    "messages": [
      { "role": "user", "content": "Write one short release note." }
    ]
  }'

Usage records

Verify the Usage record.

The HTTP response confirms the request completed. The Usage record is the check for what the selected workload actually used and charged.

Open Usage recordsOpen Credits
Request details
Verify the model and Delivery Lane.
Usage
Verify input and output tokens.
Charge
Verify the settled charge against the request.

Next

Continue from the verified request.

Return to Docs for task routing or use the Reference to choose another approved endpoint.

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