heard-dev
Heard is a macOS voice layer for coding agents, turning agent activity into concise spoken updates. It integrates with Claude Code, Codex, and other AI coding assistants, providing real-time narration of progress, decisions, failures, and completed work. Users can download the app, connect agents, and customize listening modes such as Co-pilot, Companion, and Focus. The platform offers free and paid plans, with pricing details, and maintains open-source components on GitHub. It emphasizes privacy, with data processed locally unless optional hosted services are enabled.
heard-dev is listed with 2 APIs on the APIs.io network. Tagged areas include Company, AI, Voice, macOS, and DeveloperTools.
The heard-dev catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.
heard-dev’s developer surface includes CLI, changelog, documentation, API reference, getting-started guide, support, engineering blog, and 19 more developer resources.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
Heard API
Heard is a macOS voice layer for coding agents.
heard-dev API
heard-dev API as documented publicly: 1 operations. Contract generated from the documentation by API Evangelist (2026-10-30); not the provider's own document.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Pricing Plans 1
Published pricing tiers and plan structures.
Semantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Heard Dev Context
JSON-LDSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
heard-dev API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions for this provider's data models.
GetDownloadCcResponse
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
heard-dev API — frequently asked questions
Does heard-dev have an API?
Yes. APIs.io lists 2 APIs from heard-dev, including Heard API and heard-dev API.
Is there an OpenAPI specification for the heard-dev API?
Yes. APIs.io indexes 1 OpenAPI specification for heard-dev, each linked for download from this page.
How do I authenticate with the heard-dev API?
heard-dev documents its authentication (0 schemes). The details are profiled on APIs.io as Heard Dev Authentication.
How much does the heard-dev API cost?
APIs.io lists 2 pricing plans for heard-dev, with each plan's price, limits and inclusions under Pricing Plans on this page.
Does heard-dev have an MCP server?
Yes. APIs.io lists 1 MCP server for heard-dev: Remote MCP server at docs.heard.dev.
Is the heard-dev API ready for AI agents?
heard-dev has a Kin Score of 38.5 out of 100 (thin) and an Agent Readiness score of 38.0 (agent-ready), scored by API Evangelist on 2026-10-31.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.