fone.me vs Vogent API

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.

Vogent API 57

status.vogent.ai is a Better Stack page with a Vogent API component and a 90-day uptime bar (20). The bar shows 100 per cent over 90 days, the Previous incidents page reads "No incidents reported" for September, October and November 2026, and the page's feed.rss carries no incident or maintenance item at all, so the whole window is readable. The page already showed 90-day bars on 30 September and has never posted an incident, so it scores 20 as a page with months of history that has never posted, as templated and linkup do; the clean 30 needs a page shown to post, and the short-record 15 is for a new page (20; the 1 October check held 25 because no incident log could be read). The docs mention a per-workspace concurrent dial limit, raised on request, with no numbers (0). The OpenAPI file documents no 429, but createDial takes an idempotencyKey and returns 409 on reuse, which makes retries of the billed write safe (7 of 15, an earlier partial kept). No SLA found (0). The API is generally available (10). 20+20+0+7+0+10 = 57.

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.

Vogent API 73

OpenAPI 3.0.3 file (version 1.0.11, 42 paths, 65 operations) and an AsyncAPI file, both linked from llms.txt (25). llms.txt with 117 page links and Markdown pages (10). Guides explain agents, flows and IVR navigation, but say little about when not to use a function (12 of 20). Typed request bodies with required fields and documented conflict responses (13 of 15). Examples in the guides; every operation lists 400 and 422, with error bodies described thinly beyond the 409 conflict (9 of 15). The spec carries a version number, but there's no public changelog (4 of 15). 25+10+12+13+9+4 = 73.

fone.me 50

No x402, MPP or L402 on any page read (0). Premium is $9.99 a month on llms.txt and the Smith.ai comparison page, with no minute allowance or per-call price (10 of 20). The MCP server, search API and A2A endpoints are free with no account, and the agent, first link and chat button are free for owners; no page mentions a card for any of these (20). An outside agent needs no sign-up, key or payment to find and message an agent (20). 0+10+20+20 = 50.

Vogent API 15

No x402, MPP or L402 (0 of 40). Per-second rates are public, $0.09 a minute on standard voices and $0.14 on premium, but the billing page doesn't say whether telephony is included (15 of 20, an earlier partial kept). No free tier or trial stated (0). Access starts with a human signup (0). 0+15+0+0 = 15.

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.

Vogent API 57

Closed platform. Per the 30 September check, the terms and privacy notice name Monoid, Inc. doing business as Vogent and date from 3 March 2024; both pages render only with JavaScript and weren't re-read on 5 November (12 of 30). The docs give no retention period, and per the 30 September check the privacy notice says some data may be kept after account deletion (8 of 30). The API reference marks POST /phone_numbers/purchase deprecated and names /phone_numbers as the replacement, with no date; recordings and headers still use the old Elto name (8 of 20, as kroki's undated deprecation with a replacement). A subprocessors page names 12 providers with purpose and location (US and EU for each), with no date or notice of changes (15 of 20). 12+8+8+15 = 43.

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.

Vogent API 57

Scored as an API, since there's no MCP server. Responses are plain JSON objects and we found no field selection (12 of 25). Some list endpoints page by cursor, and filters are limited (12 of 20). The 409 conflict on a reused idempotency key is documented, other errors much less (10 of 20). Dial creation is idempotent with idempotencyKey (15 of 20). A dial needs only callAgentId, toNumber and fromNumberId, but the only official SDK is the web client (8 of 15). 12+12+10+15+8 = 57.

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.

Vogent API 11

The newest release found is web client v0.1.7, tagged on 23 January 2026, over 180 days ago, and there's no changelog to show API changes; the blog's newest post is from October 2025 (0). No releases found in the last 90 days (0). No public changelog or issue tracker, and we didn't test support (3 of 15). One official SDK, the web client (5 of 15). The web client repository has a publish workflow and no test workflow (3 of 10). 0+0+3+5+3 = 11.