Walt Disney World park intelligence for AI agents: live and "Real Wait" wait times, which park to visit today, crowd forecasts, Lightning Lane prices and sellout times, and dining reservation drop odds. Public tools need no authentication; account tools (ride and dining watches) need a pairing key …
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"supapark","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 5 h ago | a2a card | ok | 200 | 417 ms | card: SupaPark · 14 skills |
| 12 h ago | a2a card | ok | 200 | 405 ms | card: SupaPark · 14 skills |
| 20 h ago | a2a card | ok | 200 | 409 ms | card: SupaPark · 14 skills |
Attributed to the source that supplied each field. Treated as claims, not facts.
Walt Disney World park intelligence for AI agents: live and "Real Wait" wait times, which park to visit today, crowd forecasts, Lightning Lane prices and sellout times, and dining reservation drop odds. Public tools need no authentication; account tools (ride and dining watches) need a pairing key the user creates in SupaPark. The interface is an MCP server (streamable HTTP, stateless JSON-RPC 2.0, tools only) with the same tools as plain JSON REST calls described by an OpenAPI 3.1 document; SupaPark does not implement the A2A message/task protocol. Independent service; not affiliated with Disney.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.