Overhear for agents and developers

Overhear translates spoken audio into bilingual subtitles as it is spoken. If you are an agent, an aggregator, or a developer integrating on someone's behalf, you do not need to scrape this site: the inventory, prices, availability and policies are published as JSON, the useful action is an authenticated endpoint, and the same surface is exposed as an MCP server.

1. Discover

GET /.well-known/agent.json: the manifest; start here.
GET /api/catalog: products, offers with USD prices, included hours, overage, the 39 target languages, availability, policies and every endpoint below.
GET /api/policies: refunds (none for partial months; cancelling keeps access to period end), data retention (audio is not stored), agent-use terms and rate limits.
GET /api/availability: live status of the free trial, the agent action and billing, uncached.
GET /openapi.json: OpenAPI 3.1 for all of it. GET /llms.txt: the plain-text summary.

2. Authenticate

POST /api/agent/keys with {"email": "you@example.com"}. The key is emailed to that address (that is how the address is verified; the response never contains the key). Send it as Authorization: Bearer <key>. Each key carries 10 free minutes of audio in total. Keys are revocable on request to support@overhearapp.com.

3. Act

POST /api/agent/translate with {"audio_url": "https://…", "target_language": "en"}. The audio is fetched by the speech provider (nothing is uploaded to Overhear), recognised with per-word confidence, translated by Claude with the recogniser's doubtful words as hints, and returned as timed segments plus SRT (translation-only and bilingual). Up to 15 minutes per request, 30 requests per key per hour. Minutes are metered on the audio's real duration, rounded up to a tenth of a minute.

When a key's free minutes are used up the action answers 402 with a purchase object. Today that object says planned: there is no way to buy minutes yet. When accounts and card payments ship, the same field will carry the checkout link and the catalog's offers will switch from planned to available. Nothing else in the contract will change.

4. MCP

POST /api/mcp is an MCP server (Streamable HTTP, protocol 2025-06-18, stateless, JSON responses) with the tools get_catalog, get_policies, check_availability, request_api_key andtranslate_audio. The translate tool takes the key as an api_key argument or a bearer header. Read tools need no key.

5. What to expect

Errors are JSON with error and a stable code; the OpenAPI document lists them per endpoint.
CORS is open on every endpoint above, so browser-hosted agents can call them directly.
Accuracy: on the September 2026 test corpus, clean audio translates correctly on first showing about 92% of the time, crowd noise around 75%; the automatic second pass lifts both. Confidence is returned per segment so you can decide what to trust.
Breaking changes will bump version in the manifest and catalog; the previous shape stays available for 90 days.

Questions, higher limits, or a partnership: support@overhearapp.com. Terms: /terms. Privacy: /privacy.