canonical: https://jentic.com/apis/shikimori.one/shikimori-one

# Shikimori One Shikimori API

API for Shikimori, a social network and database for anime and manga fans. Provides access to anime, manga, characters, users, clubs, topics, and more. OAuth2 is used for authentication. All requests must include a User-Agent header with your application name. Rate limited to 5 requests per second and 90 requests per minute. The API exposes 57 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically list animes, show an anime. Covers 57 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- List animes
- Show an anime
- Get anime roles
- Query and filter Shikimori API records by parameters
- Monitor Shikimori API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Shikimori API to perform identity auth operations programmatically. The API provides 57 endpoints covering core functionality including list animes, show an anime, get anime roles.

Example prompt: Call GET /api/animes to list animes

### Automated Animes Management

Automate animes operations by combining multiple Shikimori API endpoints. Agents can show an anime and then get anime roles in a single workflow.

Example prompt: Call GET /api/animes/{id} to show an anime, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Shikimori API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'list animes', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /api/animes | List animes |
| GET | /api/animes/{id} | Show an anime |
| GET | /api/animes/{id}/roles | Get anime roles |
| GET | /api/animes/{id}/similar | Get similar animes |
| GET | /api/animes/{id}/related | Get related animes |
| GET | /api/animes/{id}/screenshots | Get anime screenshots |
| GET | /api/animes/{id}/franchise | Get anime franchise |
| GET | /api/animes/{id}/external_links | Get anime external links |

## Key resources

- **Animes** — Operations related to Animes
- **Characters** — Operations related to Characters
- **Clubs** — Operations related to Clubs
- **Comments** — Operations related to Comments
- **Genres** — Operations related to Genres

## Why Jentic

- **Setup:** Wiring the Shikimori API by hand means running its OAuth2 flow, refreshing the access token, and pointing each call at the shikimori.one host yourself. Through Jentic you install once, import the Shikimori API from the API Directory, store the OAuth credentials once, and your agent calls it.
- **Permission scoping:** Shikimori puts the anime id in the URL path (/api/animes/{id}/...), so a rule can pin your agent to one title for reads like roles, related entries, and screenshots. You choose the operations it may call, so anything it should not touch is left out of the allowed set.
- **Credential handling:** Your Shikimori OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list animes' or 'get related titles for an anime', and Jentic returns the matching Shikimori operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Shikimori API use?

The Shikimori API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list animes with the Shikimori API?

Yes. Use the GET /api/animes endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Shikimori API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list animes through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list animes'. Jentic returns the matching Shikimori API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Shikimori API have?

The Shikimori API exposes 57 endpoints covering animes, characters, clubs operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Shikimori operations and OAuth credentials the agent may use, so you can allow read calls like list animes, show an anime, get anime roles, related titles, and screenshots while leaving every other endpoint out of the allowed set. Since Shikimori puts the anime id in the URL path (/api/animes/{id}/...), a rule can also pin the agent to one title for those reads. Anything you do not add to the allowed set, the agent cannot call.