Ceramic
Ceramic is a decentralized data network built on a protocol for mutable event streams anchored to blockchain. It provides REST APIs for creating and updating mutable data streams, managing decentralized identifiers (DIDs), registering data interests, and reading stream state and events across the composable data network.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Ceramic the way a machine reads it — 35 machine-readable artifacts across 10 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 — Ceramic scores 42.2/100 (thin), with a separate agent-readiness read of 39/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 Ceramic
Each block below is one kind of artifact we hold for Ceramic. 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 10
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.
Ceramic Config API
The Config API from Ceramic — 1 operation(s) for config.
Ceramic Debug API
The Debug API from Ceramic — 1 operation(s) for debug.
Ceramic Events API
The Events API from Ceramic — 2 operation(s) for events.
Ceramic Experimental API
The Experimental API from Ceramic — 2 operation(s) for experimental.
Ceramic Feed API
The Feed API from Ceramic — 2 operation(s) for feed.
Ceramic Interests API
The Interests API from Ceramic — 2 operation(s) for interests.
Ceramic Liveness API
The Liveness API from Ceramic — 1 operation(s) for liveness.
Ceramic Peers API
The Peers API from Ceramic — 1 operation(s) for peers.
Ceramic Streams API
The Streams API from Ceramic — 1 operation(s) for streams.
Ceramic Version API
The Version API from Ceramic — 1 operation(s) for version.
Scroll within the panel for all 10 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Ceramic API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Error response
JSON SCHEMAA Ceramic Event
JSON SCHEMAA Ceramic Event Data Payload
JSON SCHEMACeramic Event feed data
JSON SCHEMAInformation about multiple events.
JSON SCHEMAA recon interest
JSON SCHEMAInformation about multiple interests.
JSON SCHEMAInformation about the Ceramic network
JSON SCHEMAInformation about a connected peer
JSON SCHEMAList of Peers
JSON SCHEMAState of a Ceramic stream
JSON SCHEMAVersion
JSON SCHEMAScroll within the panel for all 12 ·
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Create Event
EXAMPLEGet Event Feed
EXAMPLEGet Event
EXAMPLEGet Network Info
EXAMPLEGet Peers
EXAMPLEGet Stream State
EXAMPLERegister Interest
EXAMPLEScroll within the panel for all 7 ·
Security Posture 1
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Ceramic — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
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 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ceramic · machine-readable index on apis.io