AI MODEL AGGREGATION / SMALL-TEAM GUIDES
Authenticate and Connect to TokenBison Unified API Endpoints
Learn how to perform initial authentication, construct structural payloads, and verify the basic model integration path in TokenBison.
The short answer
To connect to TokenBison, you authenticate your requests by passing an API key as a Bearer token in the request header. The platform provides an OpenAI-compatible request shape, allowing you to route text prompts to multiple downstream model providers using a single endpoint and unified authentication scheme.
Authentication Requirements and Header Structure
Every call to TokenBison requires explicit authentication using a private API key. This key must be sent as a Bearer token within the standard authorization header (`Authorization: Bearer $TOKENBISON_API_KEY`). To minimize security risks and prevent exposure, always store your API keys on secure server environments and never embed them into front-end client-side code.
Constructing the Chat Completion Request Payload
TokenBison utilizes an OpenAI-compatible request structure, which unifies the format required to communicate with different back-end models. A standard request is directed to the base URL `https://tokenbison.com/v1/chat/completions`. The JSON payload requires a `model` string specifying the exact target model ID, along with a `messages` array structured with roles and text content.
Verification Workflow for New Integrations
Proposed deployment validation workflow: 1. Generate an API key within the TokenBison console. 2. Configure a server-side test script using standard cURL or HTTP client packages to target the endpoint. 3. Pass the exact model ID retrieved from the catalog inside the payload body. 4. Execute the request and verify that the API returns a standard JSON object containing the expected text generation structure and metadata fields.
Evidence and boundaries
These are documentation references and proposed evaluation workflows, not measured model rankings or a guarantee of savings. Check the current catalog and policies before use.
TokenBison API documentation · reviewed 2026-09-26
Authorization: Bearer $TOKENBISON_API_KEY Base URL https://tokenbison.com/v1 Keep your key on the server. Never expose it in client code. Examples Send a chat completion Select a model below to generate a ready-to-copy example. Select model Loading... cURL Python JavaScript Copy code curl https://tokenbison.com/v1/chat/completions \ -H "Authorization: Bearer $TOKENBISON_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "YOUR_MODEL_ID", "messages": [{"role": "user", "content": "Hello!"}] }' Need help? Include the request ID when available. hi@tokenbison.com
TokenBison verification and limitations · reviewed 2026-09-26
TokenBison Trust Verify before you build on it. Trust comes from checks you can run yourself, not claims you have to take on faith. Get your API key What TokenBison makes visible Information you can inspect at every step. Catalog IDs you can inspect Model IDs are shown in the catalog so you can select and test the exact ID used in your request. OpenAI-compatible requests Use the same request shape in your application and inspect the model and usage fields returned with each response. Clear pricing and usage Review model prices before you call, then track token usage and cost from one console.
Put the guide into practice
Review current model prices, then make a small API request with public or non-sensitive sample data. Compare the output against your own acceptance criteria.