Dodo Ac Nookipedia
✓ Official Vendor SpecMediaContent DeliveryapiKey32 EndpointsREST
For Agents
Look up Animal Crossing villagers, fish, bugs, art, furniture, recipes, and fossils from the Nookipedia wiki via GET endpoints keyed on item names.
Use for: I need to find a villager's profile by name, List every New Horizons fish I can catch in June, Get the details for a specific bug by name, Find New Horizons artwork to verify a real-vs-fake match
Not supported: Does not handle Nintendo account data, save-game uploads, or in-game actions — use for read-only Animal Crossing wiki data only.
The Nookipedia API exposes Animal Crossing game data sourced from the community-maintained Nookipedia wiki, covering villagers, fish, bugs, sea creatures, art, furniture, clothing, tools, items, recipes, and fossils across the series with deep coverage for New Horizons. Endpoints return structured JSON for catalogue browsers, companion apps, museum trackers, and bots. An access key, requested via the Nookipedia form, is required for live calls. The API is an information-only service for fan tools and editorial integrations.
Install Jentic One Beta
Connect the Nookipedia to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nookipedia, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Nookipedia API.
Look up villager data via GET /villagers
List New Horizons fish, bugs, and sea creatures with /nh/fish, /nh/bugs, and /nh/sea
Fetch a single artwork by name via GET /nh/art/{artwork}
Browse New Horizons furniture, clothing, tools, and interior items
Retrieve DIY recipes through /nh/recipes and /nh/recipes/{item}
Look up fossil information via /nh/fossils/individuals
Use Cases
Patterns agents use Nookipedia API for, with concrete tasks.
★ Animal Crossing Companion App Catalogue
Power a companion app that shows villagers, critters, art, and furniture by calling Nookipedia endpoints like /villagers, /nh/fish, and /nh/art. Each endpoint returns structured wiki-derived JSON, so an app can render searchable lists without scraping HTML. Building a catalogue browser usually takes a day once the API key is approved.
GET /nh/fish with month=6 and hemisphere=north, then format the response into a Discord embed listing each fish, location, and shadow size.
Real vs Fake Art Checker
Build a Redd's art authenticity checker by calling GET /nh/art/{artwork} for each artwork name. The endpoint returns the canonical real/fake comparison metadata so a tool can tell players which artworks are forgeries. This is a single GET per artwork and runs entirely client-side once cached.
GET /nh/art and cache the catalogue, then for a user-provided artwork name call /nh/art/{artwork} and return the real-vs-fake metadata.
Museum Completion Tracker
Track museum completion by combining /nh/fish, /nh/bugs, /nh/sea, /nh/art, and /nh/fossils/individuals to build the canonical catchable list, then mark each entry caught or donated in user state. The API is read-only, so progress storage stays in the application.
GET /nh/fish, /nh/bugs, /nh/sea, and /nh/fossils/individuals and produce a single combined museum checklist for a user.
AI Agent Game Helper via Jentic
An AI agent uses Jentic to search for Animal Crossing intents, loads the matching Nookipedia GET endpoint, and answers player questions about villagers, critters, or recipes. The Nookipedia API key is held in the Jentic vault, so the agent never embeds it in tool prompts.
Search Jentic for 'look up an animal crossing villager', execute GET /villagers with the name filter, and return the personality, species, and birthday.
Key Endpoints
32 endpoints — the nookipedia api exposes animal crossing game data sourced from the community-maintained nookipedia wiki, covering villagers, fish, bugs, sea creatures, art, furniture, clothing, tools, items, recipes, and fossils across the series with deep coverage for new horizons.
METHOD
PATH
DESCRIPTION
GET
/villagers
List or look up villagers
GET
/nh/fish
All New Horizons fish
GET
/nh/bugs
All New Horizons bugs
GET
/nh/art/{artwork}
Single New Horizons artwork by name
GET
/nh/recipes
All New Horizons recipes
GET
/nh/fossils/individuals
All New Horizons fossils
GET
/villagers
List or look up villagers
GET
/nh/fish
All New Horizons fish
GET
/nh/bugs
All New Horizons bugs
GET
/nh/art/{artwork}
Single New Horizons artwork by name
GET
/nh/recipes
All New Horizons recipes
GET
/nh/fossils/individuals
All New Horizons fossils
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Nookipedia API key is stored encrypted in the Jentic vault and added to the X-API-KEY header at execution time. Agents only see a scoped reference, so /villagers and /nh/* calls never expose the raw key.
Intent-based discovery
Agents search Jentic with intents like 'look up an animal crossing villager' or 'list new horizons fish' and receive the matching Nookipedia operation with its parameter schema, ready to call.
Time to first call
Direct integration: a few hours once the key is approved. Through Jentic: under 15 minutes from search to first lookup.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Nookipedia API through Jentic.
What authentication does the Nookipedia API use?
Nookipedia issues per-developer API keys via a request form. Calls include the key in an X-API-KEY header. Through Jentic, the key is stored encrypted in the vault and added to outbound requests at execution time so the agent never sees it.
Can I look up an Animal Crossing villager with the Nookipedia API?
Yes. GET /villagers returns villager profiles with optional name, species, and personality filters. Use it to render villager cards or answer player questions about a specific resident.
What are the rate limits for the Nookipedia API?
The OpenAPI spec does not declare explicit rate limits. Nookipedia operates on a community-supported basis, so cache responses aggressively and apply exponential backoff on 429 errors to avoid pressure on the wiki infrastructure.
How do I check if an artwork is real or fake through Jentic?
Run pip install jentic and search for 'check animal crossing artwork'. Jentic returns GET /nh/art/{artwork}. Execute it with the artwork name and the response indicates the real-vs-fake metadata; the API key is injected from the vault.
Does the Nookipedia API include New Horizons recipes?
Yes. GET /nh/recipes lists every DIY recipe with its ingredients, and GET /nh/recipes/{item} returns a single recipe. Pair this with /nh/items to resolve any ingredient names you receive back.
Can I get fossil data for museum completion?
Yes. GET /nh/fossils/individuals returns each individual fossil. Combined with /nh/fish, /nh/bugs, /nh/sea, and /nh/art, this gives the complete museum catalogue an app needs to track completion.
GET STARTED