Everything tagged ai-gateway

3 published articles · newest first · server-rendered

Take this folder folder (.zip) markdown manifest json the whole site

Also filed under: cloudflare 3 · tooling 3 · billing 1 · coding-agents 1 · llm-routing 1 · model-pricing 1 · unified-billing 1 · workers-ai 1

  1. Two id families, a 23x price gap: choosing a coding model on Cloudflare
    Every coding-relevant model Cloudflare will run, with the id, context window and per-million price read from the live catalogue on 2026-07-26, the failures that decide the choice, and six models measu
  2. Cloudflare Unified Billing: the 5% is on the credits, and the 402 is one gateway toggle
    Route model traffic through Cloudflare with no provider keys: what the 5% credit fee costs on a real monthly volume, the exact request that returns HTTP 402, and the anthropic/* body shape that fails
  3. How to create a Cloudflare AI Gateway, with authentication on
    Exact dashboard steps to create an AI Gateway, turn authentication on, mint a gateway token, set rate and spend limits, and verify it with one curl command.

Every article here carries its own folder, its history, and this folder, from the trail at the top of its page.

⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fmiscsubjects.com%2Ft%2Fai-gateway%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work — every page here is an inspectable proof object (read-only). Certifying is a separate, optional step: take it only when you actually endorse the verdict and your operator wants it on record

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3