Eargo

Eargo was a San Jose, California direct-to-consumer medical device company that designed and sold rechargeable, virtually invisible in-canal hearing aids for adults with mild to moderate hearing loss, founded in 2010 as Aria Innovations and listed on Nasdaq in 2020. In 2025 Eargo merged with South Africa's hearX Group to form LXE Hearing, combining Eargo's direct-to-consumer platform with the Lexie and Go Hearing over-the-counter brands. In 2026 LXE Hearing began winding down its US operations after restructuring efforts failed, and the eargo.com website has been reduced to a single wind-down notice page. Eargo never operated a public developer program, developer portal, or documented API: the hearing aids paired with a consumer mobile application backed by a private, undocumented service host at api.eargo.com.

Eargo is profiled on the APIs.io network. Tagged areas include Company, Hearing Aids, Medical Devices, Consumer Health, and Direct to Consumer.

Eargo’s developer surface includes support and 9 more developer resources.

7.7/100 minimal ▬ flat Agent 7/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
0 APIs
CompanyHearing AidsMedical DevicesConsumer HealthDirect to ConsumerHearing HealthDigital HealthDefunct

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 7.7/100 · minimal
Contract Quality 0.0 / 21
Developer Ergonomics 0.7 / 17
Commercial Clarity 0.0 / 17
Operational Transparency 0.0 / 11
Governance 0.0 / 10
Discoverability 5.8 / 9
Regulatory Posture 1.1 / 15
Agent readiness — 7/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Health 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.
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/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/eargo: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Pricing Plans 1

Published pricing tiers and plan structures.

Eargo Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Eargo Rate Limits

0 limits

RATE LIMITS

Security Posture 1

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

Eargo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: eargo
name: Eargo
description: 'Eargo was a San Jose, California direct-to-consumer medical device company that designed and sold rechargeable,
  virtually invisible in-canal hearing aids for adults with mild to moderate hearing loss, founded in 2010 as Aria Innovations
  and listed on Nasdaq in 2020. In 2025 Eargo merged with South Africa''s hearX Group to form LXE Hearing, combining Eargo''s
  direct-to-consumer platform with the Lexie and Go Hearing over-the-counter brands. In 2026 LXE Hearing began winding down
  its US operations after restructuring efforts failed, and the eargo.com website has been reduced to a single wind-down notice
  page. Eargo never operated a public developer program, developer portal, or documented API: the hearing aids paired with
  a consumer mobile application backed by a private, undocumented service host at api.eargo.com.'
url: https://raw.githubusercontent.com/api-evangelist/eargo/refs/heads/main/apis.yml
image: https://www.eargo.com/assets/content/dam/eargo/samples/logo_white.png
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.20'
created: '2026-08-12'
modified: '2026-08-12'
tags:
- Company
- Hearing Aids
- Medical Devices
- Consumer Health
- Direct to Consumer
- Hearing Health
- Digital Health
- Defunct
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.eargo.com/
- type: ParentCompany
  url: https://lxehearing.com/
- type: Support
  url: mailto:support@eargo.com
- type: HelpCenter
  url: https://help.eargo.com/
- type: LLMsTxt
  url: llms/eargo-llms.txt
- type: DomainSecurity
  url: security/eargo-domain-security.yml
- type: Lifecycle
  url: lifecycle/eargo-lifecycle.yml
- type: Packages
  url: packages/eargo-packages.yml
- type: Plans
  url: plans/eargo-plans-pricing.yml
- type: RateLimits
  url: rate-limits/eargo-rate-limits.yml
x-enrichment:
  date: '2026-08-12'
  status: minimal
  artifacts_added: 7
  pass: local-v1
x-coverage:
  state: none
  reason: defunct
  detail: 'Round two enumerated eargo.com by DNS and found four hosts the first pass missed — app.eargo.com still serves a
    live Rails "Eargo Web App" storefront and help.eargo.com serves a real 16.6KB llms.txt of 106 consumer support articles
    — but there is still no API anywhere: api.eargo.com answers 403 on /openapi.json, /swagger.json, /api-docs and /graphql
    behind a Cloudflare bot challenge, and every other host is a soft-404 shell or an unreachable retired storefront.'
  evidence:
  - url: https://help.eargo.com/llms.txt
    status: 200
  - url: https://app.eargo.com/
    status: 200
  - url: https://api.eargo.com/openapi.json
    status: 403
  - url: https://api.eargo.com/graphql
    status: 403
  - url: https://www.eargo.com/
    status: 200
  - url: https://shop.eargo.com/
    status: 301
  - url: https://store.eargo.com/
    status: 0
  - url: https://developer.eargo.com/
    status: 0
  - url: https://api.github.com/orgs/eargo
    status: 404
  checked: '2026-08-12'