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.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Episerver the way a machine reads it — 8 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Episerver scores 45.1/100 (developing), with a separate agent-readiness read of 19/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Episerver
Each block below is one kind of artifact we hold for Episerver. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
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.
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Episerver Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Episerver — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
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
← All providers · Data indexed from github.com/api-evangelist/episerver · machine-readable index on apis.io