Studio Ghibli
Studio Ghibli API — a community-built, unofficial, fan-made, MIT-licensed REST API that catalogs the people, places, and things found in the worlds of Studio Ghibli. Five resource collections (films, people, locations, species, vehicles) cross-link via canonical URLs. No authentication, no metering, no paid tier. Source: github.com/janaipakos/ghibliapi (archived 2022-12-02); canonical instance now at ghibliapi.vercel.app.
APIs
Studio Ghibli API
Read-only REST API exposing five resource collections (films, people, locations, species, vehicles) that catalog the worlds of Studio Ghibli. No authentication; default page siz...
Capabilities
Studio Ghibli API — Films
Studio Ghibli API — Films. 2 operations. Lead operation: List Films. Self-contained Naftiko capability covering one Studio Ghibli business surface.
Run with NaftikoStudio Ghibli API — Locations
Studio Ghibli API — Locations. 2 operations. Lead operation: List Locations. Self-contained Naftiko capability covering one Studio Ghibli business surface.
Run with NaftikoStudio Ghibli API — People
Studio Ghibli API — People. 2 operations. Lead operation: List People. Self-contained Naftiko capability covering one Studio Ghibli business surface.
Run with NaftikoStudio Ghibli API — Species
Studio Ghibli API — Species. 2 operations. Lead operation: List Species. Self-contained Naftiko capability covering one Studio Ghibli business surface.
Run with NaftikoStudio Ghibli API — Vehicles
Studio Ghibli API — Vehicles. 2 operations. Lead operation: List Vehicles. Self-contained Naftiko capability covering one Studio Ghibli business surface.
Run with NaftikoFeatures
Films, people, locations, species, and vehicles — each addressable as a paginated collection and as a single resource by UUID.
Resources cross-link to related resources using canonical URLs, so consumers can walk the graph without join logic.
Optional `fields=` query parameter returns only the named fields, reducing payload size.
Optional `limit=` query parameter (default 50, max 250) bounds list responses.
Fully anonymous public API; no API key, no OAuth, no token.
The backing JSON Server implementation is open source and can be forked and self-hosted.
Use Cases
A safe, stable, no-auth API frequently used in front-end tutorials, REST workshops, and language-SDK demonstrations.
Builders of Studio Ghibli fan sites can hydrate film/character/location detail pages directly from the API.
Used by projects like ghibliQL to demonstrate wrapping a REST API in a GraphQL layer.
A self-contained, read-only domain that makes a good fixture for MCP server demos, tool-use examples, and agent walkthroughs.
Integrations
The API is implemented on top of typicode/json-server (https://github.com/typicode/json-server).
The documentation site is rendered with Redocly's ReDoc (https://github.com/Rebilly/ReDoc).
Film poster and banner images are served from image.tmdb.org.
Solutions
Fork janaipakos/ghibliapi and deploy to Vercel, Render, Fly.io, or any Node host for guaranteed availability.