Messages and Count Tokens
Claude Messages, message token counting, and a Claude Chat Completions-compatible endpoint.
One token for Claude Code, Codex, Kimi Code, and more. Choose models by task and track usage in one place.
Access 10 public APIs across Messages, Responses, and Chat Completions. Model availability depends on the live directory, credential permissions, and client configuration.
Claude Messages, message token counting, and a Claude Chat Completions-compatible endpoint.
The Responses protocol used by Codex and OpenAI Chat Completions.
Public Chat Completions endpoints for Gemini, GLM, Grok, Kimi, and DeepSeek.
The limited-time offer is scheduled to end September 30, 2026; the checkout page is authoritative for eligibility and Credits received. Every tier has the same Coding model access and differs only in included Credits.
For short projects, test coverage, and occasional use.
For everyday development, multiple repositories, and code review.
For sustained agents, complex refactors, and frequent use.
For team workloads, multi-agent runs, and automation.
Actual consumption depends on the model, context, cache behavior, output, tools, and parallel work.
The setup center provides working configurations for Claude Code, Codex, Kimi Code, OpenClaw, Hermes, Kilo Code, Aider, Qwen Code, and DeepSeek Harness. Each guide pins the matching endpoint, authentication method, protocol, and launch command so you can choose directly by client.
No. All tiers have the same Coding model access. Exact models depend on the live directory and the compatibility range of your client profile.
Uncached input, output, cache writes, and cache reads are metered separately. Long context, tools, and parallel tasks can increase consumption.
No. Coding Applications disable general-balance fallback. You decide whether to purchase again.
Request the live model directory with a valid Coding credential and use an exact model ID marked compatible by your current profile.
First confirm that the token belongs to a Coding Application, then compare the endpoint, protocol, model ID, and launch method with the client guide.
One token, one bill, and per-call usage details. Start with the guide for your client.