{ "data": { "a": { "slug": "deepgram-voice-agent", "name": "Deepgram Voice Agent API", "vendor": "Deepgram", "vendorUrl": "https://deepgram.com", "kind": "http-api", "category": "voice-agents", "summary": "One WebSocket that runs Deepgram STT (Flux or Nova-3), a managed or bring-your-own LLM and Deepgram or third-party TTS, with turn-taking, barge-in and function calling.", "url": "https://www.anchorterminal.com/tools/deepgram-voice-agent", "markdownUrl": "https://www.anchorterminal.com/tools/deepgram-voice-agent.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/deepgram-voice-agent.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/deepgram-voice-agent.json", "dns": "deepgram-voice-agent.grade.anchorterminal.com", "repo": "https://github.com/deepgram/deepgram-python-sdk", "license": "MIT (SDKs)", "transports": [ "http", "streamable-http", "stdio", "sse" ], "remoteUrl": "https://agent.deepgram.com/v1/agent", "packages": [ { "registry": "npm", "name": "@deepgram/sdk" }, { "registry": "pypi", "name": "deepgram-sdk" }, { "registry": "pypi", "name": "deepctl" } ], "auth": "api-key", "authNotes": "`Authorization: Token \u003ckey\u003e` header on REST and WebSocket calls. Short-lived JWTs (30-second TTL) from the token endpoint for browsers. The `dg` CLI MCP server uses `dg login` credentials or `DEEPGRAM_API_KEY`. The docs MCP needs no key. BYO LLM and TTS providers take their own keys in the `endpoint.headers` of the Settings message.", "pricing": "usage", "pricingNotes": "Billed per minute of WebSocket connection time. Standard $0.075 a minute pay as you go ($0.068 Growth), Standard with your own TTS $0.065 ($0.051 Growth), your own LLM $0.065 ($0.059 Growth), your own LLM and TTS $0.050 ($0.041 Growth). Advanced tier (larger LLMs such as GPT-5 or Claude Sonnet) $0.163 ($0.146 Growth), or $0.122 with your own TTS ($0.110 Growth). $200 free credit with no card. Carrier costs are extra (https://deepgram.com/pricing).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402 or machine payment in the docs or pricing. Card or prepaid credits only (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 468, "npmWeekly": 1123798, "pypiWeekly": 805026, "asOf": "2026-09-30" }, "docsUrl": "https://developers.deepgram.com/docs/voice-agent", "llmsTxt": "https://developers.deepgram.com/llms.txt", "capabilities": [ "voice.agent", "voice.pipeline", "voice.tools" ], "tags": [ "hosted", "no-card", "closed-source", "python", "typescript", "llms-txt", "mcp", "streaming", "pipeline", "enterprise", "self-hosted" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 72.2, "grade": "BB", "agentReady": true, "rank": 135, "ranked": true, "rankOf": 1486, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 85, "payments": 40, "reliability": 75, "schema": 90, "security": 71, "transparency": 78 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "$0.075 a minute all in on Standard, $0.050 with your own LLM and TTS, and $200 of credit with no card. Every status incident since August was partial. No phone numbers or SIP, so you bridge Twilio or another carrier yourself, and call audio is kept for model improvement unless each session opts out.", "bestFor": "Developers who already run telephony (Twilio, Amazon Connect, Genesys, AudioCodes) and want a cheap managed pipeline with their choice of LLM.", "strengths": [ "$0.075 a minute all in on Standard, $0.050 with your own LLM and TTS, $200 of credit with no card", "AsyncAPI description of the agent socket plus a public OpenAPI file", "Role-based API keys with expiry and 30-second browser tokens", "SDKs in Python, JavaScript, Java, Go, .NET and Rust, the Python and JavaScript ones released on 28 October 2026", "Function-call hold that waits for a confirmed user turn before irreversible tools run" ], "weaknesses": [ "No phone numbers or SIP, so you bridge Twilio or another carrier yourself", "Nineteen status incidents from 3 August to 29 October, each partial, one of them failing Voice Agent sessions at one datacenter on 29 October", "Call audio is kept for model improvement unless `mip_opt_out` is set, and the 2021 privacy policy doesn't mention it", "No SLA terms on self-serve plans", "Sessions end at 2 hours" ], "agentNotes": [ "Set `mip_opt_out` in the Settings message to keep call audio out of training", "Use the function-call hold for anything irreversible, since replies can start before the user's turn is confirmed", "Back off exponentially on 429, a pay-as-you-go project gets 45 concurrent sockets", "Pin the LLM version, an unpinned Gemini route failed for 1.5 hours on 21 July 2026", "Mint browser tokens with `ttl_seconds`, not `ttl`, or they expire after 30 seconds" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.2 } ], "editorialScores": { "ergonomics": 67, "maintenance": 85, "payments": 40, "reliability": 75, "schema": 90, "security": 71, "transparency": 60 }, "provenanceScore": 95, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://agent.deepgram.com/v1/agent/settings/think/models \\\n -H \"Authorization: Token $DEEPGRAM_API_KEY\"", "claudeCode": "claude mcp add deepgram-docs --transport http https://api.dx.deepgram.com/kapa/mcp", "config": { "mcpServers": { "deepgram": { "args": [ "mcp" ], "command": "dg", "env": { "DEEPGRAM_API_KEY": "${DEEPGRAM_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/deepgram-voice-agent" }, "sameCompany": [ "deepgram-stt", "deepgram-tts" ], "area": "voice", "unitPrices": [ { "item": "Standard", "unit": "call-minute", "usd": 0.075, "note": "pay as you go, Deepgram STT, managed LLM and TTS included, carrier extra" }, { "item": "Standard with own TTS", "unit": "call-minute", "usd": 0.065 }, { "item": "Own LLM", "unit": "call-minute", "usd": 0.065, "note": "Deepgram STT and TTS, your own LLM" }, { "item": "Own LLM and TTS", "unit": "call-minute", "usd": 0.05, "note": "STT and orchestration only" }, { "item": "Advanced", "unit": "call-minute", "usd": 0.163, "note": "larger LLMs, all-in except carrier" }, { "item": "Advanced with own TTS", "unit": "call-minute", "usd": 0.122 } ], "provenance": { "legalEntity": "Deepgram, Inc.", "domain": "deepgram.com", "domainRegistered": "2016-01-28", "endpointOnVendorDomain": true, "terms": "https://deepgram.com/terms", "privacy": "https://deepgram.com/privacy", "statusPage": "https://status.deepgram.com", "changelog": "https://developers.deepgram.com/changelog", "securityTxt": "valid", "checked": "2026-11-01", "notes": [ "https://deepgram.com/.well-known/security.txt answered 200 on 1 November 2026 with Contact mailto:security@deepgram.com and Expires 2027-09-30T00:00:00.000Z. It was not found on 30 September." ], "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/deepgram-voice-agent.json", "live": { "slug": "deepgram-voice-agent", "probe": { "target": "https://agent.deepgram.com/v1/agent", "method": "get", "lastAt": "2026-11-07T18:20:20.266081047Z", "lastOk": true, "lastStatus": 404, "lastMs": 460, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 401, "p95ms24h": 512, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.deepgram.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:00.994341829Z" }, "versions": [ { "registry": "github", "name": "deepgram/deepgram-python-sdk", "version": "v7.17.0", "released": "2026-11-04", "seenAt": "2026-11-06T23:20:24.910394663Z" }, { "registry": "npm", "name": "@deepgram/sdk", "version": "5.18.0", "seenAt": "2026-11-06T23:20:22.644100995Z" }, { "registry": "pypi", "name": "deepctl", "version": "0.4.0", "released": "2026-10-20", "seenAt": "2026-11-06T23:20:22.978980994Z" }, { "registry": "pypi", "name": "deepgram-sdk", "version": "7.17.0", "released": "2026-11-04", "seenAt": "2026-11-06T23:20:22.869617831Z" } ], "githubStars": 479, "npmWeekly": 1352542, "pypiWeekly": 917348, "securityTxt": { "url": "https://deepgram.com/.well-known/security.txt", "state": "valid", "expires": "2027-09-30T00:00:00.000Z", "checkedAt": "2026-11-07T16:01:56.590929452Z" }, "llmsTxt": { "url": "https://developers.deepgram.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:19.56139377Z" }, "domain": { "domain": "deepgram.com", "registered": "2016-01-28", "source": "https://rdap.verisign.com/com/v1/domain/deepgram.com", "checkedAt": "2026-11-01T14:09:32.822991287Z" }, "github": { "repo": "deepgram/deepgram-python-sdk", "checkedAt": "2026-11-02T08:43:22.258450881Z", "stars": 476, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T19:47:20Z", "openIssues": 14, "openPRs": 8, "issuesOpened90d": 24, "issuesClosed90d": 30, "prsMerged90d": 38, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-30T17:09:16Z" }, "replies": { "sampled": 25, "unanswered": 12, "medianDays": 4.6 } }, "updatedAt": "2026-11-07T18:20:20.266081047Z" } }, "answer": "Deepgram Voice Agent API scores 72.2 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing.", "b": { "slug": "fone-me", "name": "fone.me", "vendor": "Fone", "vendorUrl": "https://www.fone.me", "kind": "platform", "category": "voice-agents", "summary": "fone.me is a hosted AI agent at a personal link that answers calls and messages for a person or small business over web chat, voice, WhatsApp, Telegram and a Premium number. Other agents reach it through keyless MCP and A2A.", "url": "https://www.anchorterminal.com/tools/fone-me", "markdownUrl": "https://www.anchorterminal.com/tools/fone-me.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fone-me.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fone-me.json", "dns": "fone-me.grade.anchorterminal.com", "license": "Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published", "transports": [ "streamable-http" ], "remoteUrl": "https://www.fone.me/mcp", "packages": [], "auth": "none", "authNotes": "No credential for callers. llms.txt gives the MCP server at https://www.fone.me/mcp as Streamable HTTP with auth 'none', and the README of the GitHub repository spearisa/fone-me-mcp says 'public, like the links themselves'. The A2A agent cards read (demo and maxr) declare no securitySchemes or security. The search API at /api/agents/search takes a query with no key per llms.txt. Owners sign in with Apple, Google or email to set up an agent; no owner API key, scopes or tokens are documented.", "pricing": "freemium", "pricingNotes": "The agent, the first link and the website chat button are free. Premium is $9.99 a month (llms.txt and https://www.fone.me/alternatives/smith-ai) and adds the agent's own phone number, calling minutes and more links, with cancellation at any time; no page read gives the minute allowance, the number of links, the countries for numbers or the payment method. Outbound calls use Premium minutes and international calls use more minutes per minute. Callers and outside agents pay nothing (checked 2026-11-05).", "priceSummary": "$9.99 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the guide pages read, the MCP repository README and server.json, or the two agent cards (checked 2026-11-05). The MCP server and A2A endpoints are free and keyless; Premium is a monthly subscription with no payment route stated.", "endpoints": [] }, "toolCount": 4, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-05" }, "docsUrl": "https://www.fone.me/llms.txt", "llmsTxt": "https://www.fone.me/llms.txt", "capabilities": [ "voice.agent", "voice.telephony", "voice.calls", "messaging.whatsapp", "messaging.inbound" ], "tags": [ "hosted", "official", "closed-source", "mcp", "remote-mcp", "no-auth", "keyless", "a2a", "llms-txt", "whatsapp", "telegram", "ios", "freemium", "free-tier", "no-status-page" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 28.3, "grade": "F", "agentReady": false, "rank": 1406, "ranked": true, "rankOf": 1486, "categoryRank": 26, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 29, "maintenance": 23, "payments": 50, "reliability": 15, "schema": 31, "security": 30, "transparency": 23 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-05" }, "negative": 0, "verdict": "Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named.", "bestFor": "Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.", "strengths": [ "Keyless MCP server and per-link A2A endpoints let any agent find, look up and message a person's or business's agent without an account or payment", "Agent cards follow A2A 0.3.0 with skills, input and output modes and a JSON-RPC transport, readable at an address robots.txt allows", "Outbound calls disclose the agent and transcription, run only 8 am to 9 pm in the callee's time zone and stop permanently on a do-not-call request", "Owners see every call and chat with a transcript in one inbox, can take over at any time and approve what the agent will say before it calls", "Free agent, first link and website chat button, with Premium at $9.99 a month for a number and calling minutes" ], "weaknesses": [ "No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints", "message_agent and A2A reach any person's agent with no caller identity, and no spam, rate or abuse control for that channel is documented", "The terms, privacy policy, data-deletion page, FAQ and support page draw by script, and no company, address or country of incorporation is named on any page read", "No status page, changelog, security.txt, SLA or published minute allowance for Premium", "robots.txt disallows the /mcp, /api/ and /*/a2a paths that llms.txt advertises to agents" ], "agentNotes": [ "Connect to https://www.fone.me/mcp with no credentials; use find_agents or get_agent before message_agent so the message goes to the right person's link.", "Say who you are acting for in every message_agent call; the owner reads it in an inbox as a named conversation, and conversations continue across calls.", "Treat replies as the owner's agent speaking from what it was taught, not a commitment; the vendor says it asks its owner before agreeing to anything or spending money.", "Read a link's agent card at /{link}/.well-known/agent-card.json for its skills before using A2A message/send at /{link}/a2a.", "Don't send personal or payment details through message_agent; no retention or privacy terms for agent-to-agent messages could be read." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 28.3 } ], "editorialScores": { "ergonomics": 29, "maintenance": 23, "payments": 50, "reliability": 15, "schema": 31, "security": 30, "transparency": 13 }, "provenanceScore": 32, "checked": { "categories": { "ergonomics": "2026-11-05", "maintenance": "2026-11-05", "payments": "2026-11-05", "reliability": "2026-11-05", "schema": "2026-11-05", "security": "2026-11-05", "transparency": "2026-11-05" }, "last": "2026-11-05", "oldest": "2026-11-05", "stale": false, "staleAfterDays": 90 } }, "connect": { "config": { "mcpServers": { "fone.me": { "type": "http", "url": "https://www.fone.me/mcp" } } } }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/fone-me" }, "area": "voice", "unitPrices": [ { "item": "Premium", "unit": "month", "usd": 9.99, "note": "own fone.me number, calling minutes (allowance not published) and more links; the agent, first link and chat button are free" } ], "provenance": { "legalEntity": "", "domain": "fone.me", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.fone.me/terms", "privacy": "https://www.fone.me/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-05", "notes": [ "No legal entity is named on any page read. Page metadata gives the author and site name as 'Fone', and llms.txt gives San Francisco, CA, USA as a location. The terms, privacy policy and data-deletion page draw their text by script and showed only titles, so whether they name a company is unchecked, not absent.", "The README of github.com/spearisa/fone-me-mcp ends 'Operated by zwilio'. No fone.me page read names zwilio or links the repository, and three web searches found no company of that name, so it is not recorded as the legal entity.", "The MCP server, the search API and the A2A endpoints are on www.fone.me, the vendor's own domain. robots.txt disallows /mcp, /api/ and /*/a2a, so none was fetched; the agent cards it allows were read for two links.", "No status page or changelog found. /.well-known/security.txt answers with the app's HTML shell, recorded as none. /status failed to load.", "RDAP for fone.me, the Wayback Machine, the official MCP registry and the App Store listing (id 6759304762) were not read; each fetch needed an approval that did not come. firstReleased 2025-11-05 is the earliest sitemap lastmod (/sha_krux), a lower bound only, and falls one year to the day before the check, so the sitemap may cap its dates." ], "score": 32 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/fone-me.json", "live": { "slug": "fone-me", "probe": { "target": "https://www.fone.me/mcp", "method": "get", "lastAt": "2026-11-07T18:20:25.611446017Z", "lastOk": true, "lastStatus": 405, "lastMs": 233, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 215, "p95ms24h": 511, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "securityTxt": { "url": "https://fone.me/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:59.997697627Z" }, "llmsTxt": { "url": "https://www.fone.me/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:32.136376991Z" }, "pages": [ { "url": "https://www.fone.me/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:28:42.001987885Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://www.fone.me/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:28:44.174787172Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" } ], "mcpTools": { "url": "https://www.fone.me/mcp", "checkedAt": "2026-11-07T01:44:39.315960369Z", "status": "ok", "note": "answered without the initialize handshake", "tools": [ { "name": "find_agents", "title": "Find people and businesses on fone.me", "description": "Search fone.me for people's and businesses' AI agents by what they do or offer (e.g. 'dog walker', 'real estate agent in Miami', 'Spanish tutor'). Returns their fone.me links.", "inputSchema": { "properties": { "limit": { "description": "How many results (1-10). Default 5.", "type": "number" }, "query": { "description": "What you're looking for, in plain words.", "type": "string" } }, "required": [ "query" ], "type": "object" }, "annotations": { "openWorldHint": true, "readOnlyHint": true, "title": "Find people and businesses on fone.me" } }, { "name": "get_agent", "title": "Look up a fone.me agent", "description": "Get who is behind a fone.me link (e.g. fone.me/samspearin) and what their agent can help with, before messaging it.", "inputSchema": { "properties": { "link": { "description": "A fone.me link or name, e.g. 'fone.me/sam' or 'sam'.", "type": "string" } }, "required": [ "link" ], "type": "object" }, "annotations": { "openWorldHint": true, "readOnlyHint": true, "title": "Look up a fone.me agent" } }, { "name": "message_agent", "title": "Message a fone.me agent", "description": "Send a message to the AI agent at a fone.me link and get its reply — ask a question, request a booking or a quote, or leave a message for the person. The conversation continues across calls. Say who you're asking for in on_behalf_of.", "inputSchema": { "properties": { "link": { "description": "A fone.me link or name, e.g. 'fone.me/samspearin'.", "type": "string" }, "message": { "description": "What to say to the agent.", "type": "string" }, "on_behalf_of": { "description": "The name of the person you're asking for (shown to the owner).", "type": "string" } }, "required": [ "link", "message" ], "type": "object" }, "annotations": { "destructiveHint": false, "idempotentHint": false, "openWorldHint": true, "readOnlyHint": false, "title": "Message a fone.me agent" } }, { "name": "add_chat_to_website", "title": "Add an AI chat button to a website", "description": "Get the one-line code that puts a fone.me AI agent on a website: a chat button in the corner where visitors chat, call by voice, or continue on WhatsApp or Telegram, and the agent answers questions, takes messages and booking requests for the owner. Use it when someone building or editing a website (HTML, Next.js, React, WordPress, Shopify, Wix, Squarespace, Webflow, Framer) wants a chatbot, AI receptionist, live chat or contact widget. Free to start. Give the person's fone.me link if they have one.", "inputSchema": { "properties": { "link": { "description": "The site owner's fone.me link, e.g. 'fone.me/joes-plumbing' or 'joes-plumbing'. Leave out if they don't have one yet.", "type": "string" }, "site": { "description": "What the site is built with: html, nextjs, react, wordpress, shopify, wix, squarespace, webflow, framer. Default html.", "type": "string" } }, "type": "object" }, "annotations": { "openWorldHint": true, "readOnlyHint": true, "title": "Add an AI chat button to a website" } } ], "schemaTokens": 725, "changedAt": "2026-11-07T01:44:39.315960369Z", "check": { "checker": "anchor-check/1.0", "totalTokens": 725, "counts": { "error": 0, "note": 1, "warn": 1 }, "findings": [ { "rule": "TC18", "severity": "warn", "tool": "add_chat_to_website", "message": "readOnlyHint is true but the name says \"add\"", "fix": "If it changes anything, readOnlyHint must be false." }, { "rule": "TC24", "severity": "note", "message": "4 of 4 tools have no outputSchema", "fix": "Declare outputSchema for tools that return structured data, and return structuredContent that matches it." } ] } }, "updatedAt": "2026-11-07T18:20:25.611446017Z" } }, "edges": [ { "by": 62, "category": "maintenance", "leads": "deepgram-voice-agent", "name": "Maintenance \u0026 community", "reasons": { "a": "Changelog entries to 27 October 2026 and the Python and JavaScript SDKs released on 28 October (Python 7.16.0, JavaScript 5.17.0), both adding Voice Agent Think Live messages (30). 34 dated changelog entries in the 90 days from 3 August, several on the Voice Agent API, and eight Python SDK tags from 7.9.0 on 14 September to 7.16.0 on 28 October (20). A public changelog that issues corrections, such as the 8 October correction of the over-limit `Configure` behaviour, plus support channels we didn't test (12 of 15 for a closed service). Official SDKs current in Python, JavaScript, Java, Go, .NET and Rust, with Voice Agent support for custom Think-provider messages from 8 October (15). MIT SDKs with current releases (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.", "b": "Closed service. The newest dated change to the agent surface found is the MCP repository github.com/spearisa/fone-me-mcp, created 5 October 2026 with server.json version 1.0.0, 31 days ago (20). The comparison page marked 'Checked October 28, 2026' and the profile lastmods in the sitemap are content, not releases. No changelog, release notes or three dated changes in 90 days (0 of 20). The support page and FAQ draw by script and no support email, forum or community channel was found; responsiveness unchecked (3 of 15). server.json names the server me.fone.www/agents, a namespace that needs proof of the domain, but the official MCP registry could not be read, so presence is scored absent (0 of 15). No package, public code or CI (0 of 10). 20+0+3+0+0 = 23." }, "scores": { "a": 85, "b": 23 } }, { "by": 60, "category": "reliability", "leads": "deepgram-voice-agent", "name": "Reliability", "reasons": { "a": "Statuspage at status.deepgram.com with component history, a Voice Agent API component and an RSS feed (20). Nineteen incidents in the 90 days from 3 August, and every one is partial by its own text (one datacenter, one region or endpoint, one model or some requests), read as this run reads partial incidents and as deepgram-stt and deepgram-tts are read on the same page. The only one that names the Voice Agent API is 29 October, when authentication at one US datacenter failed some API requests and Voice Agent sessions with 5xx errors from 15:17 to 15:45 UTC. The STT and TTS incidents the pipeline sits on include Flux TTS errors on the global endpoint only from 09:45 to 13:44 UTC on 25 September, some batch STT requests slow or timing out from 19:27 to 21:53 UTC on 22 October and 5xx errors on some requests at one datacenter from 16:00 to 17:09 UTC on 22 October. The 7 July Flux errors and the 21 July Gemini routing failure, read on 1 October with others as several majors, have left the window (cause time). Minor only (20). Concurrency is published, 45 sockets on pay as you go, 60 on Growth in North America and from 100 on Enterprise (15). Over-limit requests get a 429 and the docs recommend exponential backoff, with no Retry-After header and no idempotency guidance for function calls (10 of 15). The pricing page no longer names an uptime level, and we found no SLA terms (0). The Voice Agent API is generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.", "b": "Hosted reading, for the MCP server and A2A endpoints and the service behind them. No status page is linked from llms.txt, the home page or any guide page read, and https://www.fone.me/status failed to load (0). No readable incident history, so the floor (5). No request rate limit for the MCP server, the search API or A2A is published; the only limits are on the agent's own outbound calls (8 am to 9 pm in the callee's time zone, 'limited per day' with no number), which are not request limits (0 of 15). No 429, overload or retry guidance and no idempotency key for message_agent or message/send (0 of 15). No SLA (0). Nothing on the MCP server, the agent cards or llms.txt is marked beta or preview, and the MCP repository's server.json is version 1.0.0 (10). 0+5+0+0+0+10 = 15." }, "scores": { "a": 75, "b": 15 } }, { "by": 59, "category": "schema", "leads": "deepgram-voice-agent", "name": "Schema \u0026 documentation", "reasons": { "a": "Public OpenAPI and an AsyncAPI file that describes the agent socket messages (25). llms.txt with a Markdown copy of each page, and a keyless docs MCP server (10). Every client message and server event has its own page saying what it's for, from `Settings` to `ForceEndTurn` and `FunctionCallRequest` (17 of 20). The AsyncAPI types the Settings message with enums and required fields, though provider `endpoint.headers` are free-form (13 of 15). Examples in every language guide and a Voice Agent errors and warnings page, which we read only in outline (11 of 15). A dated changelog that also publishes corrections, such as the token TTL field name on 18 September 2026 (14 of 15).", "b": "MCP reading, since the MCP server is what an outside agent calls. No tool arguments or input schemas are published in llms.txt, the guide pages or the GitHub README, and robots.txt disallows /mcp, so no session was opened and tools/list was not read. Per-link A2A agent cards are machine-readable JSON (protocol 0.3.0, JSONRPC, input and output modes, skills with examples) and server.json names the remote, but neither types the MCP tools (8 of 25). llms.txt is a real document for agents covering the MCP server, A2A, the search API and the widget (10). Each tool has a one-line purpose in llms.txt and the README, and the how-it-works page states what the agent will and won't do; nothing says when not to use a tool (6 of 20). No typed inputs, enums, constraints or required fields published (0 of 15). Example prompts in the README, per-skill examples in agent cards and widget code for eight site builders; no error response is documented (4 of 15). server.json and the agent cards carry version 1.0.0 and the cards a protocol version; no changelog (3 of 15). 8+10+6+0+4+3 = 31." }, "scores": { "a": 90, "b": 31 } }, { "by": 55, "category": "transparency", "leads": "deepgram-voice-agent", "name": "Transparency \u0026 trust", "reasons": { "a": "The service is closed with clear terms, and the official SDKs are MIT (15 of 30, read as deepgram-stt and deepgram-tts are). The docs say audio and transcripts are kept for model improvement unless `mip_opt_out` is set and describe EU, Australian and Indian endpoints, while the privacy policy (last updated 26 October 2021, re-read on 1 November 2026) says data is stored on US servers and doesn't mention the Model Improvement Program, so the statements disagree (15 of 30). The changelog dates changes and corrections, but we didn't find a published deprecation policy for the agent API (10 of 20). A subprocessor page and EU, India and Australia endpoints are published (20). 15 + 15 + 10 + 20 = 60. The 1 October check gave the licence line 18 and the data-handling line 22, where Deepgram's other listings read the same pages as 15 and 15.", "b": "Closed service. Terms of service exist at /terms but draw by script, so their content, governing law and the company they name are unchecked; no company, address or country of incorporation appears on any page read, llms.txt says San Francisco, and the MCP repository has no licence (5 of 30). Data handling was read only from guide pages, which say only the owner sees their calls and messages, calls are transcribed and callers told so, and private categories are withheld. The privacy policy and data-deletion page draw by script, so no retention period, recording statement, DPA or AI-training statement was read (8 of 30). No deprecation policy or dated notices (0). No subprocessors, telephony, model or hosting providers or data locations are named on any page read; the demo agent card's icon is served from Cloudinary (0 of 20). 5+8+0+0 = 13." }, "scores": { "a": 78, "b": 23 } }, { "by": 41, "category": "security", "leads": "deepgram-voice-agent", "name": "Security \u0026 auth", "reasons": { "a": "API keys carry an owner, admin or member role, can be set to expire, can be created through the API and can be tagged, and browsers get 30-second JWTs from the token endpoint (30). Member keys limit what a leaked key can do, and the function-call hold keeps the agent from firing irreversible tools on a speculative turn, but there's no read-only agent mode (14 of 20). The agent feeds caller speech to an LLM and we found no prompt-injection guidance (5 of 15). Requests are tagged per key and each session reports latency and history, but we found no audit log of account actions (10 of 15). The compliance page states SOC 2 Type 1 and Type 2, HIPAA and PCI. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy, bug bounty or public advisories found (12 of 20, the same reading as deepgram-stt and deepgram-tts). 30 + 14 + 5 + 10 + 12 = 71.", "b": "No credential exists for callers. llms.txt gives auth 'none', the README says the server is 'public, like the links themselves', and the two agent cards read declare no security scheme. There is nothing to leak or rotate, but fone.me and an owner can tell callers apart only by the name they give ('Maria via ChatGPT' in the README) and by traffic, and no caller identity or verification is documented (10 of 30). Three of four MCP tools are lookups; message_agent and A2A message/send reach any owner's agent. On the owner's side the vendor says the agent asks before agreeing to anything or spending money, the owner approves what it will say before a call, outbound calls run only 8 am to 9 pm local, pause when reported and stop permanently on request, and the owner can take over any chat. No read-only mode and no confirmation on the caller's side (8 of 20). message_agent returns text generated from what the owner taught the agent, and every agent on the platform reads messages from anyone; the only guidance is the how-it-works statement that the agent keeps relationship status, health, money and address private, with no documented prompt-injection or spam handling for the open channel, and the call-screening page says it does not promise to block calls (4 of 15). Owners see every call and chat with a transcript in one inbox; nothing is logged for the calling agent (8 of 15). /.well-known/security.txt answers with the app shell, and no disclosure policy, bug bounty or certification appears on any page read (0 of 20). 10+8+4+8+0 = 30." }, "scores": { "a": 71, "b": 30 } }, { "by": 38, "category": "ergonomics", "leads": "deepgram-voice-agent", "name": "Agent ergonomics", "reasons": { "a": "Scored as an API. Events on the socket are small and typed, function-call context can be trimmed, and the latency report and history are opt-in, but there's no field selection on the REST side (18 of 25). Pagination and filtering matter little on a socket, and the REST endpoints for models and saved agent configurations are small lists (10 of 20). Errors and warnings are documented as typed events (14 of 20). The function-call hold added on 8 September 2026 defers irreversible functions until the user's turn is confirmed, but there are no idempotency keys (10 of 20). Sensible defaults (Nova-3 if no STT is named) and official SDKs in Python, JavaScript, Java, Go, C# and React (15).", "b": "MCP reading. Four tools named in llms.txt, a small set, but their definitions were not read, so short of full marks (18 of 25). find_agents searches by what someone does and the search API takes a query; no limit, paging or output-size controls are documented (3 of 20). No error codes or messages documented for the MCP server, the search API or A2A (0 of 20). No readOnlyHint or destructiveHint seen and no idempotency key; the three lookups are read-only by name and description, while message_agent writes to a real person's inbox and continues the conversation across calls (2 of 20). No credentials, no configuration beyond the URL, and few stated inputs; no SDK in any language (6 of 15). 18+3+0+2+6 = 29." }, "scores": { "a": 67, "b": 29 } } ], "facts": [ { "a": "HTTP API", "b": "Platform", "name": "Kind" }, { "a": "Deepgram", "b": "Fone", "name": "Vendor" }, { "a": "https://agent.deepgram.com/v1/agent", "b": "https://www.fone.me/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio, SSE (legacy)", "b": "Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "None", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT (SDKs)", "b": "Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published", "name": "Licence" }, { "a": "none", "b": "4", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-28", "b": "2026-10-05", "name": "Last release" }, { "a": "2026-08-06", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2021-10-26", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "468 stars, 1.1M npm/wk, 805k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Deepgram Voice Agent API scores 72.2 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Deepgram Voice Agent API or fone.me?" }, { "answer": "Yes. Deepgram Voice Agent API has a hosted endpoint at https://agent.deepgram.com/v1/agent and fone.me at https://www.fone.me/mcp.", "question": "Can an agent call Deepgram Voice Agent API and fone.me without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 15", "Schema \u0026 documentation, 90 against 31", "Agent ergonomics, 67 against 29", "Security \u0026 auth, 71 against 30", "Maintenance \u0026 community, 85 against 23", "Transparency \u0026 trust, 78 against 23" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine", "Free to start without a card" ], "goodFor": "Developers who already run telephony (Twilio, Amazon Connect, Genesys, AudioCodes) and want a cheap managed pipeline with their choice of LLM.", "slug": "deepgram-voice-agent", "watchFor": "No phone numbers or SIP, so you bridge Twilio or another carrier yourself" }, { "aheadOn": [ "Payments \u0026 pricing, 50 against 40" ], "also": [ "No key needed to call it" ], "goodFor": "Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.", "slug": "fone-me", "watchFor": "No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints" } ], "history": { "deepgram-voice-agent": [ { "causes": [ "time" ], "date": "2026-11-01", "delta": 4, "from": 68.2, "fromGrade": "B", "to": 72.2, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 68.1, "fromGrade": "B", "to": 68.2, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 68.4, "fromGrade": "B", "to": 68.1, "toGrade": "B" } ], "fone-me": null }, "job": { "capability": "voice.agent", "name": "Voice agents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-deepgram-voice-agent.json", "title": "Amazon Nova 2 Sonic vs Deepgram Voice Agent API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-deepgram-voice-agent" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.json", "title": "Amazon Nova 2 Sonic vs fone.me", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me" }, { "json": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-deepgram-voice-agent.json", "title": "AssemblyAI Voice Agent API vs Deepgram Voice Agent API", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-deepgram-voice-agent" }, { "json": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me.json", "title": "AssemblyAI Voice Agent API vs fone.me", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-deepgram-voice-agent.json", "title": "Bland AI API + MCP vs Deepgram Voice Agent API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-deepgram-voice-agent" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.json", "title": "Bland AI API + MCP vs fone.me", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-fone-me" }, { "json": "https://www.anchorterminal.com/compare/bolna-vs-deepgram-voice-agent.json", "title": "Bolna API + MCP vs Deepgram Voice Agent API", "url": "https://www.anchorterminal.com/compare/bolna-vs-deepgram-voice-agent" }, { "json": "https://www.anchorterminal.com/compare/bolna-vs-fone-me.json", "title": "Bolna API + MCP vs fone.me", "url": "https://www.anchorterminal.com/compare/bolna-vs-fone-me" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-elevenlabs-agents.json", "title": "Deepgram Voice Agent API vs ElevenLabs Agents API + MCP", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-elevenlabs-agents" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-gemini-live.json", "title": "Deepgram Voice Agent API vs Gemini Live API", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-gemini-live" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-gpt-live.json", "title": "Deepgram Voice Agent API vs GPT-Live", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-gpt-live" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-harmony-ai.json", "title": "Deepgram Voice Agent API vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-harmony-ai" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-hume-evi.json", "title": "Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime.json", "title": "Deepgram Voice Agent API vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-livekit-agents.json", "title": "Deepgram Voice Agent API vs LiveKit Agents", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-livekit-agents" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-openai-realtime.json", "title": "Deepgram Voice Agent API vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-pipecat.json", "title": "Deepgram Voice Agent API vs Pipecat", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-placecall.json", "title": "Deepgram Voice Agent API vs PlaceCall", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-retell-ai.json", "title": "Deepgram Voice Agent API vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-rime-prism.json", "title": "Deepgram Voice Agent API vs Rime Prism", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-synthflow.json", "title": "Deepgram Voice Agent API vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-ultravox.json", "title": "Deepgram Voice Agent API vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vaani-voice.json", "title": "Deepgram Voice Agent API vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vapi.json", "title": "Deepgram Voice Agent API vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily.json", "title": "Deepgram Voice Agent API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vogent.json", "title": "Deepgram Voice Agent API vs Vogent API", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me.json", "title": "ElevenLabs Agents API + MCP vs fone.me", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-gemini-live.json", "title": "fone.me vs Gemini Live API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-gemini-live" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-gpt-live.json", "title": "fone.me vs GPT-Live", "url": "https://www.anchorterminal.com/compare/fone-me-vs-gpt-live" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.json", "title": "fone.me vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.json", "title": "fone.me vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/fone-me-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.json", "title": "fone.me vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-livekit-agents.json", "title": "fone.me vs LiveKit Agents", "url": "https://www.anchorterminal.com/compare/fone-me-vs-livekit-agents" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.json", "title": "fone.me vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-pipecat.json", "title": "fone.me vs Pipecat", "url": "https://www.anchorterminal.com/compare/fone-me-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-placecall.json", "title": "fone.me vs PlaceCall", "url": "https://www.anchorterminal.com/compare/fone-me-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-retell-ai.json", "title": "fone.me vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.json", "title": "fone.me vs Rime Prism", "url": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow.json", "title": "fone.me vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-ultravox.json", "title": "fone.me vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.json", "title": "fone.me vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vapi.json", "title": "fone.me vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vocily.json", "title": "fone.me vs Vocily AI", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vogent.json", "title": "fone.me vs Vogent API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/cuelight-vs-deepgram-voice-agent.json", "title": "CueLight vs Deepgram Voice Agent API", "url": "https://www.anchorterminal.com/compare/cuelight-vs-deepgram-voice-agent" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-pipecat-phonellm.json", "title": "Deepgram Voice Agent API vs Pipecat PhoneLLM", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-pipecat-phonellm" } ], "panel": null, "scores": [ { "by": 60, "deepgram-voice-agent": 75, "edge": "deepgram-voice-agent", "fone-me": 15, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 59, "deepgram-voice-agent": 90, "edge": "deepgram-voice-agent", "fone-me": 31, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 38, "deepgram-voice-agent": 67, "edge": "deepgram-voice-agent", "fone-me": 29, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 41, "deepgram-voice-agent": 71, "edge": "deepgram-voice-agent", "fone-me": 30, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "deepgram-voice-agent": 40, "edge": "fone-me", "fone-me": 50, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 62, "deepgram-voice-agent": 85, "edge": "deepgram-voice-agent", "fone-me": 23, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 55, "deepgram-voice-agent": 78, "edge": "deepgram-voice-agent", "fone-me": 23, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Deepgram Voice Agent API scores 72.2 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing. Both do voice agents.", "tasks": null, "tutorials": [], "verdicts": { "deepgram-voice-agent": "$0.075 a minute all in on Standard, $0.050 with your own LLM and TTS, and $200 of credit with no card. Every status incident since August was partial. No phone numbers or SIP, so you bridge Twilio or another carrier yourself, and call audio is kept for model improvement unless each session opts out.", "fone-me": "Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me", "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.min.md" }, "markdown": "Deepgram Voice Agent API scores 72.2 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing. Both do voice agents.\n\n- Deepgram Voice Agent API: grade BB, 72.2/100, rank #135 of 1486. Markdown https://www.anchorterminal.com/tools/deepgram-voice-agent.md · JSON https://www.anchorterminal.com/api/v1/tools/deepgram-voice-agent.json\n- fone.me: grade F, 28.3/100, rank #1406 of 1486. Markdown https://www.anchorterminal.com/tools/fone-me.md · JSON https://www.anchorterminal.com/api/v1/tools/fone-me.json\n- Best conversational voice-agent APIs: https://www.anchorterminal.com/best/voice-agents/index.md\n- All 518 voice agents comparisons: https://www.anchorterminal.com/compare/voice-agents/index.md\n\n## Which one, for what\n\n### Deepgram Voice Agent API (BB)\n\nGood for: Developers who already run telephony (Twilio, Amazon Connect, Genesys, AudioCodes) and want a cheap managed pipeline with their choice of LLM.\n\nAhead on:\n- Reliability, 75 against 15\n- Schema \u0026 documentation, 90 against 31\n- Agent ergonomics, 67 against 29\n- Security \u0026 auth, 71 against 30\n- Maintenance \u0026 community, 85 against 23\n- Transparency \u0026 trust, 78 against 23\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: No phone numbers or SIP, so you bridge Twilio or another carrier yourself\n\n### fone.me (F)\n\nGood for: Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.\n\nAhead on:\n- Payments \u0026 pricing, 50 against 40\n\nAlso in its favour:\n- No key needed to call it\n\nWatch for: No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Deepgram Voice Agent API +62\n\n- Deepgram Voice Agent API (85): Changelog entries to 27 October 2026 and the Python and JavaScript SDKs released on 28 October (Python 7.16.0, JavaScript 5.17.0), both adding Voice Agent Think Live messages (30). 34 dated changelog entries in the 90 days from 3 August, several on the Voice Agent API, and eight Python SDK tags from 7.9.0 on 14 September to 7.16.0 on 28 October (20). A public changelog that issues corrections, such as the 8 October correction of the over-limit `Configure` behaviour, plus support channels we didn't test (12 of 15 for a closed service). Official SDKs current in Python, JavaScript, Java, Go, .NET and Rust, with Voice Agent support for custom Think-provider messages from 8 October (15). MIT SDKs with current releases (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.\n- fone.me (23): Closed service. The newest dated change to the agent surface found is the MCP repository github.com/spearisa/fone-me-mcp, created 5 October 2026 with server.json version 1.0.0, 31 days ago (20). The comparison page marked 'Checked October 28, 2026' and the profile lastmods in the sitemap are content, not releases. No changelog, release notes or three dated changes in 90 days (0 of 20). The support page and FAQ draw by script and no support email, forum or community channel was found; responsiveness unchecked (3 of 15). server.json names the server me.fone.www/agents, a namespace that needs proof of the domain, but the official MCP registry could not be read, so presence is scored absent (0 of 15). No package, public code or CI (0 of 10). 20+0+3+0+0 = 23.\n\n### Reliability: Deepgram Voice Agent API +60\n\n- Deepgram Voice Agent API (75): Statuspage at status.deepgram.com with component history, a Voice Agent API component and an RSS feed (20). Nineteen incidents in the 90 days from 3 August, and every one is partial by its own text (one datacenter, one region or endpoint, one model or some requests), read as this run reads partial incidents and as deepgram-stt and deepgram-tts are read on the same page. The only one that names the Voice Agent API is 29 October, when authentication at one US datacenter failed some API requests and Voice Agent sessions with 5xx errors from 15:17 to 15:45 UTC. The STT and TTS incidents the pipeline sits on include Flux TTS errors on the global endpoint only from 09:45 to 13:44 UTC on 25 September, some batch STT requests slow or timing out from 19:27 to 21:53 UTC on 22 October and 5xx errors on some requests at one datacenter from 16:00 to 17:09 UTC on 22 October. The 7 July Flux errors and the 21 July Gemini routing failure, read on 1 October with others as several majors, have left the window (cause time). Minor only (20). Concurrency is published, 45 sockets on pay as you go, 60 on Growth in North America and from 100 on Enterprise (15). Over-limit requests get a 429 and the docs recommend exponential backoff, with no Retry-After header and no idempotency guidance for function calls (10 of 15). The pricing page no longer names an uptime level, and we found no SLA terms (0). The Voice Agent API is generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.\n- fone.me (15): Hosted reading, for the MCP server and A2A endpoints and the service behind them. No status page is linked from llms.txt, the home page or any guide page read, and https://www.fone.me/status failed to load (0). No readable incident history, so the floor (5). No request rate limit for the MCP server, the search API or A2A is published; the only limits are on the agent's own outbound calls (8 am to 9 pm in the callee's time zone, 'limited per day' with no number), which are not request limits (0 of 15). No 429, overload or retry guidance and no idempotency key for message_agent or message/send (0 of 15). No SLA (0). Nothing on the MCP server, the agent cards or llms.txt is marked beta or preview, and the MCP repository's server.json is version 1.0.0 (10). 0+5+0+0+0+10 = 15.\n\n### Schema \u0026 documentation: Deepgram Voice Agent API +59\n\n- Deepgram Voice Agent API (90): Public OpenAPI and an AsyncAPI file that describes the agent socket messages (25). llms.txt with a Markdown copy of each page, and a keyless docs MCP server (10). Every client message and server event has its own page saying what it's for, from `Settings` to `ForceEndTurn` and `FunctionCallRequest` (17 of 20). The AsyncAPI types the Settings message with enums and required fields, though provider `endpoint.headers` are free-form (13 of 15). Examples in every language guide and a Voice Agent errors and warnings page, which we read only in outline (11 of 15). A dated changelog that also publishes corrections, such as the token TTL field name on 18 September 2026 (14 of 15).\n- fone.me (31): MCP reading, since the MCP server is what an outside agent calls. No tool arguments or input schemas are published in llms.txt, the guide pages or the GitHub README, and robots.txt disallows /mcp, so no session was opened and tools/list was not read. Per-link A2A agent cards are machine-readable JSON (protocol 0.3.0, JSONRPC, input and output modes, skills with examples) and server.json names the remote, but neither types the MCP tools (8 of 25). llms.txt is a real document for agents covering the MCP server, A2A, the search API and the widget (10). Each tool has a one-line purpose in llms.txt and the README, and the how-it-works page states what the agent will and won't do; nothing says when not to use a tool (6 of 20). No typed inputs, enums, constraints or required fields published (0 of 15). Example prompts in the README, per-skill examples in agent cards and widget code for eight site builders; no error response is documented (4 of 15). server.json and the agent cards carry version 1.0.0 and the cards a protocol version; no changelog (3 of 15). 8+10+6+0+4+3 = 31.\n\n### Transparency \u0026 trust: Deepgram Voice Agent API +55\n\n- Deepgram Voice Agent API (78): The service is closed with clear terms, and the official SDKs are MIT (15 of 30, read as deepgram-stt and deepgram-tts are). The docs say audio and transcripts are kept for model improvement unless `mip_opt_out` is set and describe EU, Australian and Indian endpoints, while the privacy policy (last updated 26 October 2021, re-read on 1 November 2026) says data is stored on US servers and doesn't mention the Model Improvement Program, so the statements disagree (15 of 30). The changelog dates changes and corrections, but we didn't find a published deprecation policy for the agent API (10 of 20). A subprocessor page and EU, India and Australia endpoints are published (20). 15 + 15 + 10 + 20 = 60. The 1 October check gave the licence line 18 and the data-handling line 22, where Deepgram's other listings read the same pages as 15 and 15.\n- fone.me (23): Closed service. Terms of service exist at /terms but draw by script, so their content, governing law and the company they name are unchecked; no company, address or country of incorporation appears on any page read, llms.txt says San Francisco, and the MCP repository has no licence (5 of 30). Data handling was read only from guide pages, which say only the owner sees their calls and messages, calls are transcribed and callers told so, and private categories are withheld. The privacy policy and data-deletion page draw by script, so no retention period, recording statement, DPA or AI-training statement was read (8 of 30). No deprecation policy or dated notices (0). No subprocessors, telephony, model or hosting providers or data locations are named on any page read; the demo agent card's icon is served from Cloudinary (0 of 20). 5+8+0+0 = 13.\n\n### Security \u0026 auth: Deepgram Voice Agent API +41\n\n- Deepgram Voice Agent API (71): API keys carry an owner, admin or member role, can be set to expire, can be created through the API and can be tagged, and browsers get 30-second JWTs from the token endpoint (30). Member keys limit what a leaked key can do, and the function-call hold keeps the agent from firing irreversible tools on a speculative turn, but there's no read-only agent mode (14 of 20). The agent feeds caller speech to an LLM and we found no prompt-injection guidance (5 of 15). Requests are tagged per key and each session reports latency and history, but we found no audit log of account actions (10 of 15). The compliance page states SOC 2 Type 1 and Type 2, HIPAA and PCI. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy, bug bounty or public advisories found (12 of 20, the same reading as deepgram-stt and deepgram-tts). 30 + 14 + 5 + 10 + 12 = 71.\n- fone.me (30): No credential exists for callers. llms.txt gives auth 'none', the README says the server is 'public, like the links themselves', and the two agent cards read declare no security scheme. There is nothing to leak or rotate, but fone.me and an owner can tell callers apart only by the name they give ('Maria via ChatGPT' in the README) and by traffic, and no caller identity or verification is documented (10 of 30). Three of four MCP tools are lookups; message_agent and A2A message/send reach any owner's agent. On the owner's side the vendor says the agent asks before agreeing to anything or spending money, the owner approves what it will say before a call, outbound calls run only 8 am to 9 pm local, pause when reported and stop permanently on request, and the owner can take over any chat. No read-only mode and no confirmation on the caller's side (8 of 20). message_agent returns text generated from what the owner taught the agent, and every agent on the platform reads messages from anyone; the only guidance is the how-it-works statement that the agent keeps relationship status, health, money and address private, with no documented prompt-injection or spam handling for the open channel, and the call-screening page says it does not promise to block calls (4 of 15). Owners see every call and chat with a transcript in one inbox; nothing is logged for the calling agent (8 of 15). /.well-known/security.txt answers with the app shell, and no disclosure policy, bug bounty or certification appears on any page read (0 of 20). 10+8+4+8+0 = 30.\n\n### Agent ergonomics: Deepgram Voice Agent API +38\n\n- Deepgram Voice Agent API (67): Scored as an API. Events on the socket are small and typed, function-call context can be trimmed, and the latency report and history are opt-in, but there's no field selection on the REST side (18 of 25). Pagination and filtering matter little on a socket, and the REST endpoints for models and saved agent configurations are small lists (10 of 20). Errors and warnings are documented as typed events (14 of 20). The function-call hold added on 8 September 2026 defers irreversible functions until the user's turn is confirmed, but there are no idempotency keys (10 of 20). Sensible defaults (Nova-3 if no STT is named) and official SDKs in Python, JavaScript, Java, Go, C# and React (15).\n- fone.me (29): MCP reading. Four tools named in llms.txt, a small set, but their definitions were not read, so short of full marks (18 of 25). find_agents searches by what someone does and the search API takes a query; no limit, paging or output-size controls are documented (3 of 20). No error codes or messages documented for the MCP server, the search API or A2A (0 of 20). No readOnlyHint or destructiveHint seen and no idempotency key; the three lookups are read-only by name and description, while message_agent writes to a real person's inbox and continues the conversation across calls (2 of 20). No credentials, no configuration beyond the URL, and few stated inputs; no SDK in any language (6 of 15). 18+3+0+2+6 = 29.\n\n## Score by category\n\n| Category | Weight | Deepgram Voice Agent API | fone.me | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 15 | Deepgram Voice Agent API +60 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 90 | 31 | Deepgram Voice Agent API +59 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 29 | Deepgram Voice Agent API +38 |\n| Security \u0026 auth | 14% (17.5 this run) | 71 | 30 | Deepgram Voice Agent API +41 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 50 | fone.me +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 23 | Deepgram Voice Agent API +62 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 78 | 23 | Deepgram Voice Agent API +55 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72.2 · BB** | **28.3 · F** | |\n\n## Facts side by side\n\n| Fact | Deepgram Voice Agent API | fone.me |\n| --- | --- | --- |\n| Kind | HTTP API | Platform |\n| Vendor | Deepgram | Fone |\n| Hosted endpoint | `https://agent.deepgram.com/v1/agent` | `https://www.fone.me/mcp` |\n| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | Streamable HTTP |\n| Auth | API key | None |\n| Pricing | Pay per use | Freemium |\n| x402 | no | no |\n| Licence | MIT (SDKs) | Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published |\n| Tools exposed | none | 4 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-28 | 2026-10-05 |\n| Terms last updated | 2026-08-06 | couldn't be read |\n| Privacy policy last updated | 2021-10-26 | couldn't be read |\n| Customer content may train models | yes, with an opt-out | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | none |\n| Agent reviews | 3/5 (2) | none |\n\n## How the scores have moved\n\n### Deepgram Voice Agent API\n\n- +4.0 on 1 November 2026 (B to BB): time\n- +0.1 on 27 October 2026: checklist\n- -0.3 on 8 October 2026: checklist\n\n### fone.me\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Deepgram Voice Agent API.** $0.075 a minute all in on Standard, $0.050 with your own LLM and TTS, and $200 of credit with no card. Every status incident since August was partial. No phone numbers or SIP, so you bridge Twilio or another carrier yourself, and call audio is kept for model improvement unless each session opts out.\n\n**fone.me.** Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named.\n\n## Before you call either\n\n### Deepgram Voice Agent API\n\n1. Set `mip_opt_out` in the Settings message to keep call audio out of training\n2. Use the function-call hold for anything irreversible, since replies can start before the user's turn is confirmed\n3. Back off exponentially on 429, a pay-as-you-go project gets 45 concurrent sockets\n4. Pin the LLM version, an unpinned Gemini route failed for 1.5 hours on 21 July 2026\n5. Mint browser tokens with `ttl_seconds`, not `ttl`, or they expire after 30 seconds\n\n### fone.me\n\n1. Connect to https://www.fone.me/mcp with no credentials; use find_agents or get_agent before message_agent so the message goes to the right person's link.\n2. Say who you are acting for in every message_agent call; the owner reads it in an inbox as a named conversation, and conversations continue across calls.\n3. Treat replies as the owner's agent speaking from what it was taught, not a commitment; the vendor says it asks its owner before agreeing to anything or spending money.\n4. Read a link's agent card at /{link}/.well-known/agent-card.json for its skills before using A2A message/send at /{link}/a2a.\n5. Don't send personal or payment details through message_agent; no retention or privacy terms for agent-to-agent messages could be read.\n\n## Questions\n\n### Which is better for AI agents, Deepgram Voice Agent API or fone.me?\n\nDeepgram Voice Agent API scores 72.2 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing.\n\n### Can an agent call Deepgram Voice Agent API and fone.me without installing anything?\n\nYes. Deepgram Voice Agent API has a hosted endpoint at https://agent.deepgram.com/v1/agent and fone.me at https://www.fone.me/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.json, and with the fewest tokens: https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"deepgram-voice-agent\", \"b\": \"fone-me\"}`. From a terminal: `anchor compare deepgram-voice-agent fone-me`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/deepgram-voice-agent.json and https://www.anchorterminal.com/api/v1/tools/fone-me.json\n\n## Other comparisons with Deepgram Voice Agent API or fone.me\n\n- [Amazon Nova 2 Sonic vs Deepgram Voice Agent API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-deepgram-voice-agent.md)\n- [Amazon Nova 2 Sonic vs fone.me](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.md)\n- [AssemblyAI Voice Agent API vs Deepgram Voice Agent API](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-deepgram-voice-agent.md)\n- [AssemblyAI Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me.md)\n- [Bland AI API + MCP vs Deepgram Voice Agent API](https://www.anchorterminal.com/compare/bland-ai-vs-deepgram-voice-agent.md)\n- [Bland AI API + MCP vs fone.me](https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.md)\n- [Bolna API + MCP vs Deepgram Voice Agent API](https://www.anchorterminal.com/compare/bolna-vs-deepgram-voice-agent.md)\n- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)\n- [Deepgram Voice Agent API vs ElevenLabs Agents API + MCP](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-elevenlabs-agents.md)\n- [Deepgram Voice Agent API vs Gemini Live API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-gemini-live.md)\n- [Deepgram Voice Agent API vs GPT-Live](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-gpt-live.md)\n- [Deepgram Voice Agent API vs Harmony.ai](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-harmony-ai.md)\n- [Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-hume-evi.md)\n- [Deepgram Voice Agent API vs Inworld Realtime API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime.md)\n- [Deepgram Voice Agent API vs LiveKit Agents](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-livekit-agents.md)\n- [Deepgram Voice Agent API vs OpenAI Realtime API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-openai-realtime.md)\n- [Deepgram Voice Agent API vs Pipecat](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-pipecat.md)\n- [Deepgram Voice Agent API vs PlaceCall](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-placecall.md)\n- [Deepgram Voice Agent API vs Retell AI API + MCP](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-retell-ai.md)\n- [Deepgram Voice Agent API vs Rime Prism](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-rime-prism.md)\n- [Deepgram Voice Agent API vs Synthflow API + MCP](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-synthflow.md)\n- [Deepgram Voice Agent API vs Ultravox Realtime API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-ultravox.md)\n- [Deepgram Voice Agent API vs Vaani Developer Platform](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vaani-voice.md)\n- [Deepgram Voice Agent API vs Vapi API + MCP](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vapi.md)\n- [Deepgram Voice Agent API vs Vocily AI](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily.md)\n- [Deepgram Voice Agent API vs Vogent API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vogent.md)\n- [ElevenLabs Agents API + MCP vs fone.me](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me.md)\n- [fone.me vs Gemini Live API](https://www.anchorterminal.com/compare/fone-me-vs-gemini-live.md)\n- [fone.me vs GPT-Live](https://www.anchorterminal.com/compare/fone-me-vs-gpt-live.md)\n- [fone.me vs Harmony.ai](https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.md)\n- [fone.me vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.md)\n- [fone.me vs Inworld Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.md)\n- [fone.me vs LiveKit Agents](https://www.anchorterminal.com/compare/fone-me-vs-livekit-agents.md)\n- [fone.me vs OpenAI Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.md)\n- [fone.me vs Pipecat](https://www.anchorterminal.com/compare/fone-me-vs-pipecat.md)\n- [fone.me vs PlaceCall](https://www.anchorterminal.com/compare/fone-me-vs-placecall.md)\n- [fone.me vs Retell AI API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-retell-ai.md)\n- [fone.me vs Rime Prism](https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.md)\n- [fone.me vs Synthflow API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-synthflow.md)\n- [fone.me vs Ultravox Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-ultravox.md)\n- [fone.me vs Vaani Developer Platform](https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.md)\n- [fone.me vs Vapi API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-vapi.md)\n- [fone.me vs Vocily AI](https://www.anchorterminal.com/compare/fone-me-vs-vocily.md)\n- [fone.me vs Vogent API](https://www.anchorterminal.com/compare/fone-me-vs-vogent.md)\n- [CueLight vs Deepgram Voice Agent API](https://www.anchorterminal.com/compare/cuelight-vs-deepgram-voice-agent.md)\n- [Deepgram Voice Agent API vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-pipecat-phonellm.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Deepgram Voice Agent API vs fone.me", "url": "" } ], "description": "Deepgram Voice Agent scores 72.2 (BB) to fone.me's 28.3 (F) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Deepgram Voice Agent API BB 72.2", "fone.me F 28.3", "scores" ], "h1": "Deepgram Voice Agent API vs fone.me", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/deepgram-voice-agent-vs-fone-me", "published": "2026-10-01", "section": "tools", "title": "Deepgram Voice Agent vs fone.me for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me" }, "tokens": { "markdown": 6300, "slim": 3780 }, "version": 1 }