# fone.me vs Gemini Live API (slim)

> Gemini Live scores 54.1 (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-gemini-live.md (~6,400 tokens) · this version ~3,880 tokens · JSON https://www.anchorterminal.com/compare/fone-me-vs-gemini-live.json · canonical https://www.anchorterminal.com/compare/fone-me-vs-gemini-live
- 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)

Gemini Live API scores 54.1 (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 #1429 of 1510 · https://www.anchorterminal.com/tools/fone-me.min.md
- Gemini Live API: C 54.1, rank #922 of 1510 · https://www.anchorterminal.com/tools/gemini-live.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; No incidents deducted, where Gemini Live API loses 3 points for them.
- Gemini Live API, good for Teams building their own voice or vision assistant on a single speech-to-speech model with function calling and Search grounding, who can run a backend for tokens and audio transport. Ahead on Reliability, 41 against 15; Schema & documentation, 66 against 31; Agent ergonomics, 69 against 29; Security & auth, 48 against 30; Maintenance & community, 83 against 23; Transparency & trust, 72 against 23.

| Category | fone.me | Gemini Live API |
| --- | --- | --- |
| Reliability (16%) | 15 | 41 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 31 | 66 |
| Agent ergonomics (13%) | 29 | 69 |
| Security & auth (14%) | 30 | 48 |
| Payments & pricing (10%) | 50 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 23 | 83 |
| Transparency & trust (7%) | 23 | 72 |

| Fact (where they differ) | fone.me | Gemini Live API |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Fone | Google |
| Hosted endpoint | `https://www.fone.me/mcp` | `https://generativelanguage.googleapis.com/v1beta` |
| Transports | Streamable HTTP | HTTP |
| 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 service under the Gemini API Additional Terms of Service. The Python and JavaScript SDKs are Apache-2.0 |
| Tools exposed | 4 | none |
| Last release | 2026-10-05 | 2026-10-29 |
| Terms last updated | couldn't be read | 2026-04-28 |
| Privacy policy last updated | couldn't be read | 2026-10-01 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | yes |
| 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 | not found in the text |
| Popularity | none | 29.5M npm/wk, 34.1M PyPI/wk |

Why the edge:
- Maintenance & community, Gemini Live API +60: 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.); Gemini Live API 83 (google-genai 2.34.0 (29 October 2026) changes the Live client, adding base_url, api_version and headers to `LiveConnectConfig.http_options` and a header fix in live.py, 6 days before the check (30). In the 90 days from 6 August, the changelog's `gemini-3.5-transcribe-live` (26 August) and 3.8 Live GA (15 September) entries, and Python SDK releases that change Live code, 2.18.0 (12 August), 2.19.0 (19 August), 2.23.0 (10 September), 2.26.0 (30 September), 2.30.0 (13 October), 2.32.0 (21 October), 2.33.0 (22 October) and 2.34.0 (29 October) (20). Closed service with a changelog updated several times a month. Support channels were not tested (10 of 15). Current official SDKs, `google-genai` v2.34.0 and `@google/genai` v2.32.0, both tagged 29 October (15). Apache-2.0 SDKs with type-check workflows in the Python repository and Node 20 or later stated. CI results were not read (8 of 10).)
- Transparency & trust, Gemini Live API +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.); Gemini Live API 72 (Closed service with clear terms, SDKs under Apache-2.0 (15 of 30). The terms, pricing page and zero data retention page agree that free-tier content improves Google products and paid content does not. The terms say abuse logs are kept for a limited period and the abuse monitoring page gives 55 days. Session state is kept up to 24 hours when resumption is on, and Search grounding data 30 days (20 of 30). A deprecations table gives earliest shutdown dates and replacements, with 17 November 2026 for the two older Live previews, about nine weeks after the replacement shipped, and no stated minimum notice (15 of 20). The terms say data may be stored transiently or cached in any country where Google has facilities. The Data Processing Addendum applies to paid services, and no sub-processor list was read (5 of 20).)
- Agent ergonomics, Gemini Live API +40: 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.); Gemini Live API 69 (Scored as an API. Context can be sized with sliding-window compression and a trigger token count, media resolution is configurable and `UsageMetadata` reports token counts (18 of 25). No lists to page. Output controls are turn coverage, optional transcription of either side and the compression window (12 of 20). Server signals an agent can act on are `interrupted`, `generationComplete`, GoAway and tool call cancellation, but there is no documented error catalogue for the socket (10 of 20). Session resumption makes reconnects safe, resuming does not spend a token use, and non-blocking function calls take `SILENT`, `WHEN_IDLE` or `INTERRUPT` scheduling. No idempotency guidance for tool side effects after an interruption (14 of 20). A session needs only a model and a response modality, voice activity detection is automatic, and there are official Python and JavaScript SDKs (15).)
- Schema & documentation, Gemini Live API +35: 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.); Gemini Live API 66 (No AsyncAPI or similar file for the WebSocket messages was found. The keyless Discovery document (revision 20261006) types `auth_tokens.create` and five related schemas, `BidiGenerateContentSetup` among them, but not the client and server messages (8 of 25). llms.txt with a Markdown twin of every page (10). The capabilities guide, model comparison table and best practices page say when to use each model, voice activity mode and tool behaviour (16 of 20). The reference at aistudio.google.com/api-reference/live lists every message with field types, enums such as `ActivityHandling`, `TurnCoverage` and the sensitivity levels, and required marks, as tables and not as a schema (12 of 15). Python and JavaScript examples on every guide, but no list of WebSocket close codes or Live error responses was found (8 of 15). Dated changelog and versioned model names, less 3 because the tools page omits the 3.8 models, the overview says 70 languages where the capabilities guide lists 99, and preview banners remain on two pages after general availability (12 of 15). Docs moved from ai.google.dev to aistudio.google.com by 4 November 2026; the pages not re-read stand per the 8 October check.)
- Reliability, Gemini Live API +26: 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.); Gemini Live API 41 (Graded as a hosted API on the Gemini Developer API. A status page exists at aistudio.google.com/status, but on 4 November it still returned a script shell titled "Google AI Studio" with no components or history we could read (10 of 20, and 5 of 30 for the incident line with no readable record). Session limits are published, 15 minutes for audio and 2 for audio with video without compression, connections of about 10 minutes, and spend limits per 10 minutes of $10 on Tier 1 and $200 on Tiers 2 and 3. Per-model request limits and concurrent sessions are shown only in AI Studio, so the earlier partial 8 of 15 is kept. The server sends a GoAway message with `timeLeft` before closing, session resumption handles last 2 hours, and the troubleshooting guide gives exponential backoff with jitter for 429 and 503 (12 of 15). No SLA found for the Developer API (0). `gemini-3.8-live` is stable and generally available since 15 September, but the endpoint is `v1beta`, ephemeral tokens are in preview and the capabilities guide and API reference still label the Live API a preview, so the earlier partial 6 of 10 is kept.)
- Security & auth, Gemini Live API +18: 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.); Gemini Live API 48 (Keys created since 28 May 2026 are authorisation keys bound to a service account and restricted to the Gemini API, with IP and origin restrictions, a leak checklist and rejection of unrestricted standard keys. Ephemeral tokens add expiry and use counts (25 of 30). The WebSocket guide, re-read on 4 November, still documents the API key as a `key` query parameter and ephemeral tokens as an `access_token` query parameter, so we deduct 10 on that documentation (15 of 30). Ephemeral tokens can be locked to a model and configuration and to one session, which keeps system instructions server side. There is no approval step for tool calls, which the client runs itself (12 of 20). The model hears callers and can ground on Google Search, and the best practices page covers guardrails in system instructions but not prompt injection (5 of 15). Opt-in logs exist for billed projects, and we did not confirm they cover Live sessions. Usage is visible per project (8 of 15). security.txt on google.com valid to 2030 with a vulnerability reward programme. No certification naming the Developer API was found (8 of 20).)