Ceros website screenshot

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.

50.9/100 developing ▬ flat Agent 22/100 agent aware saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0
3 APIs
Content ManagementInteractive ContentDigital ExperienceEmbedoEmbedCMS IntegrationMarketingDesignNo-CodeContent DeliveryMedia and PublishingSDK

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0
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 →

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 Folders API

OPEN COLLECTION

Ceros Oembed API

OPEN COLLECTION

Scroll for all 7

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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 5

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

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
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'
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-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
  tags_raw:
  - 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: 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 email required.

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