Ceros

Ceros is an experiential content platform used by marketing, design and agency teams to build interactive, no-code web content — microsites, landing pages, interactive reports, infographics, pitch decks and embeddable experiences — in a browser design studio and publish them to a CDN. Its developer surface is three separate things. A small read-only REST Public API at rest.ceros.com walks accounts, folders, experiences and embed codes behind a bearer API key, versioned by dated snapshots selected with the x-ceros-api-version header. A browser-side Flex Experience SDK, delivered as an ES module from the Ceros CDN, scripts a published experience at runtime — setting text, controlling media and states, toggling visibility and navigating pages. And a public oEmbed 1.0 endpoint on view.ceros.com, together with first-party connectors for Adobe Experience Manager, Contentful, Optimizely and WordPress, places an experience inside another platform. Ceros also operates MarkUp, its visual commenting and collaboration product.

Ceros publishes 6 APIs on the APIs.io network, including Accounts API, Embed Codes API, Experience API, and 3 more. Tagged areas include Content Management, Interactive Content, Digital Experience, Embed, and oEmbed.

Ceros’ developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 26 more developer resources.

🌐 Visit website 📡 Source on GitHub
52.7/100 developing ▬ flat Agent 36/100 agent ready Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
6 APIs 1 MCP Servers
Content ManagementInteractive ContentDigital ExperienceEmbedoEmbedCMS IntegrationMarketingDesignNo CodeContent DeliveryMedia and PublishingSDK

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 52.7/100 · developing
Contract Quality 14.7 / 25
Developer Ergonomics 12.5 / 20
Commercial Clarity 10.5 / 20
Operational Transparency 5.5 / 13
Governance 1.4 / 12
Discoverability 8.2 / 10
Agent readiness — 36/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/ceros: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Ceros Accounts API

The accounts API from Ceros — 1 operation(s) for accounts.

Ceros Embed Codes API

The embedCodes API from Ceros — 1 operation(s) for embedcodes.

Ceros Experience API

The experience API from Ceros — 1 operation(s) for experience.

Ceros Experience Page API

The experiencePage API from Ceros — 6 operation(s) for experiencepage.

Ceros Folders API

The folders API from Ceros — 1 operation(s) for folders.

Ceros Oembed API

The oembed API from Ceros — 1 operation(s) for oembed.

Open Collections 7

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Ceros Accounts API

OPEN COLLECTION

Ceros Embed Codes API

OPEN COLLECTION

Ceros Experience API

OPEN COLLECTION

Ceros Public Experience Page API

OPEN COLLECTION

Ceros Folders API

OPEN COLLECTION

Ceros Oembed API

OPEN COLLECTION

Scroll for all 7

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

ceros-mcp.yml

MCP SERVER

Examples 1

Example request and response payloads for these APIs.

Ceros Oembed Response

10 fields

EXAMPLE

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Ceros Authentication

http · 1 scheme

SECURITY

Ceros Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Ceros Trust Center

trust center published

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 Login
Login
 SignUp
SignUp

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer
MCPServer
 LLMsTxt
LLMsTxt
 WellKnown
WellKnown
 AgentSkill
AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Components
Components
 Conventions
Conventions
 Lifecycle
Lifecycle
 ErrorCatalog
ErrorCatalog
 DataModel
DataModel
 Conformance
Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages
 SDKs
SDKs

Access & Security 3

Authentication, authorization, and security posture

TrustCenter
TrustCenter
 Authentication
Authentication
 DomainSecurity
DomainSecurity

Operate 5

Status, limits, changes, and where to get help

HelpCenter
HelpCenter
 Support
Support
 Roadmap
Roadmap
 StatusPage
StatusPage
 ChangeLog
ChangeLog

Commercial 3

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Other 1

Properties that don't map to a standard resource type

Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
aid: ceros
name: Ceros
description: Ceros is an experiential content platform used by marketing, design and agency teams to build interactive, no-code
  web content — microsites, landing pages, interactive reports, infographics, pitch decks and embeddable experiences — in
  a browser design studio and publish them to a CDN. Its developer surface is three separate things. A small read-only REST
  Public API at rest.ceros.com walks accounts, folders, experiences and embed codes behind a bearer API key, versioned by
  dated snapshots selected with the x-ceros-api-version header. A browser-side Flex Experience SDK, delivered as an ES module
  from the Ceros CDN, scripts a published experience at runtime — setting text, controlling media and states, toggling visibility
  and navigating pages. And a public oEmbed 1.0 endpoint on view.ceros.com, together with first-party connectors for Adobe
  Experience Manager, Contentful, Optimizely and WordPress, places an experience inside another platform. Ceros also operates
  MarkUp, its visual commenting and collaboration product.
url: https://raw.githubusercontent.com/api-evangelist/ceros/refs/heads/main/apis.yml
image: https://www.ceros.com/favicon.ico
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-09'
modified: '2026-08-09'
tags:
- Content Management
- Interactive Content
- Digital Experience
- Embed
- oEmbed
- CMS Integration
- Marketing
- Design
- No Code
- Content Delivery
- Media and Publishing
- SDK
apis:
- aid: ceros:ceros-accounts-api
  name: Ceros Accounts API
  description: The accounts API from Ceros — 1 operation(s) for accounts.
  humanURL: https://developers.ceros.com/api/public/ceros-public-api
  baseURL: https://rest.ceros.com
  tags:
  - accounts
  properties:
  - type: OpenAPI
    url: openapi/ceros-accounts-api-openapi.yml
  - type: Documentation
    url: https://developers.ceros.com/overview
  - type: APIReference
    url: https://developers.ceros.com/api/public/ceros-public-api
  - type: GettingStarted
    url: https://developers.ceros.com/guides/getting-started
  - type: Authentication
    url: authentication/ceros-authentication.yml
  - type: Conventions
    url: conventions/ceros-conventions.yml
  - type: ErrorCatalog
    url: errors/ceros-problem-types.yml
  - type: Lifecycle
    url: lifecycle/ceros-lifecycle.yml
  - type: DataModel
    url: data-model/ceros-data-model.yml
  - type: ChangeLog
    url: changelog/ceros-changelog.yml
  - type: Conformance
    url: conformance/ceros-conformance.yml
  - type: Example
    url: examples/ceros-oembed-response.json
- aid: ceros:ceros-embedcodes-api
  name: Ceros Embed Codes API
  description: The embedCodes API from Ceros — 1 operation(s) for embedcodes.
  humanURL: https://developers.ceros.com/api/public/ceros-public-api
  baseURL: https://rest.ceros.com
  tags:
  - embedCodes
  properties:
  - type: OpenAPI
    url: openapi/ceros-embedcodes-api-openapi.yml
  - type: Documentation
    url: https://developers.ceros.com/overview
  - type: APIReference
    url: https://developers.ceros.com/api/public/ceros-public-api
  - type: GettingStarted
    url: https://developers.ceros.com/guides/getting-started
  - type: Authentication
    url: authentication/ceros-authentication.yml
  - type: Conventions
    url: conventions/ceros-conventions.yml
  - type: ErrorCatalog
    url: errors/ceros-problem-types.yml
  - type: Lifecycle
    url: lifecycle/ceros-lifecycle.yml
  - type: DataModel
    url: data-model/ceros-data-model.yml
  - type: ChangeLog
    url: changelog/ceros-changelog.yml
  - type: Conformance
    url: conformance/ceros-conformance.yml
  - type: Example
    url: examples/ceros-oembed-response.json
- aid: ceros:ceros-experience-api
  name: Ceros Experience API
  description: The experience API from Ceros — 1 operation(s) for experience.
  humanURL: https://developers.ceros.com/api/public/ceros-public-api
  baseURL: https://rest.ceros.com
  tags:
  - experience
  properties:
  - type: OpenAPI
    url: openapi/ceros-experience-api-openapi.yml
  - type: Documentation
    url: https://developers.ceros.com/overview
  - type: APIReference
    url: https://developers.ceros.com/api/public/ceros-public-api
  - type: GettingStarted
    url: https://developers.ceros.com/guides/getting-started
  - type: Authentication
    url: authentication/ceros-authentication.yml
  - type: Conventions
    url: conventions/ceros-conventions.yml
  - type: ErrorCatalog
    url: errors/ceros-problem-types.yml
  - type: Lifecycle
    url: lifecycle/ceros-lifecycle.yml
  - type: DataModel
    url: data-model/ceros-data-model.yml
  - type: ChangeLog
    url: changelog/ceros-changelog.yml
  - type: Conformance
    url: conformance/ceros-conformance.yml
  - type: Example
    url: examples/ceros-oembed-response.json
- aid: ceros:ceros-experiencepage-api
  name: Ceros Experience Page API
  description: The experiencePage API from Ceros — 6 operation(s) for experiencepage.
  humanURL: https://developers.ceros.com/api/public/ceros-public-api
  baseURL: https://rest.ceros.com
  tags:
  - experiencePage
  properties:
  - type: OpenAPI
    url: openapi/ceros-experiencepage-api-openapi.yml
  - type: Documentation
    url: https://developers.ceros.com/overview
  - type: APIReference
    url: https://developers.ceros.com/api/public/ceros-public-api
  - type: GettingStarted
    url: https://developers.ceros.com/guides/getting-started
  - type: Authentication
    url: authentication/ceros-authentication.yml
  - type: Conventions
    url: conventions/ceros-conventions.yml
  - type: ErrorCatalog
    url: errors/ceros-problem-types.yml
  - type: Lifecycle
    url: lifecycle/ceros-lifecycle.yml
  - type: DataModel
    url: data-model/ceros-data-model.yml
  - type: ChangeLog
    url: changelog/ceros-changelog.yml
  - type: Conformance
    url: conformance/ceros-conformance.yml
  - type: Example
    url: examples/ceros-oembed-response.json
- aid: ceros:ceros-folders-api
  name: Ceros Folders API
  description: The folders API from Ceros — 1 operation(s) for folders.
  humanURL: https://developers.ceros.com/api/public/ceros-public-api
  baseURL: https://rest.ceros.com
  tags:
  - folders
  properties:
  - type: OpenAPI
    url: openapi/ceros-folders-api-openapi.yml
  - type: Documentation
    url: https://developers.ceros.com/overview
  - type: APIReference
    url: https://developers.ceros.com/api/public/ceros-public-api
  - type: GettingStarted
    url: https://developers.ceros.com/guides/getting-started
  - type: Authentication
    url: authentication/ceros-authentication.yml
  - type: Conventions
    url: conventions/ceros-conventions.yml
  - type: ErrorCatalog
    url: errors/ceros-problem-types.yml
  - type: Lifecycle
    url: lifecycle/ceros-lifecycle.yml
  - type: DataModel
    url: data-model/ceros-data-model.yml
  - type: ChangeLog
    url: changelog/ceros-changelog.yml
  - type: Conformance
    url: conformance/ceros-conformance.yml
  - type: Example
    url: examples/ceros-oembed-response.json
- aid: ceros:ceros-oembed-api
  name: Ceros Oembed API
  description: The oembed API from Ceros — 1 operation(s) for oembed.
  humanURL: https://developers.ceros.com/api/public/ceros-public-api
  baseURL: https://rest.ceros.com
  tags:
  - oembed
  properties:
  - type: OpenAPI
    url: openapi/ceros-oembed-api-openapi.yml
  - type: Documentation
    url: https://developers.ceros.com/overview
  - type: APIReference
    url: https://developers.ceros.com/api/public/ceros-public-api
  - type: GettingStarted
    url: https://developers.ceros.com/guides/getting-started
  - type: Authentication
    url: authentication/ceros-authentication.yml
  - type: Conventions
    url: conventions/ceros-conventions.yml
  - type: ErrorCatalog
    url: errors/ceros-problem-types.yml
  - type: Lifecycle
    url: lifecycle/ceros-lifecycle.yml
  - type: DataModel
    url: data-model/ceros-data-model.yml
  - type: ChangeLog
    url: changelog/ceros-changelog.yml
  - type: Conformance
    url: conformance/ceros-conformance.yml
  - type: Example
    url: examples/ceros-oembed-response.json
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: MCPServer
  url: mcp/ceros-mcp.yml
- type: Overlay
  url: overlays/ceros-public-api-overlay.yaml
- type: Website
  url: https://www.ceros.com/
- type: DeveloperPortal
  url: https://developers.ceros.com/
- type: Documentation
  url: https://developers.ceros.com/overview
- type: APIReference
  url: https://developers.ceros.com/api/public/ceros-public-api
- type: GettingStarted
  url: https://developers.ceros.com/guides/getting-started
- type: HelpCenter
  url: https://educate.ceros.com/en/
- type: Support
  url: https://www.ceros.com/contact/
- type: Blog
  url: https://www.ceros.com/blog/
- type: GitHubOrganization
  url: https://github.com/ceros
- type: Roadmap
  url: https://portal.productboard.com/ceros/7-ceros-staging-roadmap
- type: Pricing
  url: https://www.ceros.com/pricing/
- type: Login
  url: https://www.ceros.com/login/
- type: SignUp
  url: https://www.ceros.com/demo-request/
- type: TermsOfService
  url: https://www.ceros.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://www.ceros.com/privacy-policy/
- type: StatusPage
  url: https://status.ceros.com/
- type: TrustCenter
  url: security/ceros-trust-center.yml
- type: Packages
  url: packages/ceros-packages.yml
- type: SDKs
  url: packages/ceros-packages.yml
- type: Components
  url: components/ceros-components.yml
- type: LLMsTxt
  url: llms/ceros-llms.txt
- type: WellKnown
  url: well-known/ceros-well-known.yml
- type: Authentication
  url: authentication/ceros-authentication.yml
- type: Conventions
  url: conventions/ceros-conventions.yml
- type: Lifecycle
  url: lifecycle/ceros-lifecycle.yml
- type: ChangeLog
  url: changelog/ceros-changelog.yml
- type: ErrorCatalog
  url: errors/ceros-problem-types.yml
- type: DataModel
  url: data-model/ceros-data-model.yml
- type: Conformance
  url: conformance/ceros-conformance.yml
- type: DomainSecurity
  url: security/ceros-domain-security.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-08-09'
  status: enriched
  artifacts_added: 25
  pass: local-v1