Anam
Anam builds real-time, interactive AI avatars — photorealistic conversational personas that hold face-to-face video conversations for customer support, sales, tutoring, medical and training use cases. Its CARA avatar engine streams over WebRTC with sub-200ms latency and 70+ languages, fronted by a REST API (api.anam.ai) for managing personas, avatars, voices, LLM routing, knowledge (RAG) groups, function-calling tools, session tokens, share links and session analytics. Developers integrate via first-party JavaScript and Python SDKs, a Kotlin Multiplatform SDK, and a Pipecat plugin, or embed a no-code widget. Anam is a Redpoint Ventures portfolio company.
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 Anam the way a machine reads it — 24 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 — Anam scores 51.6/100 (developing), with a separate agent-readiness read of 24/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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.
Put this on your own site. The badge is drawn live from Anam'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/anam/"
title="Anam on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/anam.svg"
alt="Anam Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/anam/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/anam/"
title="Anam on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/anam/card.svg"
alt="Anam 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 Anam
Each block below is one kind of artifact we hold for Anam. 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 9
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.
Anam Auth API
The Auth API from Anam — 1 operation(s) for auth.
Anam Avatars API
The Avatars API from Anam — 2 operation(s) for avatars.
Anam Knowledge API
The Knowledge API from Anam — 5 operation(s) for knowledge.
Anam Llms API
The Llms API from Anam — 2 operation(s) for llms.
Anam Personas API
The Personas API from Anam — 2 operation(s) for personas.
Anam Sessions API
The Sessions API from Anam — 2 operation(s) for sessions.
Anam Share Links API
The Share Links API from Anam — 2 operation(s) for share links.
Anam Tools API
The Tools API from Anam — 2 operation(s) for tools.
Anam Voices API
The Voices API from Anam — 2 operation(s) for voices.
Scroll within the panel for all 9 ·
Open Collections 10
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAnam AI Auth API
OPEN COLLECTIONAnam AI Auth Avatars API
OPEN COLLECTIONAnam AI Auth Knowledge API
OPEN COLLECTIONAnam AI Auth Llms API
OPEN COLLECTIONAnam AI Auth Personas API
OPEN COLLECTIONAnam AI Auth Sessions API
OPEN COLLECTIONAnam AI Auth Share Links API
OPEN COLLECTIONAnam AI Auth Tools API
OPEN COLLECTIONAnam AI Auth Voices API
OPEN COLLECTIONScroll within the panel for all 10 ·
Security 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 Anam — 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 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/anam · machine-readable index on apis.io
This is an independent, third-party profile of Anam, 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.