{ "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": 1429, "ranked": true, "rankOf": 1510, "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-07T19:22:07.71997153Z", "lastOk": true, "lastStatus": 405, "lastMs": 357, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 215, "p95ms24h": 511, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "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-07T19:22:07.71997153Z" } }, "answer": "OpenAI Realtime API scores 71.7 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing.", "b": { "slug": "openai-realtime", "name": "OpenAI Realtime API", "vendor": "OpenAI", "vendorUrl": "https://openai.com", "kind": "http-api", "category": "voice-agents", "summary": "OpenAI's Realtime API runs spoken conversations with speech-to-speech models such as `gpt-realtime-2.1`. Clients connect over WebRTC, WebSocket or SIP, and sessions support interruptions, function calling and remote MCP tools.", "url": "https://www.anchorterminal.com/tools/openai-realtime", "markdownUrl": "https://www.anchorterminal.com/tools/openai-realtime.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/openai-realtime.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/openai-realtime.json", "dns": "openai-realtime.grade.anchorterminal.com", "repo": "https://github.com/openai/openai-agents-js", "license": "Proprietary service under OpenAI's services agreement, per the OpenAI API listing's check (openai.com answered 403 to our reader on 2 November 2026). The Agents SDK for TypeScript and the OpenAPI description are MIT", "transports": [ "http" ], "remoteUrl": "https://api.openai.com/v1/realtime", "packages": [ { "registry": "npm", "name": "@openai/agents" }, { "registry": "npm", "name": "@openai/agents-realtime" } ], "auth": "api-key", "authNotes": "Self-serve API key from platform.openai.com, sent as a Bearer header on server WebSocket connections and call-control requests. For browsers and phones, a server calls `POST /v1/realtime/client_secrets` for a client secret (`ek_`) that lasts 10 seconds to 2 hours, 10 minutes by default, and can start several sessions until it expires. The browser WebSocket example passes the secret as a subprotocol. SIP calls are tied to a project by the project ID in the SIP address.", "pricing": "usage", "pricingNotes": "Per 1M tokens on `gpt-realtime-2.1`. Audio $32.00 in, $0.40 cached and $64.00 out, text $4.00 in and $24.00 out, image $5.00 in. `gpt-realtime-2.1-mini` is $10.00 and $20.00 for audio. Each response re-sends the whole conversation, and input transcription is billed separately. Usage tiers start at $5 of credit purchases, and the model page's rate limits start at Build, with no Free row (https://developers.openai.com/api/docs/pricing.md, checked 2026-11-02).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Realtime guides, the pricing page or the OpenAPI file (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://developers.openai.com/api/docs/guides/realtime", "llmsTxt": "https://developers.openai.com/api/docs/llms.txt", "openapi": "https://github.com/openai/openai-openapi/blob/main/openapi.yaml", "capabilities": [ "voice.agent", "voice.speech-to-speech", "voice.tools", "voice.telephony" ], "tags": [ "hosted", "usage-priced", "closed-source", "speech-to-speech", "webrtc", "websocket", "sip", "streaming", "typescript", "python", "openapi", "llms-txt", "api-key", "function-calling", "mcp-client", "status-page" ], "lastRelease": "2026-10-20", "graded": true, "anchor": { "graded": true, "score": 71.7, "grade": "BB", "agentReady": true, "rank": 149, "ranked": true, "rankOf": 1510, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 82, "payments": 30, "reliability": 62, "schema": 84, "security": 83, "transparency": 90 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "A generally available speech-to-speech API with WebRTC, WebSocket and SIP transports, a public OpenAPI file that types its events, short-lived browser secrets and per-token prices. Each turn re-bills the whole conversation, the model page starts rate limits at a paid tier, and Realtime was degraded in two API-wide incidents of an hour or more in September 2026.", "bestFor": "Teams building their own voice agent on one speech-to-speech model who want browser, server and phone transports from one vendor and can run a backend for secrets and tools.", "strengths": [ "The OpenAPI 3.1 file in `openai/openai-openapi` covers nine Realtime paths and types 11 client events and 46 server events in its event unions.", "Browser clients use client secrets that expire after 10 seconds to 2 hours, 10 minutes by default, so the API key stays on a server.", "Remote MCP tools accept an `allowed_tools` list, and `require_approval` defaults to `always` in the OpenAPI file.", "SIP calls connect at `sip.api.openai.com` with accept, reject, refer and hangup endpoints and a signed incoming-call webhook.", "The data controls page lists `/v1/realtime` with no training use, 30-day abuse logs, no stored application state and Zero Data Retention eligibility." ], "weaknesses": [ "Realtime was degraded in two API-wide incidents, for an hour on 17 September and for 5 hours 21 minutes on 29 September 2026.", "The `gpt-realtime-2.1` rate-limit table starts at Build, which needs $5 of credit, so Free tier access to Realtime isn't established.", "Every response re-sends the whole conversation, so later turns cost more. Audio is $32 in and $64 out per 1M tokens on `gpt-realtime-2.1`.", "Session settings attached to a client secret can be overridden by the client connection, per the client secret reference.", "Realtime sits under one Model capabilities permission, so a restricted key can't be limited to Realtime alone." ], "agentNotes": [ "Create a client secret on a server with `POST /v1/realtime/client_secrets` and give browsers only the `ek_` value. Never ship the API key.", "After a response with MCP calls finishes, send another `response.create`. The API does not create the follow-up response itself.", "Set `truncation` with a `retention_ratio` below 1 and `token_limits.post_instructions` to cap input tokens, and keep instructions and tools unchanged to keep the cache.", "On a WebSocket, stop playback on `input_audio_buffer.speech_started` and send `conversation.item.truncate` with `audio_end_ms`. WebRTC and SIP truncate on the server.", "Use `gpt-realtime-2.1` or `gpt-realtime-2.1-mini`. `gpt-realtime` and `gpt-realtime-mini` shut down on 20 January 2027, and `whisper-1` and `gpt-4o-transcribe` on 26 February 2027." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.7 } ], "editorialScores": { "ergonomics": 76, "maintenance": 82, "payments": 30, "reliability": 62, "schema": 84, "security": 83, "transparency": 85 }, "provenanceScore": 95, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install @openai/agents", "http": "curl -X POST https://api.openai.com/v1/realtime/client_secrets \\\n -H \"Authorization: Bearer $OPENAI_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"session\": {\"type\": \"realtime\", \"model\": \"gpt-realtime-2.1\"}}'" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/openai-realtime" }, "sameCompany": [ "openai-api", "openai-embeddings", "openai-guardrails", "openai-moderation", "openai-image-api", "openai-sora", "openai-speech-to-text", "gpt-live", "openai-agents-sdk", "openai-decisions-api", "openai-agents-api", "openai-codex", "gpt-oss-120b", "gpt-oss-20b" ], "area": "voice", "unitPrices": [ { "item": "gpt-realtime-2.1 audio input", "unit": "1m-tokens", "usd": 32, "note": "$0.40 cached. 1 token per 100 ms of user audio, about $0.019 a minute before caching" }, { "item": "gpt-realtime-2.1 audio output", "unit": "1m-tokens", "usd": 64, "note": "1 token per 50 ms of assistant audio, about $0.077 a minute" }, { "item": "gpt-realtime-2.1 text input", "unit": "1m-tokens", "usd": 4, "note": "$0.40 cached" }, { "item": "gpt-realtime-2.1 text output", "unit": "1m-tokens", "usd": 24 }, { "item": "gpt-realtime-2.1-mini audio input", "unit": "1m-tokens", "usd": 10, "note": "$0.30 cached" }, { "item": "gpt-realtime-2.1-mini audio output", "unit": "1m-tokens", "usd": 20 } ], "provenance": { "legalEntity": "OpenAI OpCo, LLC", "domain": "openai.com", "domainRegistered": "2007-01-19", "domainNote": "openai.com was registered in 2007, before OpenAI existed.", "endpointOnVendorDomain": true, "terms": "https://openai.com/policies/services-agreement/", "privacy": "https://openai.com/policies/privacy-policy/", "statusPage": "https://status.openai.com", "changelog": "https://developers.openai.com/api/docs/changelog", "securityTxt": "valid", "checked": "2026-11-02", "notes": [ "The API, WebRTC and SIP endpoints are on api.openai.com and sip.api.openai.com. The docs are on developers.openai.com.", "Same entity, terms and privacy policy as the OpenAI API listing. The legal entity and the two policy URLs stand per that listing's check of 26 September. openai.com answered the services agreement with HTTP 403 on 2 November 2026.", "RDAP gives openai.com a registration date of 2007-01-19.", "openai.com/.well-known/security.txt, read on 2 November 2026, is PGP-signed with Bugcrowd and email contacts and a disclosure policy, and has no Expires field.", "robots.txt answered 200 on developers.openai.com, openai.com and trust.openai.com, allowing the pages read, and 404 on status.openai.com, which means no rules.", "status.openai.com lists a Realtime component under the API group." ], "score": 95 }, "requirements": { "setupChecked": true, "complianceChecked": true, "card": "paid-only", "freeTier": true, "minutes": 5, "credential": "api-key", "hosting": [ "US", "EU", "UK", "CA", "APAC" ], "euResidency": "enterprise", "trainsOnData": "no", "zeroRetention": "enterprise", "certifications": [ "SOC 2 Type II", "ISO 27001", "ISO 27701", "ISO 42001", "CSA STAR", "HIPAA (BAA available)", "GDPR" ], "dpa": true, "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/openai-realtime.json", "live": { "slug": "openai-realtime", "probe": { "target": "https://api.openai.com/v1/realtime", "method": "get", "lastAt": "2026-11-07T19:22:23.821067756Z", "lastOk": true, "lastStatus": 405, "lastMs": 149, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 157, "p95ms24h": 203, "samples24h": 238, "samples30d": 7215, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.openai.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:58.84000537Z" }, "versions": [ { "registry": "github", "name": "openai/openai-agents-js", "version": "@openai/agents-extensions@0.21.0", "released": "2026-10-20", "seenAt": "2026-11-06T23:52:08.923189579Z" }, { "registry": "npm", "name": "@openai/agents", "version": "0.21.0", "seenAt": "2026-11-06T23:52:06.660735864Z" }, { "registry": "npm", "name": "@openai/agents-realtime", "version": "0.21.0", "seenAt": "2026-11-06T23:52:06.891647011Z" } ], "githubStars": 3985, "npmWeekly": 2490720, "securityTxt": { "url": "https://openai.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:49.231731777Z" }, "llmsTxt": { "url": "https://developers.openai.com/api/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:34.663556539Z" }, "domain": { "domain": "openai.com", "registered": "2007-01-19", "source": "https://rdap.verisign.com/com/v1/domain/openai.com", "checkedAt": "2026-11-01T14:19:18.345389832Z" }, "pages": [ { "url": "https://developers.openai.com/api/docs/pricing.md", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:04:29.761864367Z", "changedAt": "2026-11-06T13:27:02.980260155Z", "fingerprint": "a83cd96e6a1c" } ], "github": { "repo": "openai/openai-agents-js", "checkedAt": "2026-11-02T09:12:52.597064382Z", "stars": 3961, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T09:20:30Z", "openIssues": 19, "openPRs": 11, "issuesOpened90d": 64, "issuesClosed90d": 65, "prsMerged90d": 319, "ci": { "branch": "main", "runs": 50, "success": 45, "failure": 5, "other": 0, "latest": "failure", "latestAt": "2026-10-30T23:12:28Z" }, "replies": { "sampled": 25, "unanswered": 11, "medianDays": 1.2 } }, "updatedAt": "2026-11-07T19:22:58.84000537Z" } }, "edges": [ { "by": 67, "category": "transparency", "leads": "openai-realtime", "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, per the OpenAI API listing's check of the services agreement, which answered 403 to our reader again on 2 November. The Agents SDK for TypeScript and the OpenAPI file are MIT (15, was 10). The data controls page, re-read on 2 November, lists `/v1/realtime` with no training use, abuse monitoring logs kept up to 30 days, no stored application state and Zero Data Retention eligibility. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum, and nothing in it conflicts with the guide, per the OpenAI API listing's 4 October check, not re-read on 2 November. The same reading as the other OpenAI listings (30, was 18). The deprecations page, re-read on 2 November, states at least six months' notice for generally available models and lists shutdown dates with replacements, including `gpt-realtime` and `gpt-realtime-mini` on 20 January 2027 (20). The guide documents residency for `/v1/realtime` in the United States and Europe for storage and processing, with a `sip-eu.api.openai.com` endpoint, and says tracing on `/v1/realtime` isn't EU residency compliant. The subprocessor list, updated 9 July 2026, names third-party subprocessors and OpenAI affiliates with processing countries for each and a form for notice of new ones, per the OpenAI API listing's 4 October check, not re-read on 2 November. The guide states the residency limit, which counts as disclosure, so the same reading as the other OpenAI listings (20, was 10). 15 + 30 + 20 + 20 = 85." }, "scores": { "a": 23, "b": 90 } }, { "by": 59, "category": "maintenance", "leads": "openai-realtime", "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": "The last dated changelog entry tagged `v1/realtime` is the 26 August 2026 deprecation of `whisper-1`, `gpt-4o-transcribe` and two related models, which Realtime sessions can use for input transcripts, after `gpt-transcribe` for committed Realtime turns on 28 July. The listing's own package, `@openai/agents-realtime`, released 0.21.0 on 20 October 2026, 13 days before the check, with Realtime fixes (WebRTC connections rejected when the server reports an error before the session is configured, Twilio audio defaults kept), read from a clone. A release that changes the product's own package sets the recency line in this run (30, was 20 when SDK releases weren't read on this line). In the 90 days from 4 August the changelog has one `v1/realtime` entry and the SDK has 11 version tags, 0.14.3 on 5 August to 0.21.0, at least seven of which change the Realtime package's source. SDK tags count half, so 1 + 3.5 clears three (20, was 0). Closed service with a changelog updated several times a week, plus a community forum and Discord linked from the docs, which we did not test (10 of 15). Current official SDKs, `@openai/agents` and `@openai/agents-realtime` 0.21.0 (15). The SDK is MIT but still 0.x, and its CI results were not read (7 of 10). 30 + 20 + 10 + 15 + 7 = 82." }, "scores": { "a": 23, "b": 82 } }, { "by": 53, "category": "schema", "leads": "openai-realtime", "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": "The OpenAPI 3.1 file in `openai/openai-openapi` (version 2.3.0, last committed 31 October 2026, read from a clone on 2 November) has nine `/realtime` paths and 185 Realtime schemas, with 11 client events and 46 server events in its main event unions and separate translation session events. It is not an AsyncAPI document, so the WebSocket channel itself is not described (22 of 25). llms.txt and a Markdown twin of every docs page, re-read on 2 November (10). The tools guide has a table of when to use `function`, `mcp` with `server_url` or a connector, and the transport guides say when to choose WebRTC, WebSocket or SIP, per the 9 October check (16 of 20). Session fields carry enums and ranges, such as `expires_after.seconds` from 10 to 7200, though `model` also accepts any string (13 of 15). Examples in JavaScript, Python, Java, Ruby and C#, an `error` event with type, code, message and param, and a list of common MCP failures. No catalogue of Realtime error codes was found (11 of 15). Dated changelog and dated snapshots for the older models (`gpt-realtime-2.1` lists only its alias), less 3 because the OpenAPI file still names `gpt-4o-realtime-preview` models (12 mentions on 2 November) that the deprecations page says were removed on 7 May 2026, and several guides mix GPT-Live and Realtime text on one page (12 of 15). 22 + 10 + 16 + 13 + 11 + 12 = 84." }, "scores": { "a": 31, "b": 84 } }, { "by": 53, "category": "security", "leads": "openai-realtime", "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": "Server connections send the API key as a Bearer header. Browsers use client secrets from `POST /v1/realtime/client_secrets` that last 10 seconds to 2 hours, 10 minutes by default, and can open several sessions until expiry, and the browser WebSocket example passes the secret as a subprotocol, not in the query string. Project keys take All, Restricted or Read Only permissions, with service accounts, workload identity federation and mutual TLS, per the OpenAI API listing's check. The permissions guide, read on 2 November, puts `/v1/realtime` under one Model capabilities permission with chat completions, audio, embeddings, images, moderations and responses, so a restricted key can't be limited to Realtime alone (27 of 30, as the OpenAI Speech-to-text listing, was 24 when key scopes were unread). MCP tools take `allowed_tools` and `require_approval`, which defaults to `always` in the OpenAPI file, and a sideband connection keeps tool execution on the server. Session settings attached to a client secret can be overridden by the client connection (15 of 20). The model hears callers and reads MCP results. The SIP guide says to treat SIP headers as untrusted, and no prompt-injection guidance specific to Realtime was found, per the 9 October check (6 of 15). The Admin APIs include audit log retrieval, and since 4 August 2026 the Usage and Costs dashboards and APIs filter and group by API key, the per-key view the other OpenAI listings get 15 for. The Usage API has no Realtime-specific endpoint (15, was 10). openai.com's security.txt, read on 2 November, is PGP-signed with a Bugcrowd programme, a disclosure email and a coordinated disclosure policy, and has no Expires field. trust.openai.com, read on 2 November, names SOC 2 Type 2, ISO/IEC 27001, 27017, 27018, 27701 and 42001 and CSA STAR (20, was 6 when openai.com refused our reader, the award the other OpenAI listings carry). 27 + 15 + 6 + 15 + 20 = 83." }, "scores": { "a": 30, "b": 83 } }, { "by": 47, "category": "reliability", "leads": "openai-realtime", "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": "Graded as a hosted API. status.openai.com (incident.io) lists Realtime as a component of the API group with history (20). The feed, read on 2 November (102 items, 4 August to 30 October), names Realtime in three incidents in the 90 days from 4 August, and each incident page gives the component's impact. Elevated error rates across API models on 17 September, with Realtime degraded from 20:20 to 21:20 UTC alongside ten other API components, and elevated errors across ChatGPT, Codex and the API on 29 September, with Realtime degraded from 17:52 to 23:14 UTC, are each an hour or more of wide errors, so two majors. Degraded performance across ChatGPT, Codex and the APIs on 21 October listed Realtime for 22 minutes (02:26 to 02:48 UTC), so minor. The 11 August incident on the API, Codex and Work Mode lists no components and isn't counted, as on the other OpenAI listings, and the July incidents the 9 October check counted have left the window. Two majors give 5, as the OpenAI API, Moderation, Embeddings and Speech-to-text listings read the same two incidents (5 of 30, was 20 when the durations were unread). The `gpt-realtime-2.1` model page, read on 2 November, gives 400 requests and 200,000 tokens a minute on Build, 10,000 and 4 million on Launch and 20,000 and 15 million on Grow (15, was 5 when the limits were known only from account settings). The docs describe `Retry-After` on 429 and 503, exponential backoff with jitter and SDK retries, sessions emit `rate_limits.updated`, and SIP webhooks carry a `webhook-id` for deduplication, per the 9 October check. No idempotency key for call control was found, so safe-retry guidance without keys (12 of 15). No SLA covering Realtime was found, read as on the other OpenAI listings, where the Scale Tier SLA names GPT and o-series models (0). Generally available since 28 August 2025 (10). 20 + 5 + 15 + 12 + 0 + 10 = 62." }, "scores": { "a": 15, "b": 62 } }, { "by": 47, "category": "ergonomics", "leads": "openai-realtime", "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": "Read on the API lines, per the 9 October check of the guides, not re-read on 2 November. Context can be capped with `truncation`, `retention_ratio` and `token_limits.post_instructions`, items can be deleted, prompt caching is automatic, and `response.done` reports token usage by modality (22 of 25). There are no lists to page. Output controls are `output_modalities`, `max_output_tokens`, optional input transcription and `allowed_tools` (14 of 20). The `error` event returns the `event_id` of the client event that caused it, and MCP tool listing and calls have their own failure events (15 of 20). Client events take an `event_id`, webhooks carry a `webhook-id`, and interruptions cancel the response. No session resumption after a dropped connection and no idempotency key for call control were found (10 of 20). A session needs only a model, voice activity detection is automatic, and the Agents SDK starts a browser voice agent in about ten lines, with examples in five languages (15). 22 + 14 + 15 + 10 + 15 = 76." }, "scores": { "a": 29, "b": 76 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Fone", "b": "OpenAI", "name": "Vendor" }, { "a": "https://www.fone.me/mcp", "b": "https://api.openai.com/v1/realtime", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "None", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "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 service under OpenAI's services agreement, per the OpenAI API listing's check (openai.com answered 403 to our reader on 2 November 2026). The Agents SDK for TypeScript and the OpenAPI description are 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-10-20", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "3.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "OpenAI Realtime API scores 71.7 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing.", "question": "Which is better for AI agents, fone.me or OpenAI Realtime API?" }, { "answer": "Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and OpenAI Realtime API at https://api.openai.com/v1/realtime.", "question": "Can an agent call fone.me and OpenAI Realtime API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 50 against 30" ], "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, 62 against 15", "Schema \u0026 documentation, 84 against 31", "Agent ergonomics, 76 against 29", "Security \u0026 auth, 83 against 30", "Maintenance \u0026 community, 82 against 23", "Transparency \u0026 trust, 90 against 23" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "Teams building their own voice agent on one speech-to-speech model who want browser, server and phone transports from one vendor and can run a backend for secrets and tools.", "slug": "openai-realtime", "watchFor": "Realtime was degraded in two API-wide incidents, for an hour on 17 September and for 5 hours 21 minutes on 29 September 2026." } ], "history": { "fone-me": null, "openai-realtime": [ { "causes": [ "evidence", "correction" ], "date": "2026-11-02", "delta": 8.3, "from": 63.4, "fromGrade": "B", "to": 71.7, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 63.3, "fromGrade": "B", "to": 63.4, "toGrade": "B" } ] }, "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-openai-realtime.json", "title": "Amazon Nova 2 Sonic vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-openai-realtime" }, { "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-openai-realtime.json", "title": "AssemblyAI Voice Agent API vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-openai-realtime" }, { "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-openai-realtime.json", "title": "Bland AI API + MCP vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-openai-realtime" }, { "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-openai-realtime.json", "title": "Bolna API + MCP vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/bolna-vs-openai-realtime" }, { "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-openai-realtime.json", "title": "Deepgram Voice Agent API vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/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-openai-realtime.json", "title": "ElevenLabs Agents API + MCP vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-openai-realtime" }, { "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-pipecat.json", "title": "fone.me vs Pipecat", "url": "https://www.anchorterminal.com/compare/fone-me-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-placecall.json", "title": "fone.me vs PlaceCall", "url": "https://www.anchorterminal.com/compare/fone-me-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-retell-ai.json", "title": "fone.me vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.json", "title": "fone.me vs Rime Prism", "url": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow.json", "title": "fone.me vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-ultravox.json", "title": "fone.me vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.json", "title": "fone.me vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vapi.json", "title": "fone.me vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vocily.json", "title": "fone.me vs Vocily AI", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vogent.json", "title": "fone.me vs Vogent API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/gemini-live-vs-openai-realtime.json", "title": "Gemini Live API vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-openai-realtime.json", "title": "Harmony.ai vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-openai-realtime.json", "title": "Hume EVI (Empathic Voice Interface) vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime.json", "title": "Inworld Realtime API vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/livekit-agents-vs-openai-realtime.json", "title": "LiveKit Agents vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/livekit-agents-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-pipecat.json", "title": "OpenAI Realtime API vs Pipecat", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-placecall.json", "title": "OpenAI Realtime API vs PlaceCall", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-retell-ai.json", "title": "OpenAI Realtime API vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-retell-ai" }, { "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/openai-realtime-vs-synthflow.json", "title": "OpenAI Realtime API vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-ultravox.json", "title": "OpenAI Realtime API vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-vaani-voice.json", "title": "OpenAI Realtime API vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-vapi.json", "title": "OpenAI Realtime API vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-vocily.json", "title": "OpenAI Realtime API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-vogent.json", "title": "OpenAI Realtime API vs Vogent API", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-openai-realtime.json", "title": "GPT-Live vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-pipecat-phonellm.json", "title": "OpenAI Realtime API vs Pipecat PhoneLLM", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-pipecat-phonellm" } ], "panel": null, "scores": [ { "by": 47, "edge": "openai-realtime", "fone-me": 15, "key": "reliability", "name": "Reliability", "openai-realtime": 62, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 53, "edge": "openai-realtime", "fone-me": 31, "key": "schema", "name": "Schema \u0026 documentation", "openai-realtime": 84, "weight": 13 }, { "by": 47, "edge": "openai-realtime", "fone-me": 29, "key": "ergonomics", "name": "Agent ergonomics", "openai-realtime": 76, "weight": 13 }, { "by": 53, "edge": "openai-realtime", "fone-me": 30, "key": "security", "name": "Security \u0026 auth", "openai-realtime": 83, "weight": 14 }, { "by": 20, "edge": "fone-me", "fone-me": 50, "key": "payments", "name": "Payments \u0026 pricing", "openai-realtime": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 59, "edge": "openai-realtime", "fone-me": 23, "key": "maintenance", "name": "Maintenance \u0026 community", "openai-realtime": 82, "weight": 7 }, { "by": 67, "edge": "openai-realtime", "fone-me": 23, "key": "transparency", "name": "Transparency \u0026 trust", "openai-realtime": 90, "weight": 7 } ], "summary": "OpenAI Realtime API scores 71.7 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing. Both do voice agents.", "tasks": null, "tutorials": [], "verdicts": { "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.", "openai-realtime": "A generally available speech-to-speech API with WebRTC, WebSocket and SIP transports, a public OpenAPI file that types its events, short-lived browser secrets and per-token prices. Each turn re-bills the whole conversation, the model page starts rate limits at a paid tier, and Realtime was degraded in two API-wide incidents of an hour or more in September 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime", "json": "https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.min.md" }, "markdown": "OpenAI Realtime API scores 71.7 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing. Both do voice agents.\n\n- fone.me: grade F, 28.3/100, rank #1429 of 1510. Markdown https://www.anchorterminal.com/tools/fone-me.md · JSON https://www.anchorterminal.com/api/v1/tools/fone-me.json\n- OpenAI Realtime API: grade BB, 71.7/100, rank #149 of 1510. Markdown https://www.anchorterminal.com/tools/openai-realtime.md · JSON https://www.anchorterminal.com/api/v1/tools/openai-realtime.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 30\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### OpenAI Realtime API (BB)\n\nGood for: Teams building their own voice agent on one speech-to-speech model who want browser, server and phone transports from one vendor and can run a backend for secrets and tools.\n\nAhead on:\n- Reliability, 62 against 15\n- Schema \u0026 documentation, 84 against 31\n- Agent ergonomics, 76 against 29\n- Security \u0026 auth, 83 against 30\n- Maintenance \u0026 community, 82 against 23\n- Transparency \u0026 trust, 90 against 23\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: Realtime was degraded in two API-wide incidents, for an hour on 17 September and for 5 hours 21 minutes on 29 September 2026.\n\n\n## Why the edge\n\n### Transparency \u0026 trust: OpenAI Realtime API +67\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- OpenAI Realtime API (90): Closed service with clear terms, per the OpenAI API listing's check of the services agreement, which answered 403 to our reader again on 2 November. The Agents SDK for TypeScript and the OpenAPI file are MIT (15, was 10). The data controls page, re-read on 2 November, lists `/v1/realtime` with no training use, abuse monitoring logs kept up to 30 days, no stored application state and Zero Data Retention eligibility. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum, and nothing in it conflicts with the guide, per the OpenAI API listing's 4 October check, not re-read on 2 November. The same reading as the other OpenAI listings (30, was 18). The deprecations page, re-read on 2 November, states at least six months' notice for generally available models and lists shutdown dates with replacements, including `gpt-realtime` and `gpt-realtime-mini` on 20 January 2027 (20). The guide documents residency for `/v1/realtime` in the United States and Europe for storage and processing, with a `sip-eu.api.openai.com` endpoint, and says tracing on `/v1/realtime` isn't EU residency compliant. The subprocessor list, updated 9 July 2026, names third-party subprocessors and OpenAI affiliates with processing countries for each and a form for notice of new ones, per the OpenAI API listing's 4 October check, not re-read on 2 November. The guide states the residency limit, which counts as disclosure, so the same reading as the other OpenAI listings (20, was 10). 15 + 30 + 20 + 20 = 85.\n\n### Maintenance \u0026 community: OpenAI Realtime API +59\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- OpenAI Realtime API (82): The last dated changelog entry tagged `v1/realtime` is the 26 August 2026 deprecation of `whisper-1`, `gpt-4o-transcribe` and two related models, which Realtime sessions can use for input transcripts, after `gpt-transcribe` for committed Realtime turns on 28 July. The listing's own package, `@openai/agents-realtime`, released 0.21.0 on 20 October 2026, 13 days before the check, with Realtime fixes (WebRTC connections rejected when the server reports an error before the session is configured, Twilio audio defaults kept), read from a clone. A release that changes the product's own package sets the recency line in this run (30, was 20 when SDK releases weren't read on this line). In the 90 days from 4 August the changelog has one `v1/realtime` entry and the SDK has 11 version tags, 0.14.3 on 5 August to 0.21.0, at least seven of which change the Realtime package's source. SDK tags count half, so 1 + 3.5 clears three (20, was 0). Closed service with a changelog updated several times a week, plus a community forum and Discord linked from the docs, which we did not test (10 of 15). Current official SDKs, `@openai/agents` and `@openai/agents-realtime` 0.21.0 (15). The SDK is MIT but still 0.x, and its CI results were not read (7 of 10). 30 + 20 + 10 + 15 + 7 = 82.\n\n### Schema \u0026 documentation: OpenAI Realtime API +53\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- OpenAI Realtime API (84): The OpenAPI 3.1 file in `openai/openai-openapi` (version 2.3.0, last committed 31 October 2026, read from a clone on 2 November) has nine `/realtime` paths and 185 Realtime schemas, with 11 client events and 46 server events in its main event unions and separate translation session events. It is not an AsyncAPI document, so the WebSocket channel itself is not described (22 of 25). llms.txt and a Markdown twin of every docs page, re-read on 2 November (10). The tools guide has a table of when to use `function`, `mcp` with `server_url` or a connector, and the transport guides say when to choose WebRTC, WebSocket or SIP, per the 9 October check (16 of 20). Session fields carry enums and ranges, such as `expires_after.seconds` from 10 to 7200, though `model` also accepts any string (13 of 15). Examples in JavaScript, Python, Java, Ruby and C#, an `error` event with type, code, message and param, and a list of common MCP failures. No catalogue of Realtime error codes was found (11 of 15). Dated changelog and dated snapshots for the older models (`gpt-realtime-2.1` lists only its alias), less 3 because the OpenAPI file still names `gpt-4o-realtime-preview` models (12 mentions on 2 November) that the deprecations page says were removed on 7 May 2026, and several guides mix GPT-Live and Realtime text on one page (12 of 15). 22 + 10 + 16 + 13 + 11 + 12 = 84.\n\n### Security \u0026 auth: OpenAI Realtime API +53\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- OpenAI Realtime API (83): Server connections send the API key as a Bearer header. Browsers use client secrets from `POST /v1/realtime/client_secrets` that last 10 seconds to 2 hours, 10 minutes by default, and can open several sessions until expiry, and the browser WebSocket example passes the secret as a subprotocol, not in the query string. Project keys take All, Restricted or Read Only permissions, with service accounts, workload identity federation and mutual TLS, per the OpenAI API listing's check. The permissions guide, read on 2 November, puts `/v1/realtime` under one Model capabilities permission with chat completions, audio, embeddings, images, moderations and responses, so a restricted key can't be limited to Realtime alone (27 of 30, as the OpenAI Speech-to-text listing, was 24 when key scopes were unread). MCP tools take `allowed_tools` and `require_approval`, which defaults to `always` in the OpenAPI file, and a sideband connection keeps tool execution on the server. Session settings attached to a client secret can be overridden by the client connection (15 of 20). The model hears callers and reads MCP results. The SIP guide says to treat SIP headers as untrusted, and no prompt-injection guidance specific to Realtime was found, per the 9 October check (6 of 15). The Admin APIs include audit log retrieval, and since 4 August 2026 the Usage and Costs dashboards and APIs filter and group by API key, the per-key view the other OpenAI listings get 15 for. The Usage API has no Realtime-specific endpoint (15, was 10). openai.com's security.txt, read on 2 November, is PGP-signed with a Bugcrowd programme, a disclosure email and a coordinated disclosure policy, and has no Expires field. trust.openai.com, read on 2 November, names SOC 2 Type 2, ISO/IEC 27001, 27017, 27018, 27701 and 42001 and CSA STAR (20, was 6 when openai.com refused our reader, the award the other OpenAI listings carry). 27 + 15 + 6 + 15 + 20 = 83.\n\n### Reliability: OpenAI Realtime API +47\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- OpenAI Realtime API (62): Graded as a hosted API. status.openai.com (incident.io) lists Realtime as a component of the API group with history (20). The feed, read on 2 November (102 items, 4 August to 30 October), names Realtime in three incidents in the 90 days from 4 August, and each incident page gives the component's impact. Elevated error rates across API models on 17 September, with Realtime degraded from 20:20 to 21:20 UTC alongside ten other API components, and elevated errors across ChatGPT, Codex and the API on 29 September, with Realtime degraded from 17:52 to 23:14 UTC, are each an hour or more of wide errors, so two majors. Degraded performance across ChatGPT, Codex and the APIs on 21 October listed Realtime for 22 minutes (02:26 to 02:48 UTC), so minor. The 11 August incident on the API, Codex and Work Mode lists no components and isn't counted, as on the other OpenAI listings, and the July incidents the 9 October check counted have left the window. Two majors give 5, as the OpenAI API, Moderation, Embeddings and Speech-to-text listings read the same two incidents (5 of 30, was 20 when the durations were unread). The `gpt-realtime-2.1` model page, read on 2 November, gives 400 requests and 200,000 tokens a minute on Build, 10,000 and 4 million on Launch and 20,000 and 15 million on Grow (15, was 5 when the limits were known only from account settings). The docs describe `Retry-After` on 429 and 503, exponential backoff with jitter and SDK retries, sessions emit `rate_limits.updated`, and SIP webhooks carry a `webhook-id` for deduplication, per the 9 October check. No idempotency key for call control was found, so safe-retry guidance without keys (12 of 15). No SLA covering Realtime was found, read as on the other OpenAI listings, where the Scale Tier SLA names GPT and o-series models (0). Generally available since 28 August 2025 (10). 20 + 5 + 15 + 12 + 0 + 10 = 62.\n\n### Agent ergonomics: OpenAI Realtime API +47\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- OpenAI Realtime API (76): Read on the API lines, per the 9 October check of the guides, not re-read on 2 November. Context can be capped with `truncation`, `retention_ratio` and `token_limits.post_instructions`, items can be deleted, prompt caching is automatic, and `response.done` reports token usage by modality (22 of 25). There are no lists to page. Output controls are `output_modalities`, `max_output_tokens`, optional input transcription and `allowed_tools` (14 of 20). The `error` event returns the `event_id` of the client event that caused it, and MCP tool listing and calls have their own failure events (15 of 20). Client events take an `event_id`, webhooks carry a `webhook-id`, and interruptions cancel the response. No session resumption after a dropped connection and no idempotency key for call control were found (10 of 20). A session needs only a model, voice activity detection is automatic, and the Agents SDK starts a browser voice agent in about ten lines, with examples in five languages (15). 22 + 14 + 15 + 10 + 15 = 76.\n\n## Score by category\n\n| Category | Weight | fone.me | OpenAI Realtime API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 62 | OpenAI Realtime API +47 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 31 | 84 | OpenAI Realtime API +53 |\n| Agent ergonomics | 13% (16.2 this run) | 29 | 76 | OpenAI Realtime API +47 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 83 | OpenAI Realtime API +53 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 30 | fone.me +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 23 | 82 | OpenAI Realtime API +59 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 23 | 90 | OpenAI Realtime API +67 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **28.3 · F** | **71.7 · BB** | |\n\n## Facts side by side\n\n| Fact | fone.me | OpenAI Realtime API |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Fone | OpenAI |\n| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.openai.com/v1/realtime` |\n| Transports | Streamable HTTP | HTTP |\n| Auth | None | API key |\n| Pricing | Freemium | Pay per use |\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 service under OpenAI's services agreement, per the OpenAI API listing's check (openai.com answered 403 to our reader on 2 November 2026). The Agents SDK for TypeScript and the OpenAPI description are 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-10-20 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | couldn't be read |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Agent reviews | none | 3.3/5 (4) |\n\n## How the scores have moved\n\n### fone.me\n\nNo score change since it was listed.\n\n### OpenAI Realtime API\n\n- +8.3 on 2 November 2026 (B to BB): new evidence, correction\n- +0.1 on 27 October 2026: checklist\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**OpenAI Realtime API.** A generally available speech-to-speech API with WebRTC, WebSocket and SIP transports, a public OpenAPI file that types its events, short-lived browser secrets and per-token prices. Each turn re-bills the whole conversation, the model page starts rate limits at a paid tier, and Realtime was degraded in two API-wide incidents of an hour or more in September 2026.\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### OpenAI Realtime API\n\n1. Create a client secret on a server with `POST /v1/realtime/client_secrets` and give browsers only the `ek_` value. Never ship the API key.\n2. After a response with MCP calls finishes, send another `response.create`. The API does not create the follow-up response itself.\n3. Set `truncation` with a `retention_ratio` below 1 and `token_limits.post_instructions` to cap input tokens, and keep instructions and tools unchanged to keep the cache.\n4. On a WebSocket, stop playback on `input_audio_buffer.speech_started` and send `conversation.item.truncate` with `audio_end_ms`. WebRTC and SIP truncate on the server.\n5. Use `gpt-realtime-2.1` or `gpt-realtime-2.1-mini`. `gpt-realtime` and `gpt-realtime-mini` shut down on 20 January 2027, and `whisper-1` and `gpt-4o-transcribe` on 26 February 2027.\n\n## Questions\n\n### Which is better for AI agents, fone.me or OpenAI Realtime API?\n\nOpenAI Realtime API scores 71.7 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing.\n\n### Can an agent call fone.me and OpenAI Realtime API without installing anything?\n\nYes. fone.me has a hosted endpoint at https://www.fone.me/mcp and OpenAI Realtime API at https://api.openai.com/v1/realtime.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fone-me\", \"b\": \"openai-realtime\"}`. From a terminal: `anchor compare fone-me openai-realtime`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fone-me.json and https://www.anchorterminal.com/api/v1/tools/openai-realtime.json\n\n## Other comparisons with fone.me or OpenAI Realtime API\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 OpenAI Realtime API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-openai-realtime.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 OpenAI Realtime API](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-openai-realtime.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 OpenAI Realtime API](https://www.anchorterminal.com/compare/bland-ai-vs-openai-realtime.md)\n- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)\n- [Bolna API + MCP vs OpenAI Realtime API](https://www.anchorterminal.com/compare/bolna-vs-openai-realtime.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 OpenAI Realtime API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-openai-realtime.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 OpenAI Realtime API](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-openai-realtime.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 Pipecat](https://www.anchorterminal.com/compare/fone-me-vs-pipecat.md)\n- [fone.me vs PlaceCall](https://www.anchorterminal.com/compare/fone-me-vs-placecall.md)\n- [fone.me vs Retell AI API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-retell-ai.md)\n- [fone.me vs Rime Prism](https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.md)\n- [fone.me vs Synthflow API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-synthflow.md)\n- [fone.me vs Ultravox Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-ultravox.md)\n- [fone.me vs Vaani Developer Platform](https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.md)\n- [fone.me vs Vapi API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-vapi.md)\n- [fone.me vs Vocily AI](https://www.anchorterminal.com/compare/fone-me-vs-vocily.md)\n- [fone.me vs Vogent API](https://www.anchorterminal.com/compare/fone-me-vs-vogent.md)\n- [Gemini Live API vs OpenAI Realtime API](https://www.anchorterminal.com/compare/gemini-live-vs-openai-realtime.md)\n- [Harmony.ai vs OpenAI Realtime API](https://www.anchorterminal.com/compare/harmony-ai-vs-openai-realtime.md)\n- [Hume EVI (Empathic Voice Interface) vs OpenAI Realtime API](https://www.anchorterminal.com/compare/hume-evi-vs-openai-realtime.md)\n- [Inworld Realtime API vs OpenAI Realtime API](https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime.md)\n- [LiveKit Agents vs OpenAI Realtime API](https://www.anchorterminal.com/compare/livekit-agents-vs-openai-realtime.md)\n- [OpenAI Realtime API vs Pipecat](https://www.anchorterminal.com/compare/openai-realtime-vs-pipecat.md)\n- [OpenAI Realtime API vs PlaceCall](https://www.anchorterminal.com/compare/openai-realtime-vs-placecall.md)\n- [OpenAI Realtime API vs Retell AI API + MCP](https://www.anchorterminal.com/compare/openai-realtime-vs-retell-ai.md)\n- [OpenAI Realtime API vs Rime Prism](https://www.anchorterminal.com/compare/openai-realtime-vs-rime-prism.md)\n- [OpenAI Realtime API vs Synthflow API + MCP](https://www.anchorterminal.com/compare/openai-realtime-vs-synthflow.md)\n- [OpenAI Realtime API vs Ultravox Realtime API](https://www.anchorterminal.com/compare/openai-realtime-vs-ultravox.md)\n- [OpenAI Realtime API vs Vaani Developer Platform](https://www.anchorterminal.com/compare/openai-realtime-vs-vaani-voice.md)\n- [OpenAI Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/openai-realtime-vs-vapi.md)\n- [OpenAI Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/openai-realtime-vs-vocily.md)\n- [OpenAI Realtime API vs Vogent API](https://www.anchorterminal.com/compare/openai-realtime-vs-vogent.md)\n- [GPT-Live vs OpenAI Realtime API](https://www.anchorterminal.com/compare/gpt-live-vs-openai-realtime.md)\n- [OpenAI Realtime API vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/openai-realtime-vs-pipecat-phonellm.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "fone.me vs OpenAI Realtime API", "url": "" } ], "description": "OpenAI Realtime scores 71.7 (BB) 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", "OpenAI Realtime API BB 71.7", "scores" ], "h1": "fone.me vs OpenAI Realtime API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/fone-me-vs-openai-realtime", "published": "2026-10-01", "section": "tools", "title": "fone.me vs OpenAI Realtime for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime" }, "tokens": { "markdown": 7250, "slim": 4580 }, "version": 1 }