
How an AI agent funds and pays for its own API calls
Registration, balance and top-up as three HTTP calls instead of three web forms. The flow, the caps that keep it safe, and when a human is still required.
Guides, model deep-dives, and how-tos for building with every AI model through one API.

Registration, balance and top-up as three HTTP calls instead of three web forms. The flow, the caps that keep it safe, and when a human is still required.

Three web context endpoints on the balance that already pays for inference. What each one costs, when to reach for which, and what you stop maintaining.

JSON mode is three different guarantees wearing one name. What ports between providers, what gets silently ignored, and why you validate anyway.

Veo, Seedance, Kling, Hailuo and Grok Imagine priced per second of output. A five-second clip runs from thirty cents to three dollars. Where the gap goes.

Output price dominates an agent's bill, not input price. Four catalog fields that decide whether a model can drive an agent at all, and how to read them.

Keep the OpenAI client, change three values, call Claude. What survives the translation, what has no equivalent, and when to use the native SDK instead.

The request format ports. Tool calling does not. Opaque IDs, hidden state, silently dropped context and the 400 that only fires on the second turn.

Two fields in Cline settings and every model becomes selectable. The setup, the three fields people get wrong, and how to switch models mid-task.

OpenRouter, LiteLLM, Portkey, Helicone and ApexApi solve different problems. Five questions that decide it, and an honest answer on where each one wins.