Spinitron v2 API

{
  "service_type": "platform",
  "base_url": "https://spinitron.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "Authorization",
    "scheme": "Bearer",
    "key_type": "API key / token",
    "notes": "Spinitron v2 API requires authentication via API token. Users obtain credentials through their Spinitron account. Exact header format should be verified against current docs, but typically Bearer token or query param."
  },
  "endpoints": [
    "/api/v2/shows",
    "/api/v2/playlists",
    "/api/v2/personas",
    "/api/v2/spins"
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "model": "SaaS subscription for radio stations / broadcasters",
      "notes": "Spinitron is a paid platform for radio stations; API access is included with subscription. Pricing is generally per-station and not publicly listed with granular tiers. There may be a trial or demo mode as referenced by the v2-api-demo tutorial."
    }
  },
  "rate_limits": {
    "known": false,
    "notes": "No public documentation of rate limits found in provided content. Likely reasonable usage limits tied to subscription. Should be confirmed in official API docs."
  },
  "capabilities": [
    "Radio playlist logging and reporting",
    "Music spin tracking (artist, title, album, label, etc.)",
    "Show scheduling and program management",
    "DJ / persona attribution",
    "Public playlist and show data for radio stations",
    "REST API v2 for programmatic access to spins, playlists, shows, and personas",
    "Web integration via iframes and/or JavaScript widgets (in addition to API)",
    "Tutorial demo environment (v2-api-demo) for developers",
    "Music reporting to licensing bodies (e.g., royalties, DMCA, SoundExchange) — implied by domain",
    "Station-level data separation and authentication"
  ],
  "raw_analysis": "Spinitron is a SaaS platform purpose-built for radio stations — primarily non-commercial, community, college, and public radio — to log and report music airplay. Its core value proposition is playlist/spin tracking, show scheduling, DJ management, and automating royalty/licensing reports to bodies like ASCAP, BMI, SESAC, and SoundExchange.\n\nThe v2 API exposes programmatic access to the core domain objects: spins (individual track plays), playlists (per-show tracklists), shows (scheduled programs), and personas (DJs/hosts). This makes it possible to build station websites, now-playing widgets, searchable archives, and external dashboards. The presence of a dedicated v2-api-demo URL and reference to iframe/JavaScript integration indicates the vendor actively supports web developers with a sandbox for experimentation.\n\nAuth appears to be API-key based, tied to a station's account. The platform is mature (v2 API implies a prior v1), but it is a vertical B2B product rather than a general-purpose API — its audience is broadcasters, station engineers, and developers building radio web experiences. Pricing is subscription-based and not fully public; access likely scales with station size or features.\n\nFrom an integration standpoint, Spinitron is a well-defined niche platform with a stable REST API, domain-specific data model, and strong documentation support via demos. Any integration should confirm current auth header conventions, rate limits, and data provenance (per-station scoping) from the official docs before implementation."
}

2/3 tests passed

```json
{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 7.0,
    "response_parseability": 8.0,
    "error_clarity": 4.0,
    "doc_quality": 6.0,
    "auth_simplicity": 4.0,
    "latency": 9.5,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "subscription",
    "public_tiers": false,
    "api_included": true,
    "notes": "Paid SaaS per radio station; API included with subscription. No public granular pricing. Likely trial/demo via v2-api-demo."
  },
  "issues": [
    "No llms.txt (404) — agents cannot fetch a compact capability/pricing summary in one request.",
    "robots.txt explicitly blocks major AI agents (anthropic-ai, ClaudeBot, ChatGPT-User, CCBot, Bytespider, etc.) — this is a direct anti-agent signal and will break any agent-driven crawling or discovery of docs.",
    "No public, granular pricing — agents cannot answer 'how much does it cost' from a single source of truth.",
    "Auth for the platform API is station-level; onboarding requires a paid/hosted relationship, so an agent cannot get from zero to a first successful call autonomously.",
    "No llms.txt means token-heavy reverse-engineering of docs to describe the value prop to a user.",
    "Niche vertical (radio stations) — limited addressable user base for agent recommendations."
  ],
  "recommendations": [
    "Publish an llms.txt with: value prop, pricing summary, auth flow, base URL, key endpoints, and rate limits. This is the single highest-leverage change for agent-friendliness.",
    "Reconsider the AI-crawler blocks in robots.txt — at minimum allow anthropic-ai / ChatGPT-User / ClaudeBot to read documentation paths so agents can recommend accurately.",
    "Publish a public pricing page with at least tier ranges and what's included (API, seats, spin volume).",
    "Offer a free sandbox with self-serve API keys (the v2-api-demo is a good start — make it programmatically reachable without a sales conversation).",
    "Return structured, paginated JSON from the API v2 with stable schemas and documented error codes; agents parse these far more reliably than HTML/iframes.",
    "Add a machine-readable OpenAPI / JSON schema published alongside the human API docs.",
    "Document explicit limitations in the docs (rate limits, data retention, timezone handling for spins, licensing-body coverage)."
  ]
}
```