James Washington
writing about archive utils free game ideas replays
Technique

Omni-token + pinned account_id

Give AI agents one all-powerful cloud key, but make every project refuse to deploy anywhere except its own account.

Cloudflare and the edge

how it works

Broad Cloudflare user token = capability; explicit account_id in each wrangler config = safety, since wrangler refuses other accounts. Verify /accounts before first deploy.

Technique: A pattern or hard-won lesson, written down so it isn't learned twice.

The code for this one lives in a private repo. This page explains the idea so you can build your own.

agentscloudflaresecretstechnique

related

  • OpenClaw agent gateway (vault project page) Note Notes on an AI gateway that routes requests across several AI providers with automatic fallbacks.
  • In shared checkouts, prove your deploy landed Technique When several AIs share code, 'deploy succeeded' doesn't mean your change is the one live.
  • Marked-up LLM gateway with per-client virtual keys and Stripe invoicing API A private AI service that lets a consultancy give each client their own AI key and bill them monthly for exactly what they used.
  • Separate flat-rate and metered Claude routes in an LLM gateway Technique Keep the subscription-covered AI and the pay-per-use AI clearly separate so you don't get surprise bills.
  • wdot: Rust headless browser for AI agents Command-line tool A fast tool that lets AI agents read websites cheaply, turning pages into clean text.
← everything I've built
© 2026 James Washington
github twitter rss