Shikimori One Shikimori API

Name: Shikimori API
Brand: Shikimori API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationoauth257 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Shikimori API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Shikimori API, 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.

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 | sh

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 instance

Jentic 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 Shikimori API.

List animes

Show an anime

Get anime roles

Query and filter Shikimori API records by parameters

GET STARTED

Start building with Shikimori API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Shikimori API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

57 endpoints — api for shikimori, a social network and database for anime and manga fans.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Shikimori API through Jentic.

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.

Shikimori One Shikimori API

Connect the Shikimori API to your agent

Capabilities

Start building with Shikimori API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs