Cloudflare Workers through Squiid

What Cloudflare Workers is

Cloudflare Workers execute your code in data centres close to the user, in an isolate-based runtime that starts in about a millisecond instead of booting a container. The platform around it is what makes it a place to build rather than just a CDN function: Durable Objects give you single-instance stateful coordination for things like rooms and counters, Queues and Cron Triggers handle background work, Workers AI runs models at the edge, and bindings connect a Worker to R2, KV and D1 without network credentials. Static assets can be served from the same Worker, so a small full-stack app is one deployment rather than a frontend host plus an API.

In an agentic coding project Workers is where the small always-on pieces live: webhook receivers, auth callbacks, image transforms, API proxies, rate limiters and scheduled jobs. Durable Objects are also the least painful way to build realtime coordination without standing up a websocket server, which is why collaborative and agent-status features often end up there. Observability is built in with logs and tail sessions, which is how you find out what a deployed Worker actually did.

Why connect it through Squiid

Squiid provisions the Cloudflare account and holds the API token, which is otherwise a broad credential that can edit DNS, purge caches and deploy code. Deployments and runtime calls go through https://api.squiid.io/v1/cloudflare-workers/... with Authorization: Bearer $SQUIID_API_KEY, and Wrangler works by pointing its API base URL at the gateway (gateway convention). Requests and CPU time are metered against prepaid credits at Cloudflare's list price, and the Workers Paid plan passes through at $5 a month on your Squiid invoice with no fee added.

• One account, one key, one bill, one dashboard. Cloudflare Workers sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Cloudflare Workers credentials. Your code carries SQUIID_API_KEY, so CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, CF_API_TOKEN never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Cloudflare Workers costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Workers account with the API token held by Squiid
• Edge deployment with near-zero cold starts
• Durable Objects, Queues and Cron Triggers
• Bindings to R2, KV and D1 on the same account
• Workers Paid at $5 a month passed through at list price

How to connect Cloudflare Workers

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, CF_API_TOKEN
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/cloudflare-workers/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Cloudflare charges a monthly plan fee plus requests and CPU time above the included allowance, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Cloudflare Workers usage, with no markup and no per-request margin.

Cloudflare Workers Workers Paid passes through at $5 a month at the provider’s listed price on your monthly Squiid invoice. Service subscriptions carry no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Cloudflare Workers usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: there is no Cloudflare account transfer, so Workers are redeployed from your source into your own account and routes are re-pointed. Squiid never owns your code, your schema or your domain, and the gateway speaks Cloudflare Workers's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Cloudflare Workers through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Cloudflare Workers usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.