Story Protocol
Story Protocol is a purpose-built EVM Layer 1 blockchain for onchain intellectual property (the "IP blockchain"), powered by Proof of Creativity, built by Pip Labs and backed by a16z. Its public REST API (api.storyapis.com) is a read-only indexer that exposes IP assets, collections, license terms, license templates and tokens, minting fees, disputes, IP groups, royalties, protocol modules, permissions, and transactions across Story mainnet (chain 1514) and the Aeneid testnet (chain 1315). Authentication is an X-Api-Key header plus an X-Chain network selector; official TypeScript and Python SDKs wrap both the API and the onchain protocol.
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 Story Protocol the way a machine reads it — 17 machine-readable artifacts across 13 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 — Story Protocol scores 39.9/100 (thin), with a separate agent-readiness read of 62/100 (agent native). 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 Story Protocol
Each block below is one kind of artifact we hold for Story Protocol. 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 13
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.
Story Protocol Collections API
The Collections API from Story Protocol — 2 operation(s) for collections.
Story Protocol Disputes API
The Disputes API from Story Protocol — 2 operation(s) for disputes.
Story Protocol IPAssets API
The IPAssets API from Story Protocol — 4 operation(s) for ipassets.
Story Protocol IPGroup API
The IPGroup API from Story Protocol — 2 operation(s) for ipgroup.
Story Protocol IPLicenseTerms API
The IPLicenseTerms API from Story Protocol — 4 operation(s) for iplicenseterms.
Story Protocol Licenses API
The Licenses API from Story Protocol — 4 operation(s) for licenses.
Story Protocol LicenseTemplates API
The LicenseTemplates API from Story Protocol — 2 operation(s) for licensetemplates.
Story Protocol LicenseTerms API
The LicenseTerms API from Story Protocol — 2 operation(s) for licenseterms.
Story Protocol LicenseTokens API
The LicenseTokens API from Story Protocol — 2 operation(s) for licensetokens.
Story Protocol Modules API
The Modules API from Story Protocol — 2 operation(s) for modules.
Story Protocol Permissions API
The Permissions API from Story Protocol — 2 operation(s) for permissions.
Story Protocol Royalties API
The Royalties API from Story Protocol — 2 operation(s) for royalties.
Story Protocol Transactions API
The Transactions API from Story Protocol — 3 operation(s) for transactions.
Scroll within the panel for all 13 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
story-protocol-mcp.yml
MCP SERVERSecurity Posture 2
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 Story Protocol — 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 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
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 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/story-protocol · machine-readable index on apis.io