audivo-dev

audivo-dev Catalog API

Public podcast show/episode search, charts, detail, and resolution. Every metadata/search/list call in this tag costs 1 credit; no catalog response echoes `credits_charged`, so the charge is stated here rather than per-response. Not yet applied: the discovery operations shipped in 0.2.0 (`GET /v1/search/shows`, `GET /v1/charts`) are metered by request rate only and write no credit-bearing row; the per-call charge lands with the catalog reads that bill.

GitHub OpenAPI

Operations 4

GET /v1/search/shows Find shows by name #
GET /v1/charts A category chart of a chosen size, capped by tier #
GET /v1/shows/{show_id}/episodes Episode metadata for a show #
GET /v1/resolve Resolve a podcast pointer to canonical IDs without creating a job #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/audivo-dev/openapi/audivo-dev-catalog-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/audivo-dev/json-schema/audivo-dev-job-status-schema.json
📊
JSONSchema
https://artifacts.apis.io/audivo-dev/json-schema/audivo-dev-quote-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/audivo-dev/json-schema/audivo-dev-job-group-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/audivo-dev/json-schema/audivo-dev-auto-recharge-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/audivo-dev/json-schema/audivo-dev-transcript-read-schema.json
📊
JSONSchema
https://artifacts.apis.io/audivo-dev/json-schema/audivo-dev-usage-response-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/audivo-dev:audivo-dev-catalog-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

audivo-dev-catalog-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Audivo Catalog API
  version: 0.16.0
  description: 'The Audivo API turns a public podcast episode into a clean, timed transcript. Name an episode by an Apple Podcasts link, by its RSS feed URL and GUID, by the episode id an earlier answer gave you, or by an upload of audio you hold; get back structured, timed text — at once for an episode already transcribed, or as a job you poll for fresh audio. One call does it: `POST /v1/transcripts`. Quotes are for pricing a selection of many episodes before confirming it.


    Two authentication schemes, and which an operation takes is part of what it is: `apiKeyBearer` — an `hk_live_` key sent as `Authorization: Bearer` — authenticates the public API, and `dashboardJwt` authenticates the dashboard''s own operations. No operation that takes one accepts the other in its place. An API-key caller reads its balance and reservations from any quote response.


    The hosted MCP server at `/mcp` and the OAuth 2.1 endpoints that connect an assistant to it — `/.well-known/oauth-protected-resource`, `/.well-known/oauth-authorization-server`, and `/oauth/authorize`, `/oauth/token`, `/oauth/register`, `/oauth/revoke` — are protocol transports on the same host, not contract operations: an MCP client discovers and describes them from those two metadata documents (RFC 9728, RFC 8414), and they are documented with the MCP server. Their access tokens are checked by the same authorizer as an API key and metered by the same plan; the consent they need is two dashboard operations below, under **Connected Apps**.


    Deferred on purpose, and absent from this document rather than hidden: webhooks, subscriptions, speaker labels beyond the frozen `diarized: false` shape, custom vocabulary, caller-selected engines, raw-audio URLs, SDKs, translation, and cross-corpus search. What changed in each version is on the documentation site''s changelog.'
  license:
    name: Proprietary
    url: https://docs.audivo.dev/legal/terms
servers:
- url: https://api.audivo.dev
  description: Production API. Append the operation path, including /v1.
tags:


# --- truncated at 32 KB (43 KB total) ---
# Full source: https://artifacts.apis.io/audivo-dev/openapi/audivo-dev-catalog-api-openapi.yml