Taddy
Taddy is a GraphQL API for podcasts and comics, giving developers access to over 4 million podcasts and 200 million episodes, plus real-time full-text search, automatically generated episode transcripts, chapters, iTunes metadata, daily top charts, webcomic and creator data, and webhook notifications for new or updated content. All queries hit a single GraphQL endpoint at https://api.taddy.org authenticated with X-USER-ID and X-API-KEY headers.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Taddy the way a machine reads it — 15 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Taddy scores 24.9/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Taddy
Each block below is one kind of artifact we hold for Taddy. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Taddy Podcast Search API
Blazing-fast full-text `search` query across all 4M+ podcasts and 200M+ episodes, with filters for country, genre, language, publish date, and whether a transcript is available,...
Taddy Podcast Series & Episodes API
Look up podcast series and episodes via getPodcastSeries, getPodcastEpisode, getMultiplePodcastSeries, getMultiplePodcastEpisodes, and getLatestPodcastEpisodes, keyed by Taddy u...
Taddy Episode Transcripts API
Retrieve episode transcripts with getEpisodeTranscript and the transcriptWithSpeakersAndTimecodes field, including per-line text, speaker names, and start/end timecodes, backed ...
Taddy Episode Chapters API
Fetch chapter markers for an episode via getEpisodeChapters and the chapters field, returning chapter titles and start timecodes for chapterized podcasts.
Taddy iTunes Info API
Resolve Apple Podcasts / iTunes metadata for a podcast with getItunesInfo and the itunesInfo field, including iTunes ID, base artwork URL, categories, and content advisory.
Taddy Top Charts & Popular API
Retrieve daily top charts and popular content with getTopChartsByCountry, getTopChartsByGenre, and getPopularContent, filterable by country, genre, and language.
Taddy Comics & Creators API
Access webcomic and creator data via getComicSeries, getComicIssue, getCreator, and getMultipleCreators, covering comic series, individual issues, and the artists, writers, and ...
Taddy Webhooks API
Real-time webhook notifications for new and updated content, delivering events such as podcast.created, podcast.updated, podcast.deleted, podcast.new_episodes, and matching crea...
Taddy Account & Usage API
Monitor plan consumption with getApiRequestsRemaining (monthly API request quota) and getTranscriptCreditsRemaining (monthly transcript credit allocation).
Scroll within the panel for all 9 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Taddy GraphQL API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Taddy GraphQL API
Taddy is a **native GraphQL API** for podcasts and comics. It gives developers
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Taddy Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Taddy Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Taddy Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Taddy — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/taddy · machine-readable index on apis.io