# Ceros

> Ceros is an experiential content platform for building interactive, no-code web content —
> microsites, landing pages, interactive reports, pitch decks and embeddable experiences — and
> publishing them to a CDN. Its developer surface is three distinct things: a small read-only REST
> Public API over accounts, folders, experiences and embed codes; a browser-side Flex Experience
> SDK that scripts a published experience at runtime; and a public oEmbed endpoint plus CMS
> connectors that put an experience inside another platform.

Generated by API Evangelist on 2026-08-09. Ceros does not publish an llms.txt of its own —
https://developers.ceros.com/llms.txt returns 404 and https://www.ceros.com/llms.txt returns 404.
This file is assembled from Ceros's own public developer documentation and from live probes.

## APIs

- [Ceros Public API](https://developers.ceros.com/api/public/ceros-public-api): REST, base URL
  https://rest.ceros.com. Bearer API key (`Authorization: Bearer YOUR_API_KEY`), key generated in
  Ceros account settings. Version pinned with the `x-ceros-api-version` header
  (current: 2026-05-28-09-00). Current version exposes four read-only operations:
  `getCurrentAccount`, `getFolderTree`, `listFolderExperiences`, `getEmbedCodes`.
- [Ceros oEmbed](https://view.ceros.com/oembed): public, unauthenticated oEmbed 1.0 provider.
  `GET /oembed?url=<experience url>&format=json` returns the title, canonical URL and responsive
  embed HTML. `format=xml` is 501; an unresolvable url is 400.

## Documentation

- [Developer portal](https://developers.ceros.com/)
- [Overview](https://developers.ceros.com/overview)
- [Getting started with the API](https://developers.ceros.com/guides/getting-started)
- [Versioning policy](https://developers.ceros.com/guides/versioning)
- [API reference](https://developers.ceros.com/api/public/ceros-public-api)
- [Help centre / knowledge base](https://educate.ceros.com/en/)
- [Technical FAQ](https://www.ceros.com/technical-faq-s/)

## SDK

- [Flex Experience SDK](https://developers.ceros.com/flex-experience-sdk): browser ES module,
  no install. On Ceros-hosted pages `import { connect } from '@ceros/flex-experience-sdk'`; on
  your own pages `import { connect } from 'https://assets.ceros.site/js/flex-experience-sdk.js'`.
- [Getting started](https://developers.ceros.com/flex-experience-sdk/getting-started)
- [Delivery modes](https://developers.ceros.com/flex-experience-sdk/delivery-modes): Standalone,
  Flex SSR, Flex Inline.
- [Capabilities](https://developers.ceros.com/flex-experience-sdk/reference/capabilities):
  text, media, states, visibility, pages.
- [Locators](https://developers.ceros.com/flex-experience-sdk/reference/locators),
  [Component](https://developers.ceros.com/flex-experience-sdk/reference/component),
  [ComponentSet](https://developers.ceros.com/flex-experience-sdk/reference/component-set),
  [Events](https://developers.ceros.com/flex-experience-sdk/reference/events),
  [Store](https://developers.ceros.com/flex-experience-sdk/reference/store)
- [Limits](https://developers.ceros.com/flex-experience-sdk/limits): runtime-only, published
  experiences only, cannot create or remove components, browser 2023+.
- [Troubleshooting](https://developers.ceros.com/flex-experience-sdk/troubleshooting)

## Packages

- npm `@ceros-dev/markup-sdk` 1.0.0-rc.1 — browser SDK for MarkUp commenting.
- npm `@ceros-dev/markup-sdk-core` 1.0.0-rc.1 — shared types and utilities.
- Maven `com.ceros:ceros-aem-connector` 1.0.2 — Adobe Experience Manager Flex component.
- There is no server-side client library for the Public API in any registry.

## Plugins and connectors

- [Plugins index](https://developers.ceros.com/plugins)
- [AEM connector](https://developers.ceros.com/plugins/aem-connector) —
  [source](https://github.com/ceros/ceros-aem-connector)
- [Contentful app](https://github.com/ceros/ceros-contentful-app)
- [Optimizely CMS plugin](https://github.com/ceros/ceros-optimizely-cms-plugin)
- [Experience plugins](https://github.com/ceros/ceros-plugins) — Eloqua, Marketo Munchkin, SoundJS

## Operations

- [Status page](https://status.ceros.com/) — Atlassian Statuspage; machine-readable summary at
  https://status.ceros.com/api/v2/summary.json
- [Service Level Agreement](https://www.ceros.com/service-level-agreement/) — 99.9% platform,
  99.995% published experiences, with a service-credit schedule.
- [Trust centre](https://trust.ceros.com/) — Vanta-hosted; certification list renders client-side
  only and could not be read.
- [Roadmap](https://portal.productboard.com/ceros/7-ceros-staging-roadmap) — Productboard.

## Company

- [Website](https://www.ceros.com/)
- [Pricing](https://www.ceros.com/pricing/)
- [Blog](https://www.ceros.com/blog/)
- [MarkUp](https://www.ceros.com/mark-up/)
- [GitHub organization](https://github.com/ceros)
- [Terms](https://www.ceros.com/terms-and-conditions/) ·
  [Privacy](https://www.ceros.com/privacy-policy/) ·
  [Contact](https://www.ceros.com/contact/) ·
  [Login](https://www.ceros.com/login/)

## What Ceros does not publish

- No downloadable OpenAPI document — the reference is generated from one, but no spec file is
  served at any URL.
- No webhooks, no event catalog, no AsyncAPI. The only "events" are browser-side SDK events.
- No MCP server and no A2A agent card.
- No rate limits, no idempotency mechanism, no request-id header.
- No sandbox or test mode.
- No API changelog, and no deprecation policy or Sunset header — the write operations present in
  version 2026-02-25-12-00 are simply absent from the current version with no notice.