Spinitron v2 API

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

★ Only Publicly Available OpenAPI DocumentDeveloper 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

Quickstart

Get started with Spinitron v2 API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get personas"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Spinitron v2 API 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 API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Spinitron v2 API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Spinitron v2 API API for, with concrete tasks.

★ Developer Tools Operations

Use the Spinitron v2 API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including get personas, get persona by id, returns scheduled shows optionally filtered by {start} and/or {end} datetimes.

Call GET /personas to get personas

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

Why though Jentic?

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

Credential isolation

Spinitron v2 API apiKey, bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get personas') and Jentic returns the matching Spinitron v2 API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Spinitron v2 API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Spinitron v2 API 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.