Read-only REST API v1

The Riordanverse,
ready to build with.

Explore characters, gods, quests, locations, and the multi-generational relationships connecting them through a structured, read-only REST API built for technical precision.

API key required for data; directory and docs are public.
14Collections
RESTArchitecture
JSONResponses

Interactive Inspect

Health: Operational
https://riordanverse.cc
STATUS 200 18.4ms
GET HTTP Request
GET /api/v1/characters/percy-jackson/ HTTP/1.1
Host: riordanverse.cc
Accept: application/json
X-API-Key: YOUR_API_KEY
● Example response excerpt
{
  "slug": "percy-jackson",
  "name": "Percy Jackson",
  "character_type": "demigod",
  "species": "demigod",
  "gender": "male",
  "status": "alive",
  "greek_or_roman": "greek",
  "age_first_appearance": 12,
  "type": "character",
  "cabin_number": 3,
  "fatal_flaw": "Personal loyalty",
  "is_demigod": true,
  "is_big_three_child": true,
  "wiki_url": "https://riordan.fandom.com/wiki/Percy_Jackson"
}

Illustrative content, not a live request or complete response.

Ceiling fresco with classical mythological figures gathered among clouds.
Schema Graph

Olympian Pantheons

Discover gods, titans, and the family relationships connecting their stories.

Image: Visit Olympus

Directory Catalog / REST Entities

Structured Lore ArchitectureCanonical Endpoints

Access comprehensive entities and relational graphs across the Riordan mythology.Base URI prefix for all entities:

Base URI: https://riordanverse.cc/api/v1/

Authentication Requirements

Protected endpoints require the X-API-Key header. Directory endpoints provide structured JSON payloads.

Key policy guidelines

Global Search Index

Cross-Resource

Perform full-text search queries across characters, deities, items, and locations in a single unified round-trip.

Media Provenance & Images

Archival Assets

Structured image references with attribution fields, source links, and Riordan Wiki provenance. Image rights remain unverified where no license is recorded.

Capabilities

Engineered for Mythic Scale

Built on standard REST paradigms with deterministic schemas and deep relationship traversal.Built to give frontend developers and bot makers an unshakeable foundation.

Connected lore

Follow family relationships, related-entity slugs, and nested REST collections connecting characters, divinities, books, and quests.

Filtering and sorting

Use resource-specific filters and supported sort fields with sort and order=asc or order=desc. Available fields vary by collection.

Paginated collections

Collection envelopes contain data and meta with total, page, limit, and total_pages. Use page and limit; the default is 20, with a maximum of 100.

Character powers

Character details embed powers with sources, types, and limitations. Dedicated character power endpoints support filtering and sorting.

Images and provenance

Explore image references, source and attribution metadata, entity galleries, and Riordan Wiki links.

Documented access

Explore Swagger UI, ReDoc, and the OpenAPI schema. Request an API key and send it in the X-API-Key header for protected endpoints.

Integration Protocol

Quick Start in 3 Steps

Initialize communication with the Riordanverse archive.No credit card or demigod pedigree required.

01 Key request

Request an API Key

Issue a key request specifying your application identifier and developer email.

curl -X POST https://riordanverse.cc/auth/request-key/ \
  -H "Content-Type: application/json" \
  --data '{"consumer_name": "Camp Half-Blood App", "email": "you@example.com"}'
02 Header

Configure the Header

Append your issued token to each outbound request in the dedicated security header.

HTTP Security Header X-API-Key: YOUR_API_KEY

Tokens must be kept confidential and omitted from public client bundles.

03

Make your first query

Execute your initial character lookup via cURL, fetch, or Axios.

curl https://riordanverse.cc/api/v1/characters/percy-jackson/ \
  -H "X-API-Key: YOUR_API_KEY"