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 API contracts indexed 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 27 more developer resources.

🌐 Visit website 📡 Source on GitHub

51.5/100 developing ▬ flat Agent 20/100 agent aware Front door AI 4/6 moderate saas Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

3 published contracts

Content ManagementInteractive ContentDigital Experience Embed oEmbedCMS IntegrationMarketing Design No-Code Content DeliveryMedia and PublishingSDK

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Marketing Management

BC-400

experiencePage

POST /experiences/{experienceResourceId}/pages POST /experiences/{experienceResourceId}/pages/{pageId}/apply-template POST /experiences/{experienceResourceId}/pages/{pageId}/duplicate

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 51.5/100 · developing

Contract Quality 10.1 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 7.9 / 15

Operational Transparency 3.9 / 10

Contract Governance 0.4 / 9

Discoverability 5.4 / 8

Regulatory Posture 4.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 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

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. 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. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Content, Documentation and Design Platforms	builds-on	17.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

oEmbed

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

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 o Embed API

The o Embed API from Ceros — 1 operation(s) for o embed.

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

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Ceros Public Api Overlay

9 actions · update · ceros-public-api-openapi.yml

GENERATED

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

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

X-MCPServerCandidate

LLMsTxt

WellKnown

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Components

Conventions

Lifecycle

ErrorCatalog

DataModel

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

Support

Roadmap

StatusPage

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 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

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
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://www.ceros.com/favicon.ico
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-09'
modified: '2026-08-09'
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-21
tags:
- Content Management
- Interactive Content
- Digital Experience
- Embed
- oEmbed
- CMS Integration
- Marketing
- Design
- No-Code
- Content Delivery
- Media and Publishing
- SDK
tags_raw:
- 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:
  - Account
  tags_raw:
  - 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: []
  tags_raw:
  - 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
  tags_raw:
  - 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: []
  tags_raw:
  - 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
  tags_raw:
  - 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-o-embed-api
  name: Ceros o Embed API
  description: The o Embed API from Ceros — 1 operation(s) for o embed.
  humanURL: https://developers.ceros.com/api/public/ceros-public-api
  baseURL: https://rest.ceros.com
  tags:
  - oEmbed
  tags_raw:
  - o Embed
  properties:
  - type: OpenAPI
    url: openapi/ceros-o-embed-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: CapabilityMap
  url: capabilities/ceros-capability-edges.yml
  name: Ceros Business Capability Map
- type: X-MCPServerCandidate
  url: mcp/ceros-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- 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

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/ceros"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/ceros/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/ceros/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.