Skip to main content

​
Usage overview

This page explains how the TokenDog API reference is organized and how to approach integration. The reference has three parts — Guides, Endpoints, and Examples. Read this page first, then jump as needed.

​
Basic integration info

  • The unified BaseUrl is https://tokendog.io.
  • To call an endpoint, append its path to the base URL, e.g. https://tokendog.io/v1/chat/completions.

Pick an API format

Start Here — decide which API format you’ll use, then go to the matching endpoint page instead of hopping between unrelated APIs.You’ll find: OpenAI-compatible → /v1/chat/completions, /v1/responses; Claude → /v1/messages; Gemini → /v1beta/...:generateContent.

Understand rate limits

Limits — treat request rate, concurrency, and output size as engineering constraints, not an afterthought.You’ll find: request windows, concurrency caps, over-limit handling.

Locate the failure

Debug — the error-codes page helps you tell quickly whether a failure is auth, params, rate limit, or server-side.You’ll find: auth failures, parameter validation, server-side errors.

​
Suggested reading order

1

Pick the API format

Decide which format you’ll use: OpenAI-compatible, Claude, or Gemini.
2

Integrate the endpoint

Go to the matching endpoint page and build straight from the request structure.
3

Add engineering constraints

Finish with the rate-limit and error-code docs for constraints and debugging.

​
Integration tips

  • Confirm requests go to the unified BaseUrl https://tokendog.io, then append the specific endpoint for your chosen API format.
  • If you already know you’re using OpenAI, Claude, Gemini, Zhipu GLM, or MiniMax, go straight to the matching endpoint pages.
  • If you’re still mapping out your flow, read the examples first, then return to the endpoint pages to implement.
  • If you’re building a unified platform layer, converge provider differences in a server-side gateway.