Hello Audio website screenshot

Hello Audio

Hello Audio (helloaudio.fm) is a hosted platform for private and public podcasts. Creators, course builders and businesses turn existing content such as courses, videos and memberships into private audio feeds that listeners subscribe to through signup pages, with listener management, analytics and AI tooling. It has no public REST API; integration is documented through a Zapier app (triggers and actions), generic and Make/Integromat webhooks, and native connections to email services, course platforms, checkout carts, Stripe, Dropbox, Google Drive and Zoom.

Hello Audio is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Audio, Podcasts, Software-as-a-Service, and Private.

The Hello Audio catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Hello Audio’s developer surface includes API reference, authentication, documentation, getting-started guide, engineering blog, pricing, support, and 30 more developer resources.

Pull Hello Audio's APIs, OpenAPI, scores and pricing into your own code or AI agent with a free APIs.io key — sign in with GitHub, Google or LinkedIn. No form to fill in; signing in shares your email address with us (Privacy).
45.1/100 developing ▬ flat Agent 11/100 agent aware Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-21 · rubric v0.28.1 · Show this score on your site →
AccessPaid
2 APIs 1 MCP Servers
CompanyAudioPodcastsSoftware-as-a-ServicePrivatePrivate PodcastsWebhookZapierCreator Economy

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-21 · rubric v0.28.1
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Hello Audio It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/hello-audio/"><img src="https://apis.io/badge/hello-audio/card.svg" alt="Hello Audio on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
10 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Ask about:
Hello Audio · a person reads this and replies by email.
or email info@apis.io
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/hello-audio/apis.yml: open an issue on github.com/api-evangelist/hello-audio to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Used by apps

1 of the reference apps in Applications, across 1 category, integrate with this provider, read from each app's own code, build or integrations page.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (verified)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Hello Audio API

Hello Audio does not document a public REST API. Programmatic access is through its Zapier app (listener and feed triggers and actions), outbound generic webhooks, Make/Integrom...

Hello Audio MCP Server

Remote Model Context Protocol server that gives an AI assistant read-only access to the feeds on a signed-in Hello Audio account (downloads, listeners, retention and similar fig...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Hello Audio API pricing

Prices published by Hello Audio.

PlanPrice
Starter (annual billing) $14/ PER MONTH BILLED ANNUALLY
Starter (monthly billing) $17/ PER MONTH
Pro (annual billing) $39/ PER MONTH BILLED ANNUALLY
Pro (monthly billing) $47/ PER MONTH
Powerhouse (annual billing) $81/ PER MONTH BILLED ANNUALLY
Powerhouse (monthly billing) $97/ PER MONTH
Hello Audio AI add-on Add to any paid plan for $5 per month

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Hello Audio Rate Limits

0 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Hello Audio

8 quoted statements, read from Hello Audio's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Hello Audio

15 quoted statements, read from Hello Audio's own page on 2026-11-09.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

Hello Audio

3 quoted statements, read from Hello Audio's own page on 2026-11-09.

ELIGIBILITY

AI Preferences 1

Its stance on AI training, inference and agents, quoted from its own pages.

Hello Audio

1 quoted statement, read from Hello Audio's own page on 2026-11-09.

AI PREFS

Data License 1

How its data and outputs may be reused, quoted from its own terms.

Hello Audio

2 quoted statements, read from Hello Audio's own page on 2026-11-09.

LICENSE

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Hello Audio Context

32 classes · 37 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Hello Audio API Rules

44 rules · 39 error-severity 4 warn-severity 1 info-severity

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Hello Audio Openapi Generated Certification Overlay

2 actions · security · hello-audio-openapi-generated.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hello Audio Authentication

3 schemes

SECURITY

Hello Audio Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Hello Audio Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 2

Status, limits, changes, and where to get help

Commercial 6

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Other 6

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: hello-audio
name: Hello Audio
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  probe_state: gated
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-20'
  method: derived
image: https://helloaudio.fm/wp-content/uploads/2022/02/MainLogo.webp
description: Hello Audio (helloaudio.fm) is a hosted platform for private and public podcasts. Creators, course builders and
  businesses turn existing content such as courses, videos and memberships into private audio feeds that listeners subscribe
  to through signup pages, with listener management, analytics and AI tooling. It has no public REST API; integration is documented
  through a Zapier app (triggers and actions), generic and Make/Integromat webhooks, and native connections to email services,
  course platforms, checkout carts, Stripe, Dropbox, Google Drive and Zoom.
url: https://artifacts.apis.io/hello-audio/apis.yml
humanURL: https://helloaudio.fm/
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-28'
modified: '2026-11-04'
tags:
- Company
- Audio
- Podcasts
- Software-as-a-Service
- Private
- Private Podcasts
- Webhook
- Zapier
- Creator Economy
tags_raw:
- Company
- Audio
- Podcast
- SaaS
- Private
- Private Podcasts
- Webhooks
- Zapier
- Creator Economy
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgentCard
  url: a2a/hello-audio-a2a.yml
- type: Hosts
  url: hosts/hello-audio-hosts.yml
- type: APIReference
  url: https://docs.zapier.com/llms.txt
- type: Spectral
  url: rules/hello-audio-rules.yml
- type: JSONLD
  url: json-ld/hello-audio-context.jsonld
- type: Vocabulary
  url: vocabulary/hello-audio-vocabulary.yml
- type: DataModel
  url: data-model/hello-audio-data-model.yml
- type: Conventions
  url: conventions/hello-audio-conventions.yml
- type: Authentication
  url: authentication/hello-audio-authentication.yml
- type: Deprecation
  url: lifecycle/hello-audio-lifecycle.yml
- type: Lifecycle
  url: lifecycle/hello-audio-lifecycle.yml
- type: Conformance
  url: conformance/hello-audio-conformance.yml
- type: IntegrationEdges
  url: integrations/hello-audio-integration-edges.yml
- type: Plans
  url: plans/hello-audio-plans-pricing.yml
- type: LLMsTxt
  url: llms/hello-audio-llms.txt
- type: SecurityTxt
  url: well-known/hello-audio-help-security.txt
- type: WellKnown
  url: well-known/hello-audio-well-known.yml
- type: Vendors
  url: vendors/hello-audio-vendors.yml
- type: DomainSecurity
  url: security/hello-audio-domain-security.yml
- type: Website
  url: https://helloaudio.fm/
- type: Documentation
  url: https://help.helloaudio.fm/en/collections/14938214-zapier-webhooks
- type: GettingStarted
  url: https://help.helloaudio.fm/en/collections/14937853-getting-started
- type: Integrations
  url: https://help.helloaudio.fm/en/collections/14937981-platform-integrations
- type: Zapier
  url: https://zapier.com/apps/hello-audio/integrations
- type: Blog
  url: https://helloaudio.fm/blog/
- type: Pricing
  url: https://helloaudio.fm/pricing/
- type: TermsOfService
  url: https://helloaudio.fm/terms/
- type: PrivacyPolicy
  url: https://helloaudio.fm/privacy/
- type: Login
  url: https://app.helloaudio.fm/login
- type: Support
  url: https://help.helloaudio.fm/en/
- type: About
  url: https://helloaudio.fm/about/
- type: YouTube
  url: https://www.youtube.com/@helloaudiofm
- type: Instagram
  url: https://www.instagram.com/helloaudiofm/
- type: UsageTerms
  url: terms/hello-audio-terms-of-service.yml
- type: DataProcessing
  url: privacy/hello-audio-privacy-policy.yml
- type: Eligibility
  url: eligibility/hello-audio-eligibility.yml
- type: AIPreferences
  url: ai-preferences/hello-audio-ai-preferences.yml
- type: DataLicense
  url: data-license/hello-audio-data-license.yml
apis:
- name: Hello Audio API
  description: Hello Audio does not document a public REST API. Programmatic access is through its Zapier app (listener and
    feed triggers and actions), outbound generic webhooks, Make/Integromat webhooks and native platform integrations, all
    documented in the Zapier & Webhooks and Platform Integrations collections of its help center.
  humanURL: https://help.helloaudio.fm/en/collections/14938214-zapier-webhooks
  aid: hello-audio:hello-audio-api
- name: Hello Audio MCP Server
  description: Remote Model Context Protocol server that gives an AI assistant read-only access to the feeds on a signed-in
    Hello Audio account (downloads, listeners, retention and similar figures); it cannot upload or edit episodes, change listeners
    or change feed settings. Sign-in is OAuth against auth.helloaudio.fm with the mcp:access scope. Claude's connector directory
    lists the endpoint and 15 tool names published by Hello Audio (list_feeds, whoami, get_feed_summary, get_active_listeners
    and others). Anonymous tools/list returns 401, so the live tool schemas were not read.
  humanURL: https://help.helloaudio.fm/en/articles/17761552-how-do-i-connect-hello-audio-to-claude-with-the-mcp-connector
  baseURL: https://mcp.helloaudio.fm/mcp
  tags:
  - MCP
  properties:
  - type: Documentation
    url: https://help.helloaudio.fm/en/articles/17761552-how-do-i-connect-hello-audio-to-claude-with-the-mcp-connector
  - type: MCPServer
    url: https://mcp.helloaudio.fm/mcp
  aid: hello-audio:hello-audio-mcp-server
x-submission-probe: 200, 2026-10-26
x-coverage:
  state: gated
  reason: auth-required
  detail: Hello Audio publishes no REST, GraphQL or AsyncAPI contract; its one machine interface, the remote MCP server at
    mcp.helloaudio.fm/mcp, answers initialize and tools/list with 401 'Missing bearer token' and points to OAuth at auth.helloaudio.fm,
    so tool schemas are readable only after signing in to a Hello Audio account.
  evidence:
  - url: https://mcp.helloaudio.fm/mcp
    status: 401
  - url: https://mcp.helloaudio.fm/.well-known/oauth-protected-resource/mcp
    status: 200
  - url: https://help.helloaudio.fm/en/articles/17761552-how-do-i-connect-hello-audio-to-claude-with-the-mcp-connector.md
    status: 200
  checked: '2026-11-04'
x-enrichment:
  date: '2026-11-04'
  status: nochange
  artifacts_added: 0
  pass: modular-v1
  engine: identity=anthropic,contract=anthropic,surfaces=anthropic,docs=anthropic,regulatory=anthropic

Hello Audio API — frequently asked questions

Does Hello Audio have an API?

Yes. APIs.io lists 2 APIs from Hello Audio, including Hello Audio API and Hello Audio MCP Server.

How do I authenticate with the Hello Audio API?

Hello Audio uses bearer-token authentication (3 schemes). The details are profiled on APIs.io as Hello Audio Authentication.

How much does the Hello Audio API cost?

Hello Audio publishes its prices; its Starter (annual billing) plan is $14/ PER MONTH BILLED ANNUALLY as of 2026-10-28. APIs.io lists 7 pricing plans for Hello Audio, with each plan's price, limits and inclusions under Pricing on this page.

Does Hello Audio have an MCP server?

Yes. APIs.io lists 1 MCP server for Hello Audio.

Is the Hello Audio API ready for AI agents?

Hello Audio has a Kin Score of 45.1 out of 100 (developing) and an Agent Readiness score of 11.3 (agent-aware), scored by API Evangelist on 2026-11-21.

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/hello-audio"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/hello-audio/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/hello-audio/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

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