Serve content to every front end
Model your content once in Geiger Content and read it from a public REST API, with scoped tokens and the filters, sorting and pagination your front end expects.
Geiger Content: the delivery APITyped fields in, clean JSON out
Content types hold Text, Number, Boolean, Date, Reference, Rich text, Enum, JSON and Media fields. The v2 API takes Strapi v5-style filters, sort, populate and pagination, and v1 serves entries by project or slug.
Tokens scoped to the job
Delivery tokens carry delivery:read, schema:read or both, and show whether they're Active, Expired or Revoked. A token that asks for more than it holds is refused.
Read the schema, not just the entries
The _schema endpoint describes every content type and its fields, so a client can check what it's about to receive.
Roll back a bad publish
Every entry keeps version snapshots you can compare and roll back to, and you can invalidate the cache on demand so the fix goes out straight away.
Personalise without ignoring consent
POST /api/decide picks the right variant for a slot, and visitors who declined personalisation only see untargeted content. The collect endpoint drops events from visitors who declined analytics.