Vogent API by Vogent

# Fix list: Vogent API

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/vogent, the October 2026 research run, assessed 1 October 2026. Grade D, 47.4 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Vogent API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Payments & pricing, 15 out of 100, up to 10.6 more on the total

Why it scored 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). No free tier or trial stated (0). Access starts with a human signup (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 2. Security & auth, 40 out of 100, up to 10.5 more on the total

Why it scored 40: Bearer keys created per user, which stop working when that user leaves the workspace. No scopes (20). No read-only keys or approval step (3 of 20). Agents hear callers and we found no prompt-injection guidance (5 of 15). Dial history per call, no audit log found (8 of 15). Webhooks are signed with HMAC-SHA256 in `X-Elto-Signature`. No security.txt, disclosure policy or certification found (4 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 3. Maintenance & community, 11 out of 100, up to 7.8 more on the total

Why it scored 11: The newest release we have is the web client from 23 January 2026, over 180 days ago, and there's no changelog to show API changes (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). Nothing else to assess (3 of 10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 4. Reliability, 62 out of 100, up to 7.6 more on the total

Why it scored 62: status.vogent.ai shows 90-day uptime bars per component (20). The bars show the Vogent API at 100 per cent and no incidents are posted, but there's no incident log to read behind them, so we give 25 of 30 rather than the full 30. 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 safe (7 of 15). No SLA found (0). The API is generally available (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 5. Agent ergonomics, 57 out of 100, up to 7 more on the total

Why it scored 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, 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 6. Transparency & trust, 46 out of 100, up to 4.7 more on the total

Made of editorial 20, provenance 72.

Why it scored 46: Closed platform. The terms and privacy notice name Monoid, Inc. doing business as Vogent, date from 3 March 2024 and render only with JavaScript (12 of 30). The docs give no retention period, and the privacy notice says some data may be kept after account deletion (8 of 30). No deprecation notices found, and recordings and headers still use the old Elto name (0 of 20). No subprocessor list or data location found (0 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: vogent.ai, registered 2024-08-28 (2 years) (7 of 15)
- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## 7. Schema & documentation, 73 out of 100, up to 4.4 more on the total

Why it scored 73: OpenAPI 3.0.3 file (version 1.0.11, 46 paths) and an AsyncAPI file (25). llms.txt covering about 115 pages (10). Guides explain agents, flows and IVR navigation, but say little about when not to use a feature (12 of 20). Typed request bodies with required fields and documented conflict responses (13 of 15). Examples in the guides, and error responses beyond the 409 conflict are thin (9 of 15). The spec carries a version number, but there's no public changelog (4 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- Whether the status page's 100 per cent figure reflects incidents that were never posted.
- Whether the per-minute rate includes telephony.
- Whether there's any free credit at signup.

## Weaknesses

- No public changelog and no release found since January 2026
- No published rate limits or 429 handling
- No free tier or trial stated
- Terms date from March 2024, with no retention, subprocessor or certification statements
- No MCP server

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Send an `idempotencyKey` on `POST /dials`, a reused key returns 409
- Create a call with `callAgentId`, plus `toNumber` and `fromNumberId` for phone calls
- Tell the model when to emit `<|transfer|>`, since transfers fire on that tag
- Verify webhooks with the HMAC in `X-Elto-Signature`
- Expect new dials to fail at the workspace's concurrent dial limit until calls end

## What the review panel asked for

- publish the concurrent dial limit
- keep an incident log
- a published retention period
- scoped keys

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.