Everything tagged tooling

13 published articles · newest first · server-rendered

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

Also filed under: architecture 5 · mcp 5 · cloudflare 4 · agents 3 · ai-gateway 3 · cost 3 · oip 3 · tool-search 3 · measurement 2 · anthropic-messages 1 · api 1 · billing 1 · capability-tokens 1 · claude-code 1

  1. Cloudflare OS: running real code
    Cloudflare OS XL part 3: running real code off the laptop
  2. The misc agent: what was asked, what shipped, what is still broken
  3. MCP is one view of a capability table, and the view you pick costs 6.25x
    One recorded 891-capability catalogue published three ways — zero definitions, seven tools, or 856 tools — cost 6.25× more per turn through its largest surface; live wire measurements show the moving
  4. Deferred tool search against a catalogue in a database: same cost today, different scaling
    Dimension-by-dimension comparison of Anthropic's deferred tool search and keeping the capability catalogue in a database behind one endpoint. On 891 capabilities both cost the same per turn — 14,109 i
  5. Resolve, read, invoke, receipt: the four calls a stranger's agent makes
    The complete cold-start loop for a model that has never seen this system: four HTTP calls with real request and response, every error string, replay and repair lineage, and a measured cost of $0.00000
  6. One row of SQL is the whole contract for a capability, and the 892nd took 3.1 seconds
    Every column of the directory row that defines a callable capability on this build, the four runner types with a real row of each, why secrets are named but never stored, and the verbatim POST, receip
  7. Nine tool definitions reach every capability: the catalogue is a SQL table, not a prompt
    The same 891-capability catalogue measured three ways on one build: 149,187 input tokens a turn as MCP tool definitions, 14,109 with deferred tool search, 14,071 with no MCP server at all.
  8. 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
  9. MCP definitions use 10.6× more input tokens until tool search defers them
    A live catalogue of 831 MCP tools measures 127,440 tokens of definitions; deferring them cut one measured turn from 149,187 input tokens to 14,109. The commands to measure your own, and the five filed
  10. 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
  11. 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.
  12. The Anthropic Messages API is one endpoint with a strict block grammar
    A complete implementation guide to one POST endpoint: required headers, five block types, 11 measured stream frames, tool pairing, cache economics and exact failure repairs.
  13. Claude Code on Kimi, GLM or Grok through your own Cloudflare account
    Step-by-step: run the Claude Code CLI against Kimi K2.7 Code, GLM-5.2, Grok or Claude through your own Cloudflare AI Gateway. Prerequisites, exact commands, the two settings that cut a turn from $0.21

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%2Ftooling%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