Install Jentic One Beta

Connect the Kissa Shuru to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kissa Shuru, 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%2Fkissashuru.com%2Fkissashuru" | sh

Step 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%2Fkissashuru.com%2Fkissashuru" | 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 Kissa Shuru API.

List movies page by page with per_page and page, and read a movie's details by movie_id for a user profile

Assign an offline download task to a device for a customer, with entertainment_id, priority, and size_bytes

List the customers assigned to a partner and their credit balances

List a partner's devices and record a device returned to the partner with deviceId and userId

GET STARTED

Start building with Kissa Shuru API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Kissa Shuru API for, with concrete tasks.

★ AI agent partner operations through Jentic

A distribution partner's agent handles routine device work: it searches Jentic for 'assign a download to a device', loads the Kissa Shuru download task operation with its input schema, and queues a movie for a customer's device. Your own Jentic One instance injects the partner bearer token at call time, so the agent never holds it.

Call POST /api/device-download-tasks/assign with customer_id 8, device_id 5, entertainment_id 12, partner_id 3, offline_download 1, priority 2, and size_bytes 1048576

Partner customer and credit review

A partner reviews who they serve and how much credit each customer has left. GET /api/customers lists the customers assigned to the partner, GET /api/customers/credits returns their credits, and GET /api/device-partners/list shows the devices in the partner's care.

Call GET /api/customers and GET /api/customers/credits, then list customers with credits alongside GET /api/device-partners/list

Movie browsing in a mobile app

A mobile client lists movies page by page, optionally filtering restricted titles with is_restricted, then opens a movie's details for the current user and profile. Dashboard operations return the home screen data for that profile.

Call GET /api/v2/movie-list with per_page 30 and page 1, then GET /api/v2/movie-details with a movie_id, user_id, and profile_id from the results

Key Endpoints

28 endpoints — the kissa shuru api serves the movie library and device network behind the kissa shuru offline viewing service.

METHOD

PATH

DESCRIPTION

GET

/api/v2/movie-list

List movies

GET

/api/v2/movie-details

Get movie details

POST

/api/device-download-tasks/assign

Assign a download task to a device

GET

/api/customers

List customers assigned to the partner

GET

/api/customers/credits

List customer credits

POST

/api/partners/return-device

Return a device to the partner

POST

/api/get-download-otp

Get a download OTP for a video

GET

/api/v2/movie-list

List movies

GET

/api/v2/movie-details

Get movie details

POST

/api/device-download-tasks/assign

Assign a download task to a device

GET

/api/customers

List customers assigned to the partner

GET

/api/customers/credits

List customer credits

POST

/api/partners/return-device

Return a device to the partner

POST

/api/get-download-otp

Get a download OTP for a video

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Kissa Shuru by hand means logging a partner in for a bearer token, knowing which operations need it and which are open, and shaping download task bodies yourself. Through Jentic you install once, import Kissa Shuru from the API Directory, store the token once, and your agent calls it.

Permission scoping

Kissa Shuru passes its customer, device, and movie targets in query parameters or the request body, so limit the agent to the operations it needs, such as listing movies and partner customers. Rules bound which operations your agent may call, not which customer, so download assignment or device returns are not included unless you add them.

Credential isolation

Your Kissa Shuru token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list movies' or 'assign a download to a device', and Jentic returns the matching Kissa Shuru operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Kissa Shuru API through Jentic.

What authentication does the Kissa Shuru API use?

Per its OpenAPI spec, the Kissa Shuru API uses a bearer token, required on partner operations such as GET /api/customers and POST /api/device-download-tasks/assign. Many mobile and lookup operations, including the movie list, movie details, partner login, and location lookups, are marked as open. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time.

Can I assign a movie download to a device with the Kissa Shuru API?

Yes. POST /api/device-download-tasks/assign takes customer_id, device_id, entertainment_id, partner_id, offline_download, priority, and size_bytes in the request body and queues the download for that device.

What are the rate limits for the Kissa Shuru API?

The OpenAPI spec does not specify rate limits. Check with Kissa Shuru at https://kissashuru.com for current limits.

Is there a Kissa Shuru MCP server?

You don't need an MCP server to give your agent the Kissa Shuru API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the movie and partner operations on demand without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with the Kissa Shuru API?

Yes. For example, write a rule that allows only GET /api/customers, GET /api/customers/credits, and GET /api/device-partners/list, so the agent can review customers, credits, and devices but cannot assign downloads or record device returns. Every call it makes through your instance is logged.

How do I list Kissa Shuru movies through Jentic?

Search Jentic for 'list Kissa Shuru movies', load the movie list operation, and call GET /api/v2/movie-list with per_page and page. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Kissa Shuru

AI ReadinessNon-Ready (F)0/100

See full scorecard

Community OpenAPI document · agent-readyMediaVideo Processingbearer28 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List Kissa Shuru movies and their details, check a movie's availability for a partner, assign offline download tasks to devices, and look up partner customers, credits, and locations.

Use for: List the movies available in the Kissa Shuru library, Get the details for a specific movie, Assign a movie download to a customer's device, List all customers assigned to my partner account

Not supported: Does not stream video online, transcode files, or process card payments. Use for Kissa Shuru movie listings, partner customers, and device download tasks only.

The Kissa Shuru API serves the movie library and device network behind the Kissa Shuru offline viewing service. Mobile operations list movies page by page, return movie details and dashboard data for a user profile, and issue a download OTP for a video, while partner operations log a partner in, list their assigned customers, customer credits, and devices, assign offline download tasks to a device, and record device returns. Location lookups return states, districts, talukas, and villages.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

71%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

18%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

46%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Kissa Shuru to your agent

Capabilities

Start building with Kissa Shuru API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Kissa Shuru

Jentic AI Readiness Score

Kissa Shuru

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness