Sanity through Squiid

What Sanity is

Sanity is a headless content platform where the schema and the editing interface are both code. You define document types and fields in your repository, and Sanity Studio renders an editor from them that you can customise with your own React components. Content is queried with GROQ, a query language that can shape and join documents in a single request, editors collaborate in real time with live preview, and the image pipeline crops and transforms assets through URL parameters. Content Lake stores documents with revision history, and portable text keeps rich text structured rather than as a blob of HTML.

For AI-coded sites this keeps content out of components. A marketing page whose copy lives in Sanity can be edited by whoever writes the copy, while the agent keeps working on the code, and nobody has to open a pull request to fix a typo. Structured content is also much easier for an agent to consume reliably than a wall of markdown, because the shape is declared. Webhooks on publish can trigger a rebuild or invalidate a cache, which is how a static site stays current.

Why connect it through Squiid

Sanity is on the Squiid roadmap. When it lands, Squiid will provision the project, hold the API token and route content and asset calls through https://api.squiid.io/v1/sanity/... with Authorization: Bearer $SQUIID_API_KEY, with the client working by base URL swap (gateway convention). API requests, bandwidth and plan cost will bill at Sanity's listed price on one Squiid invoice, and the write token that can modify every document stays out of your deployment environment.

• One account, one key, one bill, one dashboard. Sanity sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Sanity credentials. Your code carries SQUIID_API_KEY, so SANITY_PROJECT_ID, SANITY_DATASET, SANITY_API_TOKEN, NEXT_PUBLIC_SANITY_PROJECT_ID 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 Sanity 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 Sanity project with tokens held by Squiid
• Schema and Studio defined in your codebase
• GROQ queries that shape and join content
• Real-time collaborative editing and preview
• Sanity list pricing, no markup

How to connect Sanity

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 SANITY_PROJECT_ID, SANITY_DATASET, SANITY_API_TOKEN, NEXT_PUBLIC_SANITY_PROJECT_ID
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Sanity charges a plan fee plus API requests, bandwidth and assets 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 Sanity usage, with no markup and no per-request margin.

Sanity has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with 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 Sanity 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: content is exported as structured data and imported into a project in your own Sanity account. Squiid never owns your code, your schema or your domain, and the gateway speaks Sanity'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

Sanity 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 Sanity 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.