{ "data": { "a": { "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" } }, "answer": "Rime Prism scores 59.7 (C) 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": "rime-prism", "name": "Rime Prism", "vendor": "Rime Labs", "vendorUrl": "https://www.rime.ai/prism", "kind": "http-api", "category": "voice-agents", "summary": "Prism is Rime's speech-to-speech model for voice agents. It takes caller audio over one WebSocket, decides when the caller has finished, calls the developer's tools and replies in speech with matching text, in English.", "url": "https://www.anchorterminal.com/tools/rime-prism", "markdownUrl": "https://www.anchorterminal.com/tools/rime-prism.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/rime-prism.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/rime-prism.json", "dns": "rime-prism.grade.anchorterminal.com", "license": "Proprietary hosted service under Rime's terms. The Rime SDK used to call it (github.com/rimelabs/rime-sdk) is MIT.", "transports": [ "websocket" ], "remoteUrl": "wss://prism.api.rime.ai/v1/realtime", "packages": [ { "registry": "pypi", "name": "rimelabs-sdk" }, { "registry": "npm", "name": "@rimelabs/sdk" }, { "registry": "go", "name": "github.com/rimelabs/rime-sdk/go" }, { "registry": "cargo", "name": "rimelabs-sdk" } ], "auth": "api-key", "authNotes": "Rime API key from the dashboard, sent as `Authorization: Bearer` on the WebSocket upgrade from a backend. Prism reads no query parameters, so the key can't go in the URL, and it has no ephemeral tokens for browsers or phones. The same key covers Rime's text-to-speech and speech-to-text. No scoped or read-only keys were found in the docs.", "pricing": "freemium", "pricingNotes": "$0.08 a minute of call audio on Flex (pay as you go, card billed monthly) and $0.064 on Scale ($100 a month of credit, 20% off). Every account gets $50 of usage a month across Rime's models, Prism included, with no card. Fine-tuning, custom voices, VPC or on-prem deployment, SLAs and a BAA are Enterprise items with custom pricing (https://www.rime.ai/pricing, checked 2026-10-28).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Prism docs, the API reference or the pricing page, checked 2026-10-28. Paid plans bill a card monthly.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-28" }, "docsUrl": "https://docs.rime.ai/docs/prism/overview", "llmsTxt": "https://docs.rime.ai/llms.txt", "capabilities": [ "voice.speech-to-speech", "voice.agent", "voice.tools" ], "tags": [ "hosted", "freemium", "no-card", "free-tier", "closed-source", "speech-to-speech", "websocket", "streaming", "function-calling", "llms-txt", "python", "typescript", "go", "rust", "status-page", "soc2", "hipaa", "enterprise" ], "lastRelease": "2026-11-01", "graded": true, "anchor": { "graded": true, "score": 59.7, "grade": "C", "agentReady": false, "rank": 685, "ranked": true, "rankOf": 1486, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 75, "payments": 40, "reliability": 55, "schema": 69, "security": 56, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -2, "negativeNotes": [ "-2, misleading claim (29 October 2026). Rime's terms effective that day license Rime to train its models on Free Plan customer data, while its security page still says \"We never use customer text or audio to train our models\" and its privacy policy says customer data isn't used for training unless explicitly requested and agreed upon. https://www.rime.ai/security" ], "verdict": "Prism's WebSocket API documents typed events and 41 error codes with remedies, with a published per-minute price and $50 of free monthly usage. Rime's status page has no Prism component, no per-account concurrency limit is published, the SDKs are alpha, and the 29 October terms allow training on Free Plan data that the security page says never happens.", "bestFor": "English voice agents on Rime's cloud that want one speech-to-speech model with their own tools, and teams moving an OpenAI Realtime beta client who can bridge phone audio themselves.", "strengths": [ "Errors page lists 41 codes, each with scope, the field at fault, a correlation ID and what to do", "$0.08 a minute on Flex, with $50 of free usage a month and no card", "Uses OpenAI Realtime beta event names, with a migration guide for WebSocket, LiveKit, Pipecat and OpenAI SDK clients", "Key only in the upgrade header, and Prism reads no query parameters", "Context truncation is configurable and each reply reports what was left out and its token usage" ], "weaknesses": [ "Rime's status page has no Prism component, so Prism has no incident history of its own", "No concurrency limit per account or key was found, and a full server refuses with 503", "All four SDKs are 0.1.0 alpha releases that may change their API", "The 29 October terms allow training on Free Plan data, against the security page's statement that Rime never trains on customer text or audio", "Privacy and security pages describe text in, audio out, and say nothing specific about caller audio" ], "agentNotes": [ "Connect from a backend with `Authorization: Bearer`, since Prism has no browser tokens and reads no query parameters.", "Send `session.update` before any audio, or every append fails with `session_not_initialized`.", "Keep streaming audio, silence included, while Prism speaks, because it finds turn ends and interruptions from that audio.", "Ask for the continuation after each tool result, since Prism doesn't resume on its own, and never rerun a call with an unknown outcome.", "Pin the exact SDK version, because the SDKs are alpha and a new release can change the API.", "Don't send caller audio or personal data on the Free plan. The terms forbid it and allow training on Free Plan data." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.7 } ], "editorialScores": { "ergonomics": 73, "maintenance": 75, "payments": 40, "reliability": 55, "schema": 69, "security": 56, "transparency": 63 }, "provenanceScore": 81, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "uv add \"rimelabs-sdk==0.1.0a25\"" }, "letme": { "capability": "https://letme.dev/voice.speech-to-speech", "tool": "https://letme.dev/rime-prism" }, "sameCompany": [ "rime-tts" ], "area": "voice", "unitPrices": [ { "item": "Prism, Flex", "unit": "call-minute", "usd": 0.08, "note": "Metered by the minute of call audio, pay as you go. Pricing page, checked 28 October 2026" }, { "item": "Prism, Scale", "unit": "call-minute", "usd": 0.064, "note": "20% off Flex for $100 a month of credit, which rolls over up to $200. Pricing page, checked 28 October 2026" } ], "provenance": { "legalEntity": "Rime Labs, Inc.", "domain": "rime.ai", "domainRegistered": "2020-03-12", "endpointOnVendorDomain": true, "terms": "https://www.rime.ai/terms", "privacy": "https://www.rime.ai/privacy", "statusPage": "https://www.rimestat.us", "changelog": "https://docs.rime.ai/docs/changelog", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The terms name Rime Labs, Inc., the same entity as the rime-tts listing, and are effective as of 29 October 2026. The domain registration date stands per that listing's check of 30 September 2026 and wasn't re-read.", "status.rime.ai redirects to www.rimestat.us, an incident.io page with Text-to-speech API and Platform API components and data since 30 August 2026. It had no Prism component on 28 October or 4 November 2026.", "www.rime.ai/.well-known/security.txt answered 404 on 28 October 2026. The security page links a vulnerability disclosure policy.", "The Prism endpoint is on prism.api.rime.ai, under the vendor's own domain." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/rime-prism.json", "live": { "slug": "rime-prism", "probe": { "target": "wss://prism.api.rime.ai/v1/realtime", "method": "get", "lastAt": "2026-11-07T18:20:51.218637525Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "unsupported protocol scheme \"wss\"", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 239, "samples30d": 2176, "days": [ { "date": "2026-10-29", "probes": 70, "ok": 0 }, { "date": "2026-10-30", "probes": 249, "ok": 0 }, { "date": "2026-10-31", "probes": 251, "ok": 0 }, { "date": "2026-11-01", "probes": 249, "ok": 0 }, { "date": "2026-11-02", "probes": 250, "ok": 0 }, { "date": "2026-11-03", "probes": 248, "ok": 0 }, { "date": "2026-11-04", "probes": 246, "ok": 0 }, { "date": "2026-11-05", "probes": 185, "ok": 0 }, { "date": "2026-11-06", "probes": 241, "ok": 0 }, { "date": "2026-11-07", "probes": 187, "ok": 0 } ], "outages": [ { "start": "2026-10-29T17:19:57.075096127Z", "end": "0001-01-01T00:00:00Z", "note": "unsupported protocol scheme \"wss\"" } ] }, "vendorStatus": { "page": "https://www.rimestat.us", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:58.863370821Z" }, "versions": [ { "registry": "npm", "name": "@rimelabs/sdk", "version": "0.1.0-alpha.28", "seenAt": "2026-11-07T00:02:00.172452674Z" }, { "registry": "pypi", "name": "rimelabs-sdk", "version": "0.1.0a29", "released": "2026-11-03", "seenAt": "2026-11-07T00:01:59.380878167Z" } ], "npmWeekly": 659, "pypiWeekly": 2301, "securityTxt": { "url": "https://rime.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:23.635370448Z" }, "llmsTxt": { "url": "https://docs.rime.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:49.535176855Z" }, "domain": { "domain": "rime.ai", "registered": "2020-03-12", "source": "https://rdap.identitydigital.services/rdap/domain/rime.ai", "checkedAt": "2026-11-01T14:12:28.680529767Z" }, "pages": [ { "url": "https://docs.rime.ai/docs/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:44.335887738Z", "changedAt": "2026-11-06T13:30:04.475299106Z", "fingerprint": "75c552a0d3da" }, { "url": "https://www.rime.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:33:51.682568277Z", "changedAt": "2026-10-30T05:59:51.46023492Z", "fingerprint": "4abe77f20c42" }, { "url": "https://www.rime.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:33:54.085259365Z", "changedAt": "2026-10-30T05:59:53.554943994Z", "fingerprint": "def0a3cd7cf8" }, { "url": "https://www.rime.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:33:55.776678465Z", "changedAt": "2026-10-30T05:59:55.592355485Z", "fingerprint": "702110fac9ca" } ], "updatedAt": "2026-11-07T18:21:58.863370821Z" } }, "edges": [ { "by": 52, "category": "maintenance", "leads": "rime-prism", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed API on the tool lines. Prism launched on 28 October 2026, and SDK releases that change the Python `realtime` client (Prism's) followed to 1 November (30). Since 6 August the changelog has one Prism entry (28 October), and the SDK repository tagged six releases that change Prism's realtime code, on 26 October (two), 27, 30 October (two) and 1 November, each across the Python, Node.js, Go and Rust packages. Counting SDK tags at half, that is four, so three or more (20, was 10). A public changelog with RSS, docs and community support on Free and email on paid plans, and a support address. Responsiveness can't yet be judged a week after launch (8 of 15). Current official SDKs in four languages, the newest on 3 November, all 0.1.0 alpha with a warning that a release can change the API. Partly met, so the earlier 12 is kept (12 of 15). The SDK repository is MIT, and its checks workflow on main runs pytest, npm test, ruff and mypy with locked dependencies, results unread (github.com answers 403). Partly met, so the earlier 5 is kept (5 of 10). Rime retired Arcana from its cloud API 17 days after announcing it (29 July to 15 August 2026). 30+20+8+12+5 = 75." }, "scores": { "a": 23, "b": 75 } }, { "by": 49, "category": "transparency", "leads": "rime-prism", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service with clear terms from Rime Labs, Inc., and the SDK is MIT (15 of 30). The terms changed on 29 October 2026. Section 6.3(b) now grants Rime a perpetual licence to train and improve its models on Free Plan customer data (excluding voice recordings, audio with a natural person's voice and third parties' personal data), while the privacy policy (effective 22 August 2025) says \"We do not use customer data to train AI models unless explicitly requested and agreed upon\" and the security page says \"We never use customer text or audio to train our models\". The privacy and security pages still describe text in and audio out, and none covers Prism's caller audio, while the new terms define Call Content and say not to send Caller audio on a Free Plan. The DPA at rime.ai/dpa couldn't be reached from our network on 28 October. The contradiction between the terms and the security page is charged once, as the misleading-claim deduction, so the line holds (15 of 30). The new terms promise at least 30 days' notice before retiring a Model Version used on a paid plan. Arcana's cloud retirement came with 17 days' notice before that policy (15 of 20, was 10). A sub-processor list with locations, all in the United States, and the Prism endpoint stated as US East (us-east-2), per the 28 October check (18 of 20). 15+15+15+18 = 63." }, "scores": { "a": 23, "b": 72 } }, { "by": 44, "category": "ergonomics", "leads": "rime-prism", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "Scored as a model API. A 65,536-token context, with `truncation` set to leave out the oldest turns by default, a configurable `retention_ratio`, a `prism_truncation` report on each reply, `prism.conversation.get` to read the stored history and `conversation.item.delete` to trim it (20 of 25). Replies are capped at 120 seconds or 512 tokens and can't be set lower. `max_response_output_tokens`, `temperature` and text-only replies are refused. Up to 16 labels per reply for routing. No lists to page. Partly met, so the earlier 8 is kept (8 of 20). Errors carry `code`, `scope`, `owner`, `param` and a `correlation_id`, and the docs tell clients to branch on code and scope, never on message (20). Client events are matched by `event_id`, a repeated identical tool result is acknowledged, and Prism records late results. Prism doesn't deduplicate requests, a dropped connection doesn't resume, and the client replays history into a new session. Partly met, so the earlier 12 is kept (12 of 20). Short instructions are enough to start, the voice defaults to `astra` and interruption is on. Official SDKs in Python, Node.js, Go and Rust, all alpha, plus LiveKit and Pipecat quickstarts. Partly met while the SDKs are alpha, so the earlier 13 is kept (13 of 15). 20+8+20+12+13 = 73." }, "scores": { "a": 29, "b": 73 } }, { "by": 40, "category": "reliability", "leads": "rime-prism", "name": "Reliability", "reasons": { "a": "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.", "b": "status.rime.ai redirects to an incident.io page at rimestat.us with Text-to-speech API and Platform API components, and still no Prism component on 4 November 2026. A vendor status page with no component for the product takes 15 in this run (15, was 10). Its feed lists two incidents, Text-to-speech partial degradations on 3 and 5 September, and nothing since Prism launched on 28 October, a short record of seven days (15, was 5). The errors page publishes per-session numbers (55 seconds a turn, 60 seconds of queued speech, 120 seconds or 512 tokens a reply, 5 minutes idle, 1 MiB a message), but no concurrency limit per account or key, and a full server answers 503. Partly met, so the earlier 8 is kept (8). Overload is documented as `capacity_exceeded`, `unavailable`, a 503 refusal (\"Retry after a backoff\") and close code 1001, the page says which reply failures can succeed when sent again, and the tools guide says never to rerun a call with an unknown outcome. Safe-retry guidance without idempotency keys gives 12 in this run (12, was 13, not a checklist value). SLAs are an Enterprise item and none is published (0). The changelog calls Prism available, but all four SDKs are 0.1.0 alpha releases, the Pipecat path uses a pinned preview, and the pricing page says half duplex at launch. Partly met, so the earlier 5 is kept (5). 15+15+8+12+0+5 = 55." }, "scores": { "a": 15, "b": 55 } }, { "by": 38, "category": "schema", "leads": "rime-prism", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "No OpenAPI or AsyncAPI file for the WebSocket API was found in llms.txt or the reference (0 of 25). llms.txt and a Markdown twin of every page (10). The overview says what Prism handles, what it doesn't (text-only replies, sampling settings, a choice of language model, ending the caller's turn) and when a pipeline fits better, and a chart says when to use the SDK, LiveKit, Pipecat or the raw WebSocket (18 of 20). The WebSocket reference types every client and server event field with defaults and allowed values, refuses unknown fields with `invalid_client_event` naming the field, and takes tool parameters as JSON Schema. The schemas exist only as tables, not a file (13 of 15). Python and Node.js examples on each guide, and an errors page that lists 41 codes with cause, scope and what to do, plus HTTP refusals and close codes (15). A dated changelog with an RSS feed, a `version` field in `session.created` (such as `20261023a`) and pinned SDK versions. The path carries `/v1`, with no version policy for the event set found. Partly met, so the earlier 13 is kept (13 of 15). Docs and changelog re-read on 4 November. 0+10+18+13+15+13 = 69." }, "scores": { "a": 31, "b": 69 } }, { "by": 26, "category": "security", "leads": "rime-prism", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Graded as a hosted API. One Rime API key per request, sent as a Bearer header on the upgrade. Prism reads no query parameters and the docs say not to put the key in the URL. No scopes, no read-only keys and no ephemeral tokens for client devices were found, the same key also covers text-to-speech and speech-to-text, and rotation isn't described beyond creating tokens in the dashboard (20 of 30). `tool_choice` is `auto` only, so a backend can't force a call, but it can remove a tool mid-call with `session.update`. The prompting guide says Prism can call a tool before the caller confirms and to keep confirmation rules in tool code. The launch pages say every reply is text before speech so guardrails can check it, but the docs describe no step that holds a reply for checks (10 of 20). Prism takes untrusted caller audio and tool results. The docs say to confirm outcomes from the agent's own records, not the reply text, with no explicit prompt-injection guidance (6 of 15). Request, session and correlation IDs for support and token usage on each `response.done`. No per-call log or audit trail in the dashboard was found (6 of 15). SOC 2 Type II since May 2025, HIPAA compliance since February 2024 with an audit in March 2026, and a vulnerability disclosure policy linked from the security page. The security page still names a formal vulnerability disclosure programme on 4 November. security.txt answered 404 and no bug bounty was found (14 of 20). 20+10+6+6+14 = 56." }, "scores": { "a": 30, "b": 56 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Fone", "b": "Rime Labs", "name": "Vendor" }, { "a": "https://www.fone.me/mcp", "b": "wss://prism.api.rime.ai/v1/realtime", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "websocket", "name": "Transports" }, { "a": "None", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "Proprietary hosted service under Rime's terms. The Rime SDK used to call it (github.com/rimelabs/rime-sdk) is MIT.", "name": "Licence" }, { "a": "4", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-05", "b": "2026-11-01", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Rime Prism scores 59.7 (C) 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, fone.me or Rime Prism?" }, { "answer": "Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Rime Prism at wss://prism.api.rime.ai/v1/realtime.", "question": "Can an agent call fone.me and Rime Prism without installing anything?" } ], "goodFor": [ { "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" }, { "aheadOn": [ "Reliability, 55 against 15", "Schema \u0026 documentation, 69 against 31", "Agent ergonomics, 73 against 29", "Security \u0026 auth, 56 against 30", "Maintenance \u0026 community, 75 against 23", "Transparency \u0026 trust, 72 against 23" ], "also": [ "Free to start without a card" ], "goodFor": "English voice agents on Rime's cloud that want one speech-to-speech model with their own tools, and teams moving an OpenAI Realtime beta client who can bridge phone audio themselves.", "slug": "rime-prism", "watchFor": "Rime's status page has no Prism component, so Prism has no incident history of its own" } ], "history": { "fone-me": null, "rime-prism": [ { "causes": [ "terms", "product", "correction", "event" ], "date": "2026-11-04", "delta": 1.8, "from": 57.9, "fromGrade": "C", "to": 59.7, "toGrade": "C" } ] }, "job": { "capability": "voice.agent", "name": "Voice agents" }, "others": [ { "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/amazon-nova-sonic-vs-rime-prism.json", "title": "Amazon Nova 2 Sonic vs Rime Prism", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-rime-prism" }, { "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/assemblyai-voice-agent-vs-rime-prism.json", "title": "AssemblyAI Voice Agent API vs Rime Prism", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-rime-prism" }, { "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/bland-ai-vs-rime-prism.json", "title": "Bland AI API + MCP vs Rime Prism", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-rime-prism" }, { "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/bolna-vs-rime-prism.json", "title": "Bolna API + MCP vs Rime Prism", "url": "https://www.anchorterminal.com/compare/bolna-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.json", "title": "Deepgram Voice Agent API vs fone.me", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me" }, { "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/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/elevenlabs-agents-vs-rime-prism.json", "title": "ElevenLabs Agents API + MCP vs Rime Prism", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-rime-prism" }, { "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-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/gemini-live-vs-rime-prism.json", "title": "Gemini Live API vs Rime Prism", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-rime-prism.json", "title": "Harmony.ai vs Rime Prism", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-rime-prism.json", "title": "Hume EVI (Empathic Voice Interface) vs Rime Prism", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism.json", "title": "Inworld Realtime API vs Rime Prism", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/livekit-agents-vs-rime-prism.json", "title": "LiveKit Agents vs Rime Prism", "url": "https://www.anchorterminal.com/compare/livekit-agents-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-rime-prism.json", "title": "OpenAI Realtime API vs Rime Prism", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-rime-prism.json", "title": "Pipecat vs Rime Prism", "url": "https://www.anchorterminal.com/compare/pipecat-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/placecall-vs-rime-prism.json", "title": "PlaceCall vs Rime Prism", "url": "https://www.anchorterminal.com/compare/placecall-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/retell-ai-vs-rime-prism.json", "title": "Retell AI API + MCP vs Rime Prism", "url": "https://www.anchorterminal.com/compare/retell-ai-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/rime-prism-vs-synthflow.json", "title": "Rime Prism vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/rime-prism-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/rime-prism-vs-vaani-voice.json", "title": "Rime Prism vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/rime-prism-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/rime-prism-vs-vocily.json", "title": "Rime Prism vs Vocily AI", "url": "https://www.anchorterminal.com/compare/rime-prism-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/rime-prism-vs-vogent.json", "title": "Rime Prism vs Vogent API", "url": "https://www.anchorterminal.com/compare/rime-prism-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-rime-prism.json", "title": "GPT-Live vs Rime Prism", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/rime-prism-vs-ultravox.json", "title": "Rime Prism vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/rime-prism-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/rime-prism-vs-vapi.json", "title": "Rime Prism vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/rime-prism-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-rime-prism.json", "title": "Pipecat PhoneLLM vs Rime Prism", "url": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-rime-prism" } ], "panel": null, "scores": [ { "by": 40, "edge": "rime-prism", "fone-me": 15, "key": "reliability", "name": "Reliability", "rime-prism": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 38, "edge": "rime-prism", "fone-me": 31, "key": "schema", "name": "Schema \u0026 documentation", "rime-prism": 69, "weight": 13 }, { "by": 44, "edge": "rime-prism", "fone-me": 29, "key": "ergonomics", "name": "Agent ergonomics", "rime-prism": 73, "weight": 13 }, { "by": 26, "edge": "rime-prism", "fone-me": 30, "key": "security", "name": "Security \u0026 auth", "rime-prism": 56, "weight": 14 }, { "by": 10, "edge": "fone-me", "fone-me": 50, "key": "payments", "name": "Payments \u0026 pricing", "rime-prism": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 52, "edge": "rime-prism", "fone-me": 23, "key": "maintenance", "name": "Maintenance \u0026 community", "rime-prism": 75, "weight": 7 }, { "by": 49, "edge": "rime-prism", "fone-me": 23, "key": "transparency", "name": "Transparency \u0026 trust", "rime-prism": 72, "weight": 7 } ], "summary": "Rime Prism scores 59.7 (C) 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": { "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.", "rime-prism": "Prism's WebSocket API documents typed events and 41 error codes with remedies, with a published per-minute price and $50 of free monthly usage. Rime's status page has no Prism component, no per-account concurrency limit is published, the SDKs are alpha, and the 29 October terms allow training on Free Plan data that the security page says never happens." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism", "json": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.min.md" }, "markdown": "Rime Prism scores 59.7 (C) 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- 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- Rime Prism: grade C, 59.7/100, rank #685 of 1486. Markdown https://www.anchorterminal.com/tools/rime-prism.md · JSON https://www.anchorterminal.com/api/v1/tools/rime-prism.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### 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### Rime Prism (C)\n\nGood for: English voice agents on Rime's cloud that want one speech-to-speech model with their own tools, and teams moving an OpenAI Realtime beta client who can bridge phone audio themselves.\n\nAhead on:\n- Reliability, 55 against 15\n- Schema \u0026 documentation, 69 against 31\n- Agent ergonomics, 73 against 29\n- Security \u0026 auth, 56 against 30\n- Maintenance \u0026 community, 75 against 23\n- Transparency \u0026 trust, 72 against 23\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Rime's status page has no Prism component, so Prism has no incident history of its own\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Rime Prism +52\n\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- Rime Prism (75): Read as a closed API on the tool lines. Prism launched on 28 October 2026, and SDK releases that change the Python `realtime` client (Prism's) followed to 1 November (30). Since 6 August the changelog has one Prism entry (28 October), and the SDK repository tagged six releases that change Prism's realtime code, on 26 October (two), 27, 30 October (two) and 1 November, each across the Python, Node.js, Go and Rust packages. Counting SDK tags at half, that is four, so three or more (20, was 10). A public changelog with RSS, docs and community support on Free and email on paid plans, and a support address. Responsiveness can't yet be judged a week after launch (8 of 15). Current official SDKs in four languages, the newest on 3 November, all 0.1.0 alpha with a warning that a release can change the API. Partly met, so the earlier 12 is kept (12 of 15). The SDK repository is MIT, and its checks workflow on main runs pytest, npm test, ruff and mypy with locked dependencies, results unread (github.com answers 403). Partly met, so the earlier 5 is kept (5 of 10). Rime retired Arcana from its cloud API 17 days after announcing it (29 July to 15 August 2026). 30+20+8+12+5 = 75.\n\n### Transparency \u0026 trust: Rime Prism +49\n\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- Rime Prism (72): Closed service with clear terms from Rime Labs, Inc., and the SDK is MIT (15 of 30). The terms changed on 29 October 2026. Section 6.3(b) now grants Rime a perpetual licence to train and improve its models on Free Plan customer data (excluding voice recordings, audio with a natural person's voice and third parties' personal data), while the privacy policy (effective 22 August 2025) says \"We do not use customer data to train AI models unless explicitly requested and agreed upon\" and the security page says \"We never use customer text or audio to train our models\". The privacy and security pages still describe text in and audio out, and none covers Prism's caller audio, while the new terms define Call Content and say not to send Caller audio on a Free Plan. The DPA at rime.ai/dpa couldn't be reached from our network on 28 October. The contradiction between the terms and the security page is charged once, as the misleading-claim deduction, so the line holds (15 of 30). The new terms promise at least 30 days' notice before retiring a Model Version used on a paid plan. Arcana's cloud retirement came with 17 days' notice before that policy (15 of 20, was 10). A sub-processor list with locations, all in the United States, and the Prism endpoint stated as US East (us-east-2), per the 28 October check (18 of 20). 15+15+15+18 = 63.\n\n### Agent ergonomics: Rime Prism +44\n\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- Rime Prism (73): Scored as a model API. A 65,536-token context, with `truncation` set to leave out the oldest turns by default, a configurable `retention_ratio`, a `prism_truncation` report on each reply, `prism.conversation.get` to read the stored history and `conversation.item.delete` to trim it (20 of 25). Replies are capped at 120 seconds or 512 tokens and can't be set lower. `max_response_output_tokens`, `temperature` and text-only replies are refused. Up to 16 labels per reply for routing. No lists to page. Partly met, so the earlier 8 is kept (8 of 20). Errors carry `code`, `scope`, `owner`, `param` and a `correlation_id`, and the docs tell clients to branch on code and scope, never on message (20). Client events are matched by `event_id`, a repeated identical tool result is acknowledged, and Prism records late results. Prism doesn't deduplicate requests, a dropped connection doesn't resume, and the client replays history into a new session. Partly met, so the earlier 12 is kept (12 of 20). Short instructions are enough to start, the voice defaults to `astra` and interruption is on. Official SDKs in Python, Node.js, Go and Rust, all alpha, plus LiveKit and Pipecat quickstarts. Partly met while the SDKs are alpha, so the earlier 13 is kept (13 of 15). 20+8+20+12+13 = 73.\n\n### Reliability: Rime Prism +40\n\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- Rime Prism (55): status.rime.ai redirects to an incident.io page at rimestat.us with Text-to-speech API and Platform API components, and still no Prism component on 4 November 2026. A vendor status page with no component for the product takes 15 in this run (15, was 10). Its feed lists two incidents, Text-to-speech partial degradations on 3 and 5 September, and nothing since Prism launched on 28 October, a short record of seven days (15, was 5). The errors page publishes per-session numbers (55 seconds a turn, 60 seconds of queued speech, 120 seconds or 512 tokens a reply, 5 minutes idle, 1 MiB a message), but no concurrency limit per account or key, and a full server answers 503. Partly met, so the earlier 8 is kept (8). Overload is documented as `capacity_exceeded`, `unavailable`, a 503 refusal (\"Retry after a backoff\") and close code 1001, the page says which reply failures can succeed when sent again, and the tools guide says never to rerun a call with an unknown outcome. Safe-retry guidance without idempotency keys gives 12 in this run (12, was 13, not a checklist value). SLAs are an Enterprise item and none is published (0). The changelog calls Prism available, but all four SDKs are 0.1.0 alpha releases, the Pipecat path uses a pinned preview, and the pricing page says half duplex at launch. Partly met, so the earlier 5 is kept (5). 15+15+8+12+0+5 = 55.\n\n### Schema \u0026 documentation: Rime Prism +38\n\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- Rime Prism (69): No OpenAPI or AsyncAPI file for the WebSocket API was found in llms.txt or the reference (0 of 25). llms.txt and a Markdown twin of every page (10). The overview says what Prism handles, what it doesn't (text-only replies, sampling settings, a choice of language model, ending the caller's turn) and when a pipeline fits better, and a chart says when to use the SDK, LiveKit, Pipecat or the raw WebSocket (18 of 20). The WebSocket reference types every client and server event field with defaults and allowed values, refuses unknown fields with `invalid_client_event` naming the field, and takes tool parameters as JSON Schema. The schemas exist only as tables, not a file (13 of 15). Python and Node.js examples on each guide, and an errors page that lists 41 codes with cause, scope and what to do, plus HTTP refusals and close codes (15). A dated changelog with an RSS feed, a `version` field in `session.created` (such as `20261023a`) and pinned SDK versions. The path carries `/v1`, with no version policy for the event set found. Partly met, so the earlier 13 is kept (13 of 15). Docs and changelog re-read on 4 November. 0+10+18+13+15+13 = 69.\n\n### Security \u0026 auth: Rime Prism +26\n\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- Rime Prism (56): Graded as a hosted API. One Rime API key per request, sent as a Bearer header on the upgrade. Prism reads no query parameters and the docs say not to put the key in the URL. No scopes, no read-only keys and no ephemeral tokens for client devices were found, the same key also covers text-to-speech and speech-to-text, and rotation isn't described beyond creating tokens in the dashboard (20 of 30). `tool_choice` is `auto` only, so a backend can't force a call, but it can remove a tool mid-call with `session.update`. The prompting guide says Prism can call a tool before the caller confirms and to keep confirmation rules in tool code. The launch pages say every reply is text before speech so guardrails can check it, but the docs describe no step that holds a reply for checks (10 of 20). Prism takes untrusted caller audio and tool results. The docs say to confirm outcomes from the agent's own records, not the reply text, with no explicit prompt-injection guidance (6 of 15). Request, session and correlation IDs for support and token usage on each `response.done`. No per-call log or audit trail in the dashboard was found (6 of 15). SOC 2 Type II since May 2025, HIPAA compliance since February 2024 with an audit in March 2026, and a vulnerability disclosure policy linked from the security page. The security page still names a formal vulnerability disclosure programme on 4 November. security.txt answered 404 and no bug bounty was found (14 of 20). 20+10+6+6+14 = 56.\n\n## Score by category\n\n| Category | Weight | fone.me | Rime Prism | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 55 | Rime Prism +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 31 | 69 | Rime Prism +38 |\n| Agent ergonomics | 13% (16.2 this run) | 29 | 73 | Rime Prism +44 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 56 | Rime Prism +26 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 40 | fone.me +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 23 | 75 | Rime Prism +52 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 23 | 72 | Rime Prism +49 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **28.3 · F** | **59.7 · C** | |\n\n## Facts side by side\n\n| Fact | fone.me | Rime Prism |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Fone | Rime Labs |\n| Hosted endpoint | `https://www.fone.me/mcp` | `wss://prism.api.rime.ai/v1/realtime` |\n| Transports | Streamable HTTP | websocket |\n| Auth | None | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | 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 | Proprietary hosted service under Rime's terms. The Rime SDK used to call it (github.com/rimelabs/rime-sdk) is MIT. |\n| Tools exposed | 4 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-05 | 2026-11-01 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | no date given |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | yes |\n\n## How the scores have moved\n\n### fone.me\n\nNo score change since it was listed.\n\n### Rime Prism\n\n- +1.8 on 4 November 2026: terms, product, correction, negative event\n\n## Verdicts\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**Rime Prism.** Prism's WebSocket API documents typed events and 41 error codes with remedies, with a published per-minute price and $50 of free monthly usage. Rime's status page has no Prism component, no per-account concurrency limit is published, the SDKs are alpha, and the 29 October terms allow training on Free Plan data that the security page says never happens.\n\n## Before you call either\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### Rime Prism\n\n1. Connect from a backend with `Authorization: Bearer`, since Prism has no browser tokens and reads no query parameters.\n2. Send `session.update` before any audio, or every append fails with `session_not_initialized`.\n3. Keep streaming audio, silence included, while Prism speaks, because it finds turn ends and interruptions from that audio.\n4. Ask for the continuation after each tool result, since Prism doesn't resume on its own, and never rerun a call with an unknown outcome.\n5. Pin the exact SDK version, because the SDKs are alpha and a new release can change the API.\n6. Don't send caller audio or personal data on the Free plan. The terms forbid it and allow training on Free Plan data.\n\n## Questions\n\n### Which is better for AI agents, fone.me or Rime Prism?\n\nRime Prism scores 59.7 (C) 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 fone.me and Rime Prism without installing anything?\n\nYes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Rime Prism at wss://prism.api.rime.ai/v1/realtime.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fone-me\", \"b\": \"rime-prism\"}`. From a terminal: `anchor compare fone-me rime-prism`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fone-me.json and https://www.anchorterminal.com/api/v1/tools/rime-prism.json\n\n## Other comparisons with fone.me or Rime Prism\n\n- [Amazon Nova 2 Sonic vs fone.me](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.md)\n- [Amazon Nova 2 Sonic vs Rime Prism](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-rime-prism.md)\n- [AssemblyAI Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me.md)\n- [AssemblyAI Voice Agent API vs Rime Prism](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-rime-prism.md)\n- [Bland AI API + MCP vs fone.me](https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.md)\n- [Bland AI API + MCP vs Rime Prism](https://www.anchorterminal.com/compare/bland-ai-vs-rime-prism.md)\n- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)\n- [Bolna API + MCP vs Rime Prism](https://www.anchorterminal.com/compare/bolna-vs-rime-prism.md)\n- [Deepgram Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.md)\n- [Deepgram Voice Agent API vs Rime Prism](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-rime-prism.md)\n- [ElevenLabs Agents API + MCP vs fone.me](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me.md)\n- [ElevenLabs Agents API + MCP vs Rime Prism](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-rime-prism.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 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- [Gemini Live API vs Rime Prism](https://www.anchorterminal.com/compare/gemini-live-vs-rime-prism.md)\n- [Harmony.ai vs Rime Prism](https://www.anchorterminal.com/compare/harmony-ai-vs-rime-prism.md)\n- [Hume EVI (Empathic Voice Interface) vs Rime Prism](https://www.anchorterminal.com/compare/hume-evi-vs-rime-prism.md)\n- [Inworld Realtime API vs Rime Prism](https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism.md)\n- [LiveKit Agents vs Rime Prism](https://www.anchorterminal.com/compare/livekit-agents-vs-rime-prism.md)\n- [OpenAI Realtime API vs Rime Prism](https://www.anchorterminal.com/compare/openai-realtime-vs-rime-prism.md)\n- [Pipecat vs Rime Prism](https://www.anchorterminal.com/compare/pipecat-vs-rime-prism.md)\n- [PlaceCall vs Rime Prism](https://www.anchorterminal.com/compare/placecall-vs-rime-prism.md)\n- [Retell AI API + MCP vs Rime Prism](https://www.anchorterminal.com/compare/retell-ai-vs-rime-prism.md)\n- [Rime Prism vs Synthflow API + MCP](https://www.anchorterminal.com/compare/rime-prism-vs-synthflow.md)\n- [Rime Prism vs Vaani Developer Platform](https://www.anchorterminal.com/compare/rime-prism-vs-vaani-voice.md)\n- [Rime Prism vs Vocily AI](https://www.anchorterminal.com/compare/rime-prism-vs-vocily.md)\n- [Rime Prism vs Vogent API](https://www.anchorterminal.com/compare/rime-prism-vs-vogent.md)\n- [GPT-Live vs Rime Prism](https://www.anchorterminal.com/compare/gpt-live-vs-rime-prism.md)\n- [Rime Prism vs Ultravox Realtime API](https://www.anchorterminal.com/compare/rime-prism-vs-ultravox.md)\n- [Rime Prism vs Vapi API + MCP](https://www.anchorterminal.com/compare/rime-prism-vs-vapi.md)\n- [Pipecat PhoneLLM vs Rime Prism](https://www.anchorterminal.com/compare/pipecat-phonellm-vs-rime-prism.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": "fone.me vs Rime Prism", "url": "" } ], "description": "Rime Prism scores 59.7 (C) to fone.me's 28.3 (F) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "fone.me F 28.3", "Rime Prism C 59.7", "scores" ], "h1": "fone.me vs Rime Prism", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/fone-me-vs-rime-prism", "published": "2026-10-01", "section": "tools", "title": "fone.me vs Rime Prism for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism" }, "tokens": { "markdown": 6700, "slim": 4330 }, "version": 1 }