What authentication does AniAPI use?

AniAPI uses HTTP bearer authentication with a JWT issued through its OAuth flow. Public read operations on /anime, /episode, and /song typically work unauthenticated, but /user_story and /auth/me require a user-scoped JWT. Through Jentic the JWT is stored in the encrypted vault and is never injected into the agent's prompt context.

Can I update a user's watch history with AniAPI?

Yes. The /user_story endpoint supports reading and updating watch progress, status, and score for a given anime, scoped to the authenticated user identified by the JWT.

What are the rate limits for AniAPI?

The OpenAPI spec does not declare explicit rate limits. AniAPI is community-run, so treat it as best-effort: cache responses for catalogue lookups and back off on 429 or 5xx responses rather than retrying tightly.

How do I look up an anime by title with AniAPI through Jentic?

Run pip install jentic, then search Jentic for 'find anime by title'. Jentic returns GET /anime with its query parameter schema. Execute the call with your title string and parse the returned MyAnimeList, AniList, and Kitsu IDs.

Does AniAPI return streaming provider links?

Yes. GET /resources and GET /resources/{id} return streaming-resource entries for an anime or episode, including provider names and URLs where available. Coverage depends on what the AniAPI community has indexed for that title.

Can I limit what my agent is allowed to do with the AniAPI?

Yes. Because you run Jentic One yourself, your own rules decide which AniAPI operations and credentials the agent may use. You can grant read-only calls like GET /anime and GET /resources/{id} while leaving the /user_story write operations out, so the agent cannot change a user's watch progress or score unless you explicitly add those. Since AniAPI puts the resource id in the URL path, such as /anime/{id} and /resources/{id}, a rule can pin the agent to a specific anime or streaming resource.