Install Jentic One Beta

Connect the Spinitron v2 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Spinitron v2 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%2Fspinitron.com%2Fspinitron" | 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%2Fspinitron.com%2Fspinitron" | 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 Spinitron v2 API.

Get Personas

Returns scheduled shows optionally filtered by {start} and/or {end} datetimes

Log a Spin

Query and filter Spinitron v2 API records by parameters

Monitor Spinitron v2 API operational status and events

GET STARTED

Start building with Spinitron v2 API

Explore with Jentic One

View OpenAPI Document

Automated Persona Management

Automate persona operations by combining multiple Spinitron v2 API endpoints. Agents can get persona by id and then returns scheduled shows optionally filtered by {start} and/or {end} datetimes in a single workflow.

Call GET /personas/{id} to get persona by id, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Spinitron v2 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 personas', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — notes **tutorial demo** using this api is at [https://spinitron.

METHOD

PATH

DESCRIPTION

GET

/personas

Get Personas

GET

/personas/{id}

Get Persona by id

GET

/shows

Returns scheduled shows optionally filtered by {start} and/or {end} datetimes

GET

/shows/{id}

Get a Show by id

GET

/playlists

Returns playlists optionally filtered by {start} and/or {end} datetimes

GET

/playlists/{id}

Get a Playlist by id

POST

/spins

Log a Spin

GET

/spins

Returns spins optionally filtered by {start} and/or {end} datetimes

GET

/personas

Get Personas

GET

/personas/{id}

Get Persona by id

GET

/shows

Returns scheduled shows optionally filtered by {start} and/or {end} datetimes

GET

/shows/{id}

Get a Show by id

GET

/playlists

Returns playlists optionally filtered by {start} and/or {end} datetimes

GET

/playlists/{id}

Get a Playlist by id

POST

/spins

Log a Spin

GET

/spins

Returns spins optionally filtered by {start} and/or {end} datetimes

Why Jentic?

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

Setup

Wiring the Spinitron v2 API by hand means handling both its query-string access token and JWT bearer auth, and pointing every call at the spinitron.com/api host yourself. Through Jentic you install once, import the Spinitron v2 API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Spinitron puts the resource id in the URL path (/shows/{id}, /playlists/{id}), so a rule can pin your agent to reading one show or playlist. You choose the operations it may call, so posting new spins is not included unless you add it.

Credential isolation

Your Spinitron access 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 DJ personas' or 'get a show's playlists', and Jentic returns the matching Spinitron v2 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Spinitron v2 API through Jentic.

What authentication does the Spinitron v2 API use?

The Spinitron v2 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 personas with the Spinitron v2 API?

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

What are the rate limits for the Spinitron v2 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 personas through Jentic?

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

How many endpoints does the Spinitron v2 API have?

The Spinitron v2 API exposes 9 endpoints covering persona, show, playlist operations.

Can I limit what my agent is allowed to do with the Spinitron v2 API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Spinitron operations and credentials the agent may use. Because Spinitron puts the resource id in the URL path, such as GET /shows/{id} and GET /playlists/{id}, you can pin the agent to reading a single show or playlist. You also choose the operations it may call, so writing new records with POST /spins stays off unless you add it.

Spinitron v2 API

Name: Spinitron v2 API
Brand: Spinitron v2 API
Availability: InStock

Developer ToolsSource ControlapiKey, bearer9 EndpointsREST

For Agents

Programmatically get personas, get persona by id. Covers 9 operations with apiKey, bearer authentication.

Use for: I need to personas, I want to persona by id, Search for returns scheduled shows optionally filtered by {start} and/or {end} datetimes, Find all a show by id

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Notes **Tutorial demo** using this API is at [https://spinitron.com/v2-api-demo/](https://spinitron.com/v2-api-demo/). For web integration using iframes and/or JavaScript instead of an API, see [https://spinitron.github.io/v2-web-integration/](https://spinitron.github.io/v2-web-integration/). **Your API key** is found in the Spinitron web app. Log in to Spinitron and go to *Automation & API* in th. The API exposes 9 endpoints secured with apiKey, bearer authentication.

Jentic One on Github View OpenAPI Document

Connect the Spinitron v2 API to your agent

Capabilities

Start building with Spinitron v2 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Spinitron v2 API