Quickstart
TokenForFree is currently in Early Access. The interface below is the planned API contract, not a production-ready endpoint.
Authentication
Planned requests use a bearer token in the Authorization header.
Authorization: Bearer $TFF_API_KEYKeys are not being issued in the current release.
Base URL
https://api.tokenforfree.com/v1This hostname is reserved for the planned API. It may not accept requests yet.
Chat Completions
The planned interface follows the familiar OpenAI Chat Completions request shape.
from openai import OpenAI
client = OpenAI(
base_url="https://api.tokenforfree.com/v1",
api_key="YOUR_TFF_API_KEY",
)
response = client.chat.completions.create(
model="tff/free",
messages=[
{"role": "user", "content": "Hello!"}
],
)
print(response.choices[0].message.content)Models
Routing profiles keep application code stable while the underlying eligible free source can change.
tff/freeBalanced automatic routing previewtff/free-fastLatency-oriented routing previewtff/free-reasoningReasoning-oriented routing previewErrors
The planned API will use standard HTTP status codes and a compact JSON error body.
401Missing or invalid API key429Free allocation temporarily exhausted503No eligible free model currently availableError semantics may change before API launch.
Rate Limits
Limits will depend on available free supply and may vary by route. Exact policies will be published with the backend launch.
FAQ
Is the API live?
Not yet. The website documents the intended interface while routing and key issuance are being built.
Will it require a credit card?
The free access path is designed to start without one.
Are the models on the Models page real-time?
No. They are clearly marked design mock data until the real model feed is connected.
Is TokenForFree OpenAI compatible?
The planned request format is OpenAI compatible. Compatibility will be verified and documented when the API launches.