Contentful through Squiid

Enterprise headless CMS with localisation and publishing workflows. Contentful is on the Squiid roadmap.

Roadmap Provisioned Provisioned. Squiid creates the project or account for you and keeps the provider keys.

What Contentful is

Contentful is a headless CMS built for organisations with process. Content models define types and relationships, entries carry locales for translation, roles and permissions control who can edit and publish what, scheduled publishing and release grouping coordinate a launch, and both REST and GraphQL delivery APIs serve the published result from a CDN with a separate preview API for drafts. An app framework extends the editing interface, and migrations are scriptable so content model changes can be reviewed like code.

In an AI-coded project Contentful is chosen when a marketing or content team already works this way, or when localisation is a real requirement rather than a possibility. Multi-locale content is where lighter tools struggle, because every field needs a per-language version and an editorial state, and building that on top of a database table is a project nobody planned for. Rich text is stored as a structured document rather than HTML, which makes rendering consistent across web and mobile clients. Release scheduling is the other piece teams buy it for, because a coordinated launch across locales is hard to fake with a git-based workflow.

Why connect it through Squiid

Contentful is on the Squiid roadmap. When it is connected, Squiid will provision the space, hold the delivery, preview and management tokens, and route calls through https://api.squiid.io/v1/contentful/... with Authorization: Bearer $SQUIID_API_KEY, with the SDKs working by base URL swap (gateway convention). API calls, bandwidth and plan cost will bill at Contentful's listed price on one Squiid invoice. The management token in particular can rewrite every entry in the space, which is not something that belongs in a preview deployment's environment variables.

  • One account, one key, one bill, one dashboard. Contentful sits beside every other service your project uses, on the same invoice and the same credit balance.
  • Key custody. Squiid holds the Contentful credentials. Your code carries SQUIID_API_KEY, so CONTENTFUL_SPACE_ID, CONTENTFUL_DELIVERY_TOKEN, CONTENTFUL_PREVIEW_TOKEN, CONTENTFUL_MANAGEMENT_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 Contentful 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 Contentful space with tokens held by Squiid
  • Content modelling with references and validation
  • Localisation and editorial workflows
  • REST and GraphQL delivery plus a preview API
  • Contentful list pricing, no markup

How to connect Contentful

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 CONTENTFUL_SPACE_ID, CONTENTFUL_DELIVERY_TOKEN, CONTENTFUL_PREVIEW_TOKEN, CONTENTFUL_MANAGEMENT_TOKEN
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Add it in your dashboard

Open the Squiid catalog, add Contentful and fund credits. Squiid provisions the project and keeps the provider keys.

02

Put the one key in your env

Add SQUIID_API_KEY to .env and delete CONTENTFUL_SPACE_ID, CONTENTFUL_DELIVERY_TOKEN, CONTENTFUL_PREVIEW_TOKEN, CONTENTFUL_MANAGEMENT_TOKEN. Nothing else from Contentful needs to exist in your project.

03

Point your agent at it

Claude Code, Cursor and Codex read the same variable and call https://api.squiid.io/v1/contentful/. Agents query the delivery API with GraphQL and keep the management token server side for any write path.

Pricing through Squiid

Contentful charges a plan fee by users, spaces and API calls with usage above the allowance billed separately, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Contentful usage, with no markup and no per-request margin.

Contentful 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 Contentful 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 Contentful account. Squiid never owns your code, your schema or your domain, and the gateway speaks Contentful'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

Contentful 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:

Vibe coding a feature on Contentful 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.

Related services

Questions people ask

Is Contentful on Squiid yet?

Not yet. It is on the roadmap as a provisioned service.

Contentful or Sanity?

Sanity is more developer-shaped, with the studio and schema in code. Contentful is stronger on localisation, roles and editorial process.

Does it support GraphQL?

Yes, alongside the REST delivery API, with a separate preview API for unpublished drafts.

Who holds the management token?

Squiid. It can rewrite every entry in the space, so provisioned access keeps it out of application environments.

How will it be billed?

Plan and usage at Contentful's listed price on your single Squiid invoice, with no markup.

Connect Contentful with one key.

Contentful is a headless CMS with content modelling, localisation, editorial workflows, scheduled publishing and both REST and GraphQL delivery APIs. Planned for Squiid.