Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Simkl 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsimkl.com%2Fsimkl" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsimkl.com%2Fsimkl" | 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.
What an agent can do with Simkl API.
Get PIN for device authentication
Check PIN status
Search movies
Query and filter Simkl API records by parameters
Monitor Simkl API operational status and events
GET STARTED
Patterns agents use Simkl API for, with concrete tasks.
★ Analytics Operations
Use the Simkl API to perform analytics operations programmatically. The API provides 27 endpoints covering core functionality including get pin for device authentication, check pin status, get access token.
Call GET /oauth/pin to get pin for device authentication
Automated Authentication Management
Automate authentication operations by combining multiple Simkl API endpoints. Agents can check pin status and then get access token in a single workflow.
Call GET /oauth/pin/{user_code} to check pin status, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Simkl 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 apiKey, bearer tokens manually.
Search Jentic for 'get pin for device authentication', load the operation schema, and execute with Jentic-managed credentials
27 endpoints — simkl api for accessing movie, tv show, and anime data.
METHOD
PATH
DESCRIPTION
/oauth/pin
Get PIN for device authentication
/oauth/pin/{user_code}
Check PIN status
/oauth/token
Get access token
/search/movie
Search movies
/search/tv
Search TV shows
/search/anime
Search anime
/search/id
Search by external ID
/movies/{id}
Get movie details
/oauth/pin
Get PIN for device authentication
/oauth/pin/{user_code}
Check PIN status
/oauth/token
Get access token
/search/movie
Search movies
/search/tv
Search TV shows
/search/anime
Search anime
/search/id
Search by external ID
/movies/{id}
Get movie details
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Simkl by hand means combining its simkl-api-key header with a bearer token from the device PIN flow and pointing calls at https://api.simkl.com. Through Jentic you install once, import Simkl from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Simkl search operations carry their query in the request path and query string, so limit the agent to the operations it needs, such as searching movies or looking up a title by id. You choose the operations it may call, so anything you do not add stays unavailable to the agent.
Credential isolation
Your Simkl api-key and token 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 'search for a movie' or 'look up a title by id', and Jentic returns the matching Simkl operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Simkl API through Jentic.
What authentication does the Simkl API use?
The Simkl API uses apiKey, bearer authentication. 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 get pin for device authentication with the Simkl API?
Yes. Use the GET /oauth/pin endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Simkl 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 get pin for device authentication through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get pin for device authentication'. Jentic returns the matching Simkl API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Simkl API have?
The Simkl API exposes 27 endpoints covering authentication, search, movies operations.
Can I limit what my agent is allowed to do with the Simkl API?
Yes. Because Jentic One is self-hosted, you decide which Simkl operations your agent may call and which credentials it may use. Simkl carries its queries in the request path and query string, so you can add only the operations you need, such as searching movies, TV shows, or anime, or looking up a title by external id, and leave everything else unavailable. Any operation you do not add, and the stored api-key and token behind it, stays out of the agent's reach.
For Agents
Programmatically get pin for device authentication, check pin status. Covers 27 operations with apiKey, bearer authentication.
Use for: I need to pin for device authentication, I want to check pin status, Search for access token, Find all movies
Not supported: Does not handle payments, communications, or crm - use for analytics only.
Simkl API for accessing movie, TV show, and anime data. Provides search, ratings, watch history tracking, and recommendations. The API exposes 27 endpoints secured with apiKey, bearer authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>