Avoma
Avoma is an AI-powered meeting assistant platform that automates note‑taking, scheduling, and coaching for sales and revenue teams. It records and transcribes meetings in real time, generates structured summaries, pushes data to CRMs, and provides AI‑driven sales coaching and guidance. The platform also offers lead routing, meeting reminders, and revenue intelligence tools to help organizations improve productivity and close deals faster.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Avoma the way a machine reads it — 25 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 — Avoma scores 55.9/100 (strong), with a separate agent-readiness read of 42/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 publishes developer documentation but serves no machine-readable contract from it
The documentation is public — a person can read it, but a machine cannot. This one is Avoma's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.
What we probed
https://www.nasdaqprivatemarket.com/→ HTTP 200
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-03 · rubric v0.23.0
Put this on your own site. The badge is drawn live from Avoma'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/avoma/"
title="Avoma on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/avoma.svg"
alt="Avoma Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/avoma/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/avoma/"
title="Avoma on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/avoma/card.svg"
alt="Avoma 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 Avoma
Each block below is one kind of artifact we hold for Avoma. 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 18
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.
Avoma Calls API
The Calls API from Avoma — 2 operation(s) for calls.
Avoma Custom Category API
**Deprecated**: The "Custom Category" feature is deprecated and will be removed in future versions. We recommend using the "Smart Category" feature instead.
Avoma Engagement Analytics API
The Engagement Analytics API from Avoma — 4 operation(s) for engagement analytics.
Avoma Meeting Outcomes API
The Meeting Outcomes API from Avoma — 2 operation(s) for meeting outcomes.
Avoma Meeting Types API
The Meeting Types API from Avoma — 2 operation(s) for meeting types.
Avoma Meetings API
Meetings are the foundation and starting point of the flow in Avoma. You can fetch recordings , transcriptions , ai notes , sentiments and coaching once the meeting is recorded ...
Avoma Meetings Sentiments API
Avoma's meeting sentiment feature is a powerful tool designed to provide end users with a deeper understanding of the emotional tone and dynamics within their meetings. By analy...
Avoma Notes API
Avoma's AI takes notes so that you can focus on engaging in the conversation. These notes are intelligently categorised using Avoma's Smart Categories feature, which employs nat...
Avoma Recording API
Recordings contain Audio and Video information for a completed meeting. Once recording is available you should be able to download the same using the pre-signed url. The url wil...
Avoma Revenue Intelligence [Beta] API
The Revenue Intelligence [Beta] API from Avoma — 2 operation(s) for revenue intelligence [beta].
Avoma Scorecard Evaluations API
The Scorecard Evaluations API from Avoma — 1 operation(s) for scorecard evaluations.
Avoma Scorecards API
The Scorecards API from Avoma — 2 operation(s) for scorecards.
Avoma Smart Category API
Smart Categories can help organize your meeting notes into logical groupings, making it effortless to navigate and extract specific information from large volumes of conversatio...
Avoma Snippets API
The Snippets API from Avoma — 1 operation(s) for snippets.
Avoma Templates API
`Templates` help in extraction of AI-generated notes based on mentioned categories. A template will be automatically inserted into the meeting notes page, if the `meeting type` ...
Avoma Transcriptions API
Transcription is generated for meeting's recording. This is available once the meeting recording is processed. Availability of transcription can be verified using `transcript_re...
Avoma Users API
The Users API from Avoma — 2 operation(s) for users.
Avoma Webhooks API
**Webhooks** Avoma Webhooks notify users about the successful occurrence of events within the Avoma application. Instead of polling or calling APIs to detect events, Avoma sends...
Scroll within the panel for all 18 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Avoma Plans Pricing
PLANSSpectral 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.
Avoma API Rules
SPECTRALSecurity Posture 4
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 Avoma — 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 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Access & Security 6
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
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/avoma · machine-readable index on apis.io
This is an independent, third-party profile of Avoma, 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.