Blog

Turn a live web page into LLM-ready markdown in one call. POST /v1/fetch, same Flux key and base URL as your chat calls, one field for the URL, one flag for JS-heavy pages. curl + Python, request and response shape, costs and limits. Runs on any paid plan.

Every LLM call is a bet on the same three corners: latency, cost, quality. You can buy two. The real skill is choosing which one to sacrifice, per workload, not once for your whole app.

What LLM routing actually is, the four jobs a router does for you, when routing is the wrong call, how a router differs from a gateway, and how to trust and evaluate any router by what it shows you about one live request.

A 107x price gap between models means most of your API calls pay a premium they never earned. Right-size each prompt and the bill follows the work.

The price-quality frontier moves monthly and your hardcoded default never notices. Decide the model per request instead of baking one into a config file.

The monthly invoice hides everything that matters: which model answered, what each call cost, how much was failed retries. You can't cut what you can't see.

The cheapest model on the price sheet loops four times and still needs a human. Optimise dollars per task that worked, not dollars per million tokens.

The token savings are yours to count. The bad answer is your customer's to screenshot. Cheap is fine; cheap-and-unwatched is the trap.

Wire your app to a single provider and your reliability is capped at theirs. Their bad Tuesday becomes yours, with no second path to route around it.

Wiring models, re-tuning prompts after silent updates, and babysitting every provider's quirks is a recurring tax billed in your best engineers' time.