ListenHub

API documentation is structured across authentication, concepts, errors, pricing, and quick-start sections. However, the OpenAPI specification endpoint returns 404, and multi-modal output claims from the vendor tagline are not represented in the documented API.

Documentation covers authentication flow, generation modes, speaker management, error codes, and credit system. The .well-known/openapi.json endpoint returns a 404 page instead of a machine-readable spec.

Standard Bearer token authentication, environment variable setup, and consistent HTTP 200 + code field error model reduce integration friction. SSE streaming enables progressive UI without polling. Quick-start guide claims sub-5-minute first API call.

Authentication uses Bearer $LISTENHUB_API_KEY. All responses return HTTP 200 with code field for success/failure. SSE delivers outline and script during audio generation. Quick Start promises first call under 5 minutes.

Podcast, debate, and multi-role dialogue modes provide meaningful generation variety. Speaker library with language/gender metadata supports voice casting. SSE streaming and dual script+MP3 output are well-documented. However, vendor tagline claims music, image, and video generation that lack corresponding API documentation.

Documented modes: podcast (1-2 speakers), debate (2 speakers), multi-role dialogue. Speaker library via GET /v1/speakers/list. No documented endpoints for music, image, or video generation despite tagline claims.

API-first design with script-first workflow, SSE progressive delivery, and credit-based consumption suits programmatic integration into CMS, news aggregation, and content automation pipelines. Multi-role dialogue extends utility to audiobook and drama production workflows.

Script-first workflow with separate audio synthesis step. SSE for progressive outline delivery. Credit-based consumption with balance-check endpoint. Multi-role mode supports audiobook and radio drama use cases.

Documented error codes and rate limits provide basic operational transparency. However, no SLA, uptime commitment, or redundancy details are available in the documentation. API key leak risk is explicitly noted by the vendor as a direct financial exposure.

Error codes documented for invalid keys (21007), insufficient credits (26004), invalid state (25008), parameter validation (29003). Vendor warns API key = account credentials. No SLA or uptime information provided.

Credit-based pricing with subscription plans is mentioned, and a balance-check endpoint exists. However, concrete per-request costs are not disclosed in public documentation, making cost projection difficult without signing up.

Credits system with subscription plans and GET /v1/user/subscription endpoint documented. Rate limits mentioned. No per-request pricing figures in public documentation.