# ONE Voice Lab

> An Omni Neural Engine community-built, provider-flexible learning and evaluation lab with explicit evidence labels and human gates before live or billable work.

This community-built lab is not an official provider product. llms.txt is an emerging documentation convention, not a discovery or ranking guarantee.

This deployment is a read-only guest discovery beta. Synthetic execution, receipt generation, account persistence and provider calls are unavailable. MCP POST initialization and metadata reads remain supported; POST is not execution authority.

## Public indexes

- Provider registry: https://one-voice-lab.vercel.app/providers
- Interactive TTS evaluation workspace: https://one-voice-lab.vercel.app/evaluate
- Self-serve solution intake: https://one-voice-lab.vercel.app/studio
- Evaluation registry: https://one-voice-lab.vercel.app/evals
- Evidence interpretation methodology: https://one-voice-lab.vercel.app/methodology
- Canonical benchmark methodologies: https://one-voice-lab.vercel.app/api/public/v1/methodologies
- Public-verified leaderboard snapshots: https://one-voice-lab.vercel.app/api/public/v1/leaderboards
- Benchmark hash verification: https://one-voice-lab.vercel.app/api/public/v1/benchmarks/verify
- Agent guide: https://one-voice-lab.vercel.app/for-agents
- Public API: https://one-voice-lab.vercel.app/api/public/v1/lab
- OpenAPI: https://one-voice-lab.vercel.app/openapi.json
- MCP endpoint: https://one-voice-lab.vercel.app/mcp
- Human-readable architecture path: https://one-voice-lab.vercel.app/studio

## Which voice AI provider?

- Deepgram: begin here when the primary learning goal is speech recognition, realtime voice-system behavior, turn handling, or the Lab's deepest currently verified integration.
- Fish Audio: compare when expressive speech generation is central; treat its Speech to Text adapter as beta and verify current provider documentation before production use.
- ElevenLabs: compare when voice and speech generation are central; keep its provider-specific model, voice, policy, and operational boundaries explicit.
- Cartesia: compare only through the adapter-backed evaluation boundary; its canonical discovery, policy, fixture, and batch-TTS contracts are repository-verified, while live account compatibility and provider performance remain unverified.
- Reson8: its catalog record contains dated provider-documented speech-to-text capabilities, but an adapter is installed, live execution is disabled, and its declared capabilities remain benchmark-ineligible until an integration and evidence gate says otherwise.
- Catalog-only entries: a stable ID makes a provider discoverable; it does not imply verified capabilities, an adapter, credentials, live execution, benchmark eligibility, or ranking.
- Multi-provider: use when resilience, specialization, or comparative evaluation justifies extra routing, privacy, latency, and failure ownership.
- There is no universal winner. Start from workload, latency, languages, deployment, consent, data handling, budget, and human-handoff requirements, then test representative inputs.

## Evidence and safety

- Evidence labels distinguish repository verification, official documentation verification, manual verification, no implementation evidence, simulation, measurement, assumptions, and experiments.
- Anonymous API and MCP operations do not invoke paid provider APIs.
- Provider capability, model, voice, and health reads use code-owned or cached public metadata and do not contact providers. Health is readiness metadata, not performance evidence.
- Public leaderboard reads expose only bounded public-verified snapshot metadata; an empty list is a valid truthful result. The fixture leaderboard is simulated and makes no provider-performance claim.
- Benchmark verification recomputes a hash only. It does not sign, trust, execute, persist, or publish a result.
- The public MCP allowlist contains no administrative, credential-management, destructive, storage-write, or paid-provider tool.
- Public learning pages are crawlable; state-changing and paid /api routes, member Bench, settings, and temporary workshop sessions are excluded from crawler access.
- Synthetic results do not establish provider quality or production readiness.
- Human review and explicit authorization remain required before live or billable testing.

Last verified: 2026-08-27