Zelto
Zelto AI provides production QA for voice AI agents, offering analytics and monitoring of conversational pipelines. It ingests calls, transcripts, messages, and LLM traces to surface failures, rank findings, and draft fixes, helping teams improve conversion and reliability at scale. The platform integrates with major voice AI services and offers a dashboard for debugging, testing, and continuous improvement.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Zelto the way a machine reads it — 23 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Zelto scores 53.8/100 (developing), with a separate agent-readiness read of 43/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
the company serves an API surface but requires credentials before any description of it can be read
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Zelto's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://docs.zelto.ai/mcp→ HTTPhttps://api.zelto.ai/openapi.json→ HTTPhttps://dashboard.zelto.ai/openapi.json→ HTTPhttps://api.zelto.ai/mcp→ HTTP 401https://dashboard.zelto.ai/mcp→ HTTP 401https://trust.zelto.ai/mcp→ HTTP 403
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Zelto's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zelto/"
title="Zelto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zelto.svg"
alt="Zelto Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/zelto/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zelto/"
title="Zelto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zelto/card.svg"
alt="Zelto Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Zelto
Each block below is one kind of artifact we hold for Zelto. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Zelto Action checks API
The Action checks API from Zelto — 1 operation(s) for action checks.
Zelto Agents API
Voice and chat bots normalised through Zelto's ingestion pipeline.
Zelto Buckets API
Reviewer routing — group conversations for batched review.
Zelto Companies API
Clients or brands your agents work for, and their logos.
Zelto Conversations API
Calls, chats, and voicemails — plus their transcripts and recordings.
Zelto Customer Metrics API
Customer-provided evaluations attached to a call (requires metrics enabled).
Zelto Experiments API
Prospective measurement of two externally routed prompt versions across independent monitor outcomes.
Zelto Findings API
Structured issues discovered during analysis, with optional conversation attachments and comments.
Zelto Organizations API
Headless org provisioning. Requires an admin/service API key (not a read-only org-scoped customer key).
Zelto Reports API
The Reports API from Zelto — 3 operation(s) for reports.
Zelto Reviews API
Human review state for conversations.
Scroll within the panel for all 11 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Zelto Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Zelto API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ActionCheckInput
JSON SCHEMACallIngest
JSON SCHEMACustomerMetric
JSON SCHEMACustomerTransferReport
JSON SCHEMAExperimentCreate
JSON SCHEMAFinding
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Zelto — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 6
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zelto · machine-readable index on apis.io
This is an independent, third-party profile of Zelto, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.