Level AI
Level AI (legally Ujwal Inc.) is a Mountain View, California contact center AI company founded in 2019 by Ashish Nagar, a former member of Amazon's Alexa conversational AI team. The company builds LLM-native customer experience intelligence and service automation for enterprise contact centers, with a platform spanning two product surfaces: a CX Delivery suite (AI Virtual Agent, Agent Assist, AgentGPT, Coaching, Manager Assist, Knowledge Bot, Auto Summary, Agent Screen Recording) and a CX Strategy suite (Auto-QA on 100% of interactions, Voice of the Customer theme detection, omnichannel Analytics, iCSAT, AI Workers). The proprietary full-stack AI platform includes Level AI's own ASR/Voice AI and semantic-intelligence layer trained on customer-service data, and is positioned for financial services, insurance, healthcare, retail, banking, and collections operations. Level AI exposes a public REST API for bidirectional data exchange with BI tools and existing contact center stacks, and ships native integrations across telephony, CRM, customer support, workforce management, CX management, communication, learning management, and SSO categories. The company has raised $73.1M to date (Series A 2021, Series B 2022 led by Battery Ventures, Series C $39.4M 2024 led by Adams Street Partners with Cross Creek, Brightloop, Battery Ventures and Eniac Ventures), holds a 4.7/5 rating on G2, and reports customer outcomes including 25% CSAT lift, 45% agent satisfaction improvement, and 90% time savings on manual QA. The Level AI GitHub organization (github.com/Level-AI) exists but is currently empty — there is no public OpenAPI specification, public SDK, or open-source release; the API is documented and credentialed through the customer's tenant of the Level AI platform.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Level AI the way a machine reads it — 2 machine-readable artifacts, 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 — Level AI scores 12.1/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Level AI
Each block below is one kind of artifact we hold for Level AI. 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.
Security Posture 2
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.
Resources
Every other property we hold for Level AI — 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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/level-ai · machine-readable index on apis.io