canonical: https://jentic.com/apis/nekos.best/nekos-best

# NekosBest

Jentic publishes the only available OpenAPI specification for NekosBest, keeping it validated and agent-ready. NekosBest is a free anime image and GIF API offering high-quality assets across multiple categories including neko, kitsune, waifu, husbando, and a wide range of reaction GIFs such as hug, kiss, pat, and slap. The 2 endpoints expose a category list and a randomised image fetch, so a single GET against /endpoints discovers the available categories and a GET to /{category} returns one or more random images with source attribution.

## For AI agents

Fetch random anime images and reaction GIFs across categories like neko, waifu, hug, and pat from a free, no-auth public API.

## Scope

Does not generate new images, host user uploads, or moderate content - use for fetching curated anime images and reaction GIFs only.

## Capabilities

- List all available image and GIF categories via GET /endpoints
- Fetch a random anime image from a chosen category via GET /{category}
- Request multiple images in a single call using the amount query parameter on /{category}
- Receive source artist and post URL metadata alongside each returned asset
- Switch between still image and reaction GIF categories using the category path
- Cache the /endpoints response to avoid re-listing the category set on every call

## Use cases

### Discord Reaction Bot

A Discord bot lets users send anime-styled reaction commands like /hug @user or /pat @user by calling GET /hug or GET /pat on NekosBest and posting the returned GIF in chat. The /endpoints call seeds the bot's command list at startup. The API is free, no-auth, and CDN-backed, so the bot can serve thousands of users without managing storage or rate negotiation.

Example prompt: GET https://nekos.best/api/v2/hug and post the returned URL as the bot's reply to a /hug command.

### Web App Avatar and Mood Pack

A community web app lets new users pick a randomised anime avatar by calling GET /neko or GET /waifu and presenting the returned URLs as a chooser. The same flow swaps in a reaction GIF for the user's mood indicator. Source attribution is preserved using the artist_href and source_url fields in the response.

Example prompt: GET /waifu?amount=4 and render the four returned image URLs in the avatar picker UI.

### Static Site Hero Image

A fan site uses NekosBest to rotate the hero image on the homepage by calling /kitsune at build time and embedding the URL. Because the API is free and unauthenticated, the build step does not need credentials, and the source attribution shipped in the JSON satisfies the artist credit requirement on the page footer.

Example prompt: GET /kitsune at build time, write the returned URL into the site's homepage template, and render the artist credit from the response.

### Agent-Driven Reaction Picker

A chat-assistant agent decorates its replies with reaction GIFs when the conversation calls for it, using Jentic to discover the NekosBest categories and fetch a matching GIF without manually maintaining a category map. The agent searches for the operation, loads the schema, and submits the call with the chosen category.

Example prompt: Search Jentic for 'fetch a NekosBest reaction GIF', load the schema for GET /{category}, and execute it with category=hug.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/endpoints` | List all available categories |
| GET | `/{category}` | Get random image or GIF from a category |

## Key resources

- **Categories** — List the available image and GIF categories
- **Images** — Fetch random images or GIFs from a chosen category

## Why Jentic

- **Setup:** Wiring NekosBest by hand means discovering which categories exist from the endpoints listing, then building the category path for each image or reaction GIF fetch yourself. Through Jentic you install once, import NekosBest from the API Directory, and your agent calls it, with no credential to store since it is unauthenticated.
- **Permission scoping:** NekosBest is read-only and takes the category in the URL path with no account or resource id, so you limit the agent to the operations it needs, such as listing endpoints or fetching a category. The agent can only run the two operations you allow, and neither changes any state.
- **Credential handling:** NekosBest is unauthenticated, so your Jentic One instance stores no credential for it and routes calls without injecting any secret. No token enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'fetch an anime hug GIF' or 'list the available image categories', and Jentic returns the matching NekosBest operation with its category schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **MyAnimeList** — Anime and manga catalogue API for titles, characters, and episodes
- **Kitsu** — Anime and manga catalogue API with library and progress tracking
- **OpenAI** — Image generation via DALL-E for custom anime-style art instead of curated stills

## FAQ

### Why is there no official OpenAPI spec for NekosBest?

NekosBest publishes its API as a documentation site at docs.nekos.best rather than a machine-readable OpenAPI file. Jentic generates and maintains this spec so that AI agents and developers can call NekosBest via structured tooling. It is validated against the live nekos.best/api/v2 endpoints and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the NekosBest API use?

NekosBest is unauthenticated - no API key, bearer token, or basic-auth header is required. The OpenAPI spec declares no security scheme, and the public endpoints under nekos.best/api/v2 are accessible directly. Through Jentic the calls are routed without any credential handling.

### Can I fetch multiple images in a single call?

Yes. GET /{category}?amount=N returns N random assets from that category in one response. The maximum per call is documented as 20 in the official docs; values above that are clamped or rejected by the server.

### What are the rate limits for NekosBest?

NekosBest does not publish numeric per-endpoint rate limits in the OpenAPI document. The public CDN handles bursts well, but heavy continuous polling will be throttled at the network edge; back off on 429 responses and cache the /endpoints listing rather than refetching it each call.

### How do I get a reaction GIF through Jentic?

Run pip install jentic, then search for 'fetch a NekosBest reaction GIF', load the schema for GET /{category}, and execute it with the desired category like hug, pat, or kiss. Jentic returns the JSON body with the asset URL and artist attribution.

### Does NekosBest host arbitrary uploaded images?

No. NekosBest serves a curated catalogue of anime images and reaction GIFs aggregated by the maintainers. There is no upload endpoint and no way to add custom images via the API.

### Can I limit what my agent is allowed to do with the NekosBest API?

Yes. Because you run Jentic One self-hosted, your own rules decide which NekosBest operations the agent may call, so you can allow only listing the categories via GET /endpoints, only fetching an image via GET /{category}, or both. NekosBest is read-only and takes the category in the URL path with no account or resource id, so the agent can run only the operations you permit and neither one changes any state. No credential is involved, since the API is unauthenticated.
