# fone.me vs Rime Prism (slim)

> 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.

- Full: https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.md (~6,700 tokens) · this version ~4,330 tokens · JSON https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.json · canonical https://www.anchorterminal.com/compare/fone-me-vs-rime-prism
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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 & pricing. Both do voice agents.

- fone.me: F 28.3, rank #1406 of 1486 · https://www.anchorterminal.com/tools/fone-me.min.md
- Rime Prism: C 59.7, rank #685 of 1486 · https://www.anchorterminal.com/tools/rime-prism.min.md
- fone.me, good 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. Ahead on Payments & pricing, 50 against 40. Also No key needed to call it.
- Rime Prism, good 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. Ahead on Reliability, 55 against 15; Schema & documentation, 69 against 31; Agent ergonomics, 73 against 29; Security & auth, 56 against 30; Maintenance & community, 75 against 23; Transparency & trust, 72 against 23. Also Free to start without a card.

| Category | fone.me | Rime Prism |
| --- | --- | --- |
| Reliability (16%) | 15 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 31 | 69 |
| Agent ergonomics (13%) | 29 | 73 |
| Security & auth (14%) | 30 | 56 |
| Payments & pricing (10%) | 50 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 23 | 75 |
| Transparency & trust (7%) | 23 | 72 |

| Fact (where they differ) | fone.me | Rime Prism |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Fone | Rime Labs |
| Hosted endpoint | `https://www.fone.me/mcp` | `wss://prism.api.rime.ai/v1/realtime` |
| Transports | Streamable HTTP | websocket |
| Auth | None | API key |
| 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. |
| Tools exposed | 4 | none |
| Last release | 2026-10-05 | 2026-11-01 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |

Why the edge:
- Maintenance & community, Rime Prism +52: 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.); 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.)
- Transparency & trust, Rime Prism +49: 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.); 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.)
- Agent ergonomics, Rime Prism +44: 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.); 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.)
- Reliability, Rime Prism +40: 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.); 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.)
- Schema & documentation, Rime Prism +38: 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.); 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.)
- Security & auth, Rime Prism +26: 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.); 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.)