~/ domain/unmute.ai.mdTHE AGENT-READABLE WEB

unmute.ai valid

Unmute

A declarative standard for voice agents. Describe the agent once, compile it to SLNG, LiveKit, Pipecat, or Twilio.

Visit publisher ↗
Authority
45 reach 0 · trust 10 · quality 20 · freshness 15
Tier
listed
llms.txt
https://unmute.ai/llms.txt
llms-full.txt
https://unmute.ai/llms-full.txt
Sections
0
Links
149
Size
25479 bytes
Registered
2023-08-28
Country
— Publisher location unknown; CDN address excluded
Country evidence
No published address evidence collected yet
For agents
Documentation: developer or product docs worth reading, nothing to call
First seen
2026-10-25T18:57:47.579Z
Last checked
2026-10-25T18:57:55.839Z
Badge
Agent Web Map badge for unmute.ai

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T18:57:47.624Z. Cached copy · Source on unmute.ai

# Unmute

> A declarative standard for voice agents. Describe the agent once, compile it to SLNG, LiveKit, Pipecat, or Twilio.

> ## Agent Instructions
> Unmute compiles to exactly four targets. Pipecat and LiveKit are code targets: compile writes a Python project you run. SLNG is a hosted target: compile writes a deployment body and SLNG runs the agent, so it has no `unmute dev`. Twilio compiles to a small Python app that Twilio ConversationRelay calls; you host it, and it has no `unmute dev` either. Those four are the only values `provider` accepts in `targets.yaml`. Deepgram and ElevenLabs appear in these docs as model vendors, which is not the same thing as a target, and `slng` is both.
> The Go structs in `internal/spec` and `internal/ir` are the schema truth. Check a field against them, or run `unmute validate`, rather than against what you remember.

- [Unmute](https://unmute.ai/index.md): A declarative standard for voice agents. Describe the agent once, compile it to SLNG, LiveKit, Pipecat, or Twilio.
- [Installation](https://unmute.ai/start/installation.md): Install Unmute on macOS, Windows, or Linux and check the one Quickstart prerequisite.
- [Quickstart](https://unmute.ai/start/quickstart.md): Scaffold an agent, add two keys, and talk to it in your browser.
- [Coding agents](https://unmute.ai/start/coding-agents.md): Optional setup for supported coding assistants, followed by one checked voice-agent build.
- [How Unmute works](https://unmute.ai/start/how-unmute-works.md): The four stages between your package and what each target runs.
- [Your first agent](https://unmute.ai/build/your-first-agent.md): The smallest real agent: a prompt, four models, and one file that says who is answering.
- [How a package fits together](https://unmute.ai/build/how-a-package-fits-together.md): One rule explains the whole file: an agent owns what it can do, and writes each one where it uses it.
- [Variables](https://unmute.ai/build/variables.md): Declare a value once in state.py, fill it during the call, and read it only where it is needed.
- [Credentials](https://unmute.ai/build/credentials.md): Give the agent an API key without putting one in your package.
- [Pre-fetch](https://unmute.ai/build/prefetch.md): Run a lookup before the call starts, when you already have everything it needs.
- [Tools](https://unmute.ai/build/tools/overview.md): What a tool is, the eight ways one can run, how each target treats them, and how you attach one to an agent.
- [Webhook tools](https://unmute.ai/build/tools/webhook.md): Call your own API: a URL from the environment, a path that renders per call, and values the model never sees.
- [Python tools](https://unmute.ai/build/tools/python.md): A handler of your own in the package: what it receives, what it returns, and where it is copied.
- [MCP servers](https://unmute.ai/build/tools/mcp.md): Point the agent at a remote MCP server and let it offer that server's tools.
- [Prebuilt tools](https://unmute.ai/build/tools/prebuilt
…

Machine-readable: GET /v1/resolve?q=unmute.ai · GET /v1/domain/unmute.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Own or manage this website?

If you own or manage unmute.ai, you can update its listing and review file health, discovery activity and score history.

Manage this listing — optional

What verification unlocks

See how your site is discovered—and control what agents see.

  • See your website in the map

    Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.

  • Control what agents see

    Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.

  • Make your profile eligible for search

    A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.

  • Appear in our llms-full.txt

    Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.

Free. No account registration, backlink or payment required. Public discovery remains available without verification.

Verify your website—free

Preview the owner dashboard · All verification benefits

Let your coding agent verify it

If your coding agent is authorized to manage this website, paste these instructions into it.

Claim my listing on Agent Web Map for unmute.ai:
1. POST https://agentwebmap.com/v1/sites/unmute.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://unmute.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/unmute.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/unmute.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.

agent web map / a clearer way in.API & MCP · Contact