Scrykeeper Intelligence API

Structured intelligence for agents.

Query Scrykeeper's Story Intelligence, resolved author identities, observed reader graph, Royal Road metadata and known commercial mappings using stable, machine-readable endpoints.

OpenAPI JSON → Data methodology → Request beta access → Agent discovery →

Important data semantics

Observed readers are readers present in Scrykeeper's sampled public Royal Road favourite graph. They are not total readership counts.

“No known commercial mapping” does not mean a story is unpublished, and an author profile is not guaranteed to be a complete bibliography.

Agent discovery

Start here


GET https://scrykeeper.com/.well-known/scrykeeper.json

Automated clients can discover the OpenAPI document, methodology endpoint, authentication model and supported operations from this record.

Core operations

API V1

GET


                /api/v1/story/{rr_fiction_id}

Story metadata, sampled audience observations, author identity and known commercial mappings.

Authentication optional

GET


                /api/v1/author/{identity_id}

Resolved author identity, known Royal Road works and deduplicated observed audience footprint.

Authentication optional

GET


                /api/v1/market/search

Structured search across genre, lifecycle, followers, sampled audience, freshness and known commercial mappings.

API key + market:read

GET


                /api/v1/about-data

Current data coverage, source-specific freshness, methodology and limitations.

No authentication

Example

Story lookup

curl \
  https://scrykeeper.com/api/v1/story/118891

Example

Market search

Never put an API key in a public URL. Send it in an authorization header.

curl \
  -H "Authorization: Bearer $SCRYKEEPER_API_KEY" \
  "https://scrykeeper.com/api/v1/market/search?genre=litrpg&lifecycle=ongoing&followers_min=1000&followers_max=5000&readers_min=10&commercial=none&updated_days=30"

Current data context

Know what you are querying

9,453 Story Intelligence records

2,414 observed graph readers

56,810 reader-story edges

115 known commercial mappings

Reader graph latest represented observation: 2026-09-17T11:54:29.926852+00:00

See /api/v1/about-data for the authoritative current coverage and source-specific freshness information.

MCP Public Beta

Connect an AI agent directly

Scrykeeper also exposes the same intelligence through Model Context Protocol. The beta endpoint uses Streamable HTTP.

https://scrykeeper.com/mcp

Available tools:


                get_story

Story Intelligence for a Royal Road fiction ID.


                get_author

Resolved author identity, known catalogue and sampled audience footprint.


                search_market

Structured Royal Road market discovery using metadata, sampled audience and known commercial mappings.


                get_data_context

Current coverage, freshness, methodology and data limitations.

Beta authentication

MCP currently uses the same sk_v1_ Bearer API keys as the REST API. Standards-based OAuth is planned before broader public MCP availability.

Authentication

API keys

Beta API keys use the sk_v1_ prefix and are currently provisioned manually. Scrykeeper stores a cryptographic digest of the key rather than the plaintext credential.

Authorization: Bearer sk_v1_...

or

X-API-Key: sk_v1_...

Treat API keys as secrets. Do not put them in source repositories, browser-side code, screenshots, URLs or prompts sent to services that do not need the credential.

Contract

Stable semantics

Current data contract: scrykeeper_data_contract_v1.1.0

Normal API responses contain a compact data_context and data_notice. Full methodology and limitations remain at /api/v1/about-data .