ThemeParks.wiki
An ever-growing database of real-time data for the world's best theme parks, including wait times, schedules, and park information.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles ThemeParks.wiki the way a machine reads it — 60 machine-readable artifacts across 2 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 — ThemeParks.wiki scores 22.1/100 (emerging), with a separate agent-readiness read of 29/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from ThemeParks.wiki's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/themeparks-wiki/"
title="ThemeParks.wiki on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/themeparks-wiki.svg"
alt="ThemeParks.wiki Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/themeparks-wiki/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/themeparks-wiki/"
title="ThemeParks.wiki on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/themeparks-wiki/card.svg"
alt="ThemeParks.wiki Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile ThemeParks.wiki
Each block below is one kind of artifact we hold for ThemeParks.wiki. 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 2
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.
ThemeParks.wiki Destinations API
Theme park resort destinations
ThemeParks.wiki Entities API
Park entities including rides, shows, restaurants, and parks
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONThemeParks.wiki Destinations API
OPEN COLLECTIONThemeParks.wiki Destinations Entities API
OPEN COLLECTIONThemeParks.wiki API
OPEN COLLECTIONPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate 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.
Themeparks Wiki 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.
Themeparks Wiki Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Real-Time Wait Times
Live queue wait times and operational status for attractions at 75+ destinations
Park Schedules
Operating hours, special event schedules, and monthly calendar views for parks
Destination Catalog
Complete listing of all supported theme park resort destinations worldwide
Entity Metadata
Detailed information for parks, attractions, shows, and restaurants
Live Operational Status
Real-time OPERATING, DOWN, CLOSED, and REFURBISHMENT status for all entities
Monthly Schedule Lookup
Historical and future operating schedules by specific month and year
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Themeparks Wiki Context
JSON-LDSpectral Rules 2
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.
ThemeParks.wiki API Rules
SPECTRALThemeParks.wiki API Rules
SPECTRALJSON Schema 11
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.
ChildrenResponse
JSON SCHEMADestination
JSON SCHEMADestinationsResponse
JSON SCHEMAEntity
JSON SCHEMALiveDataResponse
JSON SCHEMALiveEntityData
JSON SCHEMALocation
JSON SCHEMAPark
JSON SCHEMAQueueData
JSON SCHEMAScheduleEntry
JSON SCHEMAScheduleResponse
JSON SCHEMAScroll within the panel for all 11 ·
JSON Structure 11
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Themeparks Wiki Children Response Structure
JSON STRUCTUREThemeparks Wiki Destination Structure
JSON STRUCTUREThemeparks Wiki Destinations Response Structure
JSON STRUCTUREThemeparks Wiki Entity Structure
JSON STRUCTUREThemeparks Wiki Live Data Response Structure
JSON STRUCTUREThemeparks Wiki Live Entity Data Structure
JSON STRUCTUREThemeparks Wiki Location Structure
JSON STRUCTUREThemeparks Wiki Park Structure
JSON STRUCTUREThemeparks Wiki Queue Data Structure
JSON STRUCTUREThemeparks Wiki Schedule Entry Structure
JSON STRUCTUREThemeparks Wiki Schedule Response Structure
JSON STRUCTUREScroll within the panel for all 11 ·
Examples 11
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.
Themeparks Wiki Park Example
EXAMPLEScroll within the panel for all 11 ·
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.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Trip Planning
Research park schedules and wait time patterns before visiting
Real-Time Monitoring
Monitor live wait times and attraction availability during a park visit
Media Centers
Power home media center displays with live park data and wait times
AI Park Assistant
Power AI agents that help users plan and navigate theme park visits
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
EmulationStation/RetroPie
Community integrations for theme park data displays
Home Assistant
Smart home integrations for displaying live park data on dashboards
Kodi
Media center plugin integrations for theme park information
Resources
Every other property we hold for ThemeParks.wiki — 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 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/themeparks-wiki · machine-readable index on apis.io
This is an independent, third-party profile of ThemeParks.wiki, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.