Episerver

Episerver is a digital experience platform (DXP) vendor that rebranded to Optimizely in 2021 after Episerver acquired Optimizely; the developer surface now ships under the Optimizely brand. The platform combines content management (CMS / Content Cloud), a headless Content Delivery and Content Management REST API, the Optimizely Graph (Content Graph) GraphQL API, Commerce (Configured Commerce and Commerce Connect), Feature Experimentation and Web Experimentation, the Optimizely Data Platform (ODP), the Content Marketing Platform (CMP), and Opti ID for unified OIDC identity. Developers integrate via first-party SDKs for JavaScript, React, Python, Java, C#/.NET, Ruby, PHP, Go and Swift, the EPiServer.CMS .NET libraries on NuGet, REST and GraphQL APIs, and webhooks. This profile was seeded as a portfolio lead and enriched by the API Evangelist pipeline from Optimizely's public developer documentation.

Episerver is listed with 3 APIs on the APIs.io network. Tagged areas include Company, Enterprise, Content Management, Digital Experience Platform, and CMS.

The Episerver catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Episerver’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, authentication, and 21 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

50.0/100 developing ▬ flat Agent 32/100 agent ready saas Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

AccessSelf serve

3 APIs 1 MCP Servers

Company Enterprise Content Management Digital Experience Platform CMS Commerce Experimentation Personalization GraphQL SDK

Kin Score

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

Composite quality — 50.0/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 8.7 / 17

Access Clarity 8.1 / 17

Operational Transparency 6.3 / 11

Contract Governance 1.9 / 10

Discoverability 6.8 / 9

Regulatory Posture 5.3 / 15

Agent readiness — 32/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 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 5 / 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/episerver: 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 →

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.

GraphQL

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

APIs 3

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

Optimizely Graph (Content Graph)

GraphQL Content Graph API that indexes CMS/Commerce content for fast, federated querying across the Optimizely platform.

Optimizely Feature Experimentation REST API

REST API and multi-language SDKs for feature flags, experimentation and rollouts, with the self-hosted Optimizely Agent as a microservice front end.

Content Management REST API (CMS 12)

Headless Content Delivery, Content Management and Content Definitions REST APIs for the Optimizely (Episerver) CMS.

MCP Servers 1

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

Episerver MCP Server

Remote MCP server at mcp.optimizely.com over HTTP.

MCP SERVER

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Episerver Webhooks

ASYNCAPI

Security Posture 4

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

Episerver Authentication

oauth2/openIdConnect/apiKey/http · 6 schemes

SECURITY

Episerver Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Episerver Vulnerability Disclosure

no policy recorded

SECURITY

Episerver Trust Center

SOC 2, ISO 27001, ISO 27017, ISO 27018, PCI DSS, HIPAA

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Lifecycle

Conventions

Conformance

Webhooks

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 6

Authentication, authorization, and security posture

Compliance

TrustCenter

Security

Authentication

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Operate 4

Status, limits, changes, and where to get help

Support

StatusPage

Deprecation

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

Source (apis.yml)

aid: episerver
name: Episerver
description: Episerver is a digital experience platform (DXP) vendor that rebranded to Optimizely in 2021 after Episerver
  acquired Optimizely; the developer surface now ships under the Optimizely brand. The platform combines content management
  (CMS / Content Cloud), a headless Content Delivery and Content Management REST API, the Optimizely Graph (Content Graph)
  GraphQL API, Commerce (Configured Commerce and Commerce Connect), Feature Experimentation and Web Experimentation, the Optimizely
  Data Platform (ODP), the Content Marketing Platform (CMP), and Opti ID for unified OIDC identity. Developers integrate via
  first-party SDKs for JavaScript, React, Python, Java, C#/.NET, Ruby, PHP, Go and Swift, the EPiServer.CMS .NET libraries
  on NuGet, REST and GraphQL APIs, and webhooks. This profile was seeded as a portfolio lead and enriched by the API Evangelist
  pipeline from Optimizely's public developer documentation.
url: https://raw.githubusercontent.com/api-evangelist/episerver/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://logo.clearbit.com/optimizely.com
x-type: company
x-source: vc-portfolio
x-backed-by:
- northzone
x-tier: stub
x-tier-reason: portfolio-lead
x-rebranded-to: Optimizely
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Enterprise
- Content Management
- Digital Experience Platform
- CMS
- Commerce
- Experimentation
- Personalization
- GraphQL
- SDK
tags_raw:
- Company
- Enterprise
- Content Management
- Digital Experience Platform
- CMS
- Commerce
- Experimentation
- Personalization
- GraphQL
- SDKs
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Optimizely Graph (Content Graph)
  description: GraphQL Content Graph API that indexes CMS/Commerce content for fast, federated querying across the Optimizely
    platform.
  humanURL: https://docs.developers.optimizely.com/platform-optimizely/docs/optimizely-graph
  baseURL: https://cg.optimizely.com
  properties:
  - type: GraphQL
    url: https://docs.developers.optimizely.com/platform-optimizely/docs/optimizely-graph
  - type: Authentication
    url: authentication/episerver-authentication.yml
- name: Optimizely Feature Experimentation REST API
  description: REST API and multi-language SDKs for feature flags, experimentation and rollouts, with the self-hosted Optimizely
    Agent as a microservice front end.
  humanURL: https://docs.developers.optimizely.com/feature-experimentation
  baseURL: https://api.optimizely.com
  properties:
  - type: SDKs
    url: packages/episerver-packages.yml
- name: Content Management REST API (CMS 12)
  description: Headless Content Delivery, Content Management and Content Definitions REST APIs for the Optimizely (Episerver)
    CMS.
  humanURL: https://docs.developers.optimizely.com/content-management-system/reference
  baseURL: https://cg.optimizely.com
  properties:
  - type: Documentation
    url: https://docs.developers.optimizely.com/content-management-system/reference
common:
- type: Website
  url: https://www.optimizely.com
- type: DeveloperPortal
  url: https://docs.developers.optimizely.com
- type: Documentation
  url: https://docs.developers.optimizely.com
- type: APIReference
  url: https://docs.developers.optimizely.com/content-management-system/reference
- type: GettingStarted
  url: https://docs.developers.optimizely.com/getting-started
- type: Support
  url: https://support.optimizely.com
- type: Blog
  url: https://www.optimizely.com/insights/blog/
- type: GitHubOrganization
  url: https://github.com/optimizely
- type: StatusPage
  url: https://status.optimizely.com
- type: Deprecation
  url: https://docs.developers.optimizely.com/deprecated-products/docs/deprecated-products
- type: Pricing
  url: https://www.optimizely.com/pricing/
- type: TermsOfService
  url: https://www.optimizely.com/legal/website-terms-of-use/
- type: PrivacyPolicy
  url: https://www.optimizely.com/privacy-policy/
- type: Compliance
  url: https://www.optimizely.com/trust-center/compliance
- type: TrustCenter
  url: security/episerver-trust-center.yml
- type: Security
  url: https://www.optimizely.com/trust-center/security
- type: Packages
  url: packages/episerver-packages.yml
- type: SDKs
  url: packages/episerver-packages.yml
- type: LLMsTxt
  url: llms/episerver-llms.txt
- type: WellKnown
  url: well-known/episerver-well-known.yml
- type: Authentication
  url: authentication/episerver-authentication.yml
- type: Lifecycle
  url: lifecycle/episerver-lifecycle.yml
- type: ChangeLog
  url: changelog/episerver-changelog.yml
- type: Conventions
  url: conventions/episerver-conventions.yml
- type: Conformance
  url: conformance/episerver-conformance.yml
- type: Webhooks
  url: asyncapi/episerver-webhooks.yml
- type: DomainSecurity
  url: security/episerver-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/episerver-vulnerability-disclosure.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

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/episerver"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/episerver/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.