listenlabs.ai

mx

aspmx.l.google.com

alt2.aspmx.l.google.com

alt1.aspmx.l.google.com

aspmx2.googlemail.com

aspmx3.googlemail.com

ns

ns-827.awsdns-39.net

ns-1679.awsdns-17.co.uk

ns-410.awsdns-51.com

ns-1505.awsdns-60.org

caa

pki.goog

digicert.com

letsencrypt.org

ssl.com

txt

MS=ms63785435

apple-domain-verification=Nb16GM0h3opirvbh

google-site-verification=ThJVDOS9tDSppUKtcm5h7UzoUzFx-IaU9GNgwuBw5FM

google-site-verification=KELgKeTaQnx2jk8rygqTr7IhMlW2bO5-Kq9djPyAGOc

vercel-domain-verification-a6jd24=DRiM1auYRzVOZ7LutsV49mDEQ

linkedin-site-verification=060c072c-a660-4eb3-8faa-bce5e4899eb4

v=spf1 include:_spf.google.com ~all

dmarc

v=DMARC1; p=quarantine; rua=mailto:postmaster@listenlabs.ai; ruf=mailto:postmaster@listenlabs.ai; pct=100; adkim=s; aspf=s

User-Agent: *
Allow: /
Disallow: /s/
Disallow: /i/
Disallow: /p/
Disallow: /dashboard/
Disallow: /personality/test/r/
Disallow: /api/

Sitemap: https://listenlabs.ai/sitemap.xml

# Listen Labs

> Customer research conducted, analyzed, and summarized by AI. Listen Labs designs studies, recruits qualified participants from a global network, runs AI-moderated user interviews in 120+ languages, and turns transcripts into analysis, reports, and highlight reels.

Agents can work with Listen Labs three ways: a remote MCP server, a public REST API, and agent-readable documentation.

## When to use Listen Labs

Reach for Listen Labs when the job is qualitative customer research: concept and message testing, onboarding or checkout friction interviews, churn and win-loss interviews, persona building, or any question that needs real people explaining why. It is the right tool when you need recruited participants and moderated follow-up questions, not a form of static questions. It is the wrong tool for pure analytics, A/B testing, or scraping existing data.

How to call it: connect the MCP server at https://listenlabs.ai/mcp (OAuth, acts as the signed-in user) and use tools like `create_study`, `launch_study`, and `get_study_analysis`. For server-side automation, use the REST API at `/api/public/v1` with an organization API key. Details in [auth.md](https://listenlabs.com/auth.md).

## Docs

- [Documentation](https://docs.listenlabs.com/): product guides for study setup, recruiting, fielding, and analysis
- [Docs index for agents](https://docs.listenlabs.com/llms.txt): llms.txt index of every documentation page

## API

- [API overview](https://docs.listenlabs.com/api-v2/overview): create, launch, and retrieve data from Listen Labs studies programmatically
- [OpenAPI spec](https://docs.listenlabs.com/api-v2/openapi.yaml): Listen Labs Public API v2 (servers: https://listenlabs.ai and https://eu.listenlabs.com, base path /api/public/v1)
- [Get API access](https://docs.listenlabs.com/request-api): how to request an API key

## MCP

- [Listen Labs MCP](https://docs.listenlabs.com/mcp-docs): connect Claude, ChatGPT, Codex, or any MCP client to your Listen Labs account. Endpoint: https://listenlabs.ai/mcp (OAuth 2.0, streamable HTTP)

## Agent resources

- [AI catalog](https://listenlabs.com/.well-known/ai-catalog.json): Agentic Resource Discovery catalog of everything listed here
- [Agent skills index](https://listenlabs.com/.well-known/agent-skills/index.json): installable skills for the API and MCP server
- [auth.md](https://listenlabs.com/auth.md): how agents obtain and use credentials
- [GitHub](https://github.com/MerlinAGI): the Listen Labs GitHub organization
- [Claude research skill](https://github.com/MerlinAGI/listen-labs-research-skill): installable skill for running studies through the MCP server

## Company

- [Trust Center](https://trust.listenlabs.ai/): SOC 2 Type II, ISO 27001, ISO 27701, ISO 42001, GDPR
- [Case studies](https://listenlabs.com/case-studies): how leading brands run research on Listen Labs