How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Lemma website screenshot

Lemma

Lemma (uselemma.ai, Forge AI Labs, Inc., Y Combinator Fall 2025) is a production monitoring and observability platform for AI agents. Teams instrument agents with the Lemma tracing SDKs (TypeScript and Python) so every agent execution becomes one trace with LLM generations, tool calls, and app-logic spans as children; Lemma then surfaces silent semantic failures, groups recurring issues with root-cause analysis, sends signed incident webhooks, and exposes the whole surface — projects, traces, issues, and learn-agent artifacts — through the Lemma Platform API and an official remote MCP server so coding agents can pull the exact runs and errors they need and fix issues in place.

agent ready

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.

Kin Score

API Evangelist profiles Lemma the way a machine reads it — 14 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 — Lemma scores 43.2/100 (developing), with a separate agent-readiness read of 38/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.

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 Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Lemma Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Lemma'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/uselemma/"
   title="Lemma on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/uselemma.svg"
       alt="Lemma Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Lemma

Each block below is one kind of artifact we hold for Lemma. 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 4

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.

Lemma Artifacts API

The Artifacts API from Lemma — 6 operation(s) for artifacts.

Lemma Issues API

The Issues API from Lemma — 8 operation(s) for issues.

Lemma Projects API

The Projects API from Lemma — 6 operation(s) for projects.

Lemma Traces API

The Traces API from Lemma — 17 operation(s) for traces.

Open Collections 5

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).

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

Lemma MCP Server

Lemma operates an official remote MCP server at https://api.uselemma.ai/mcp (Streamable HTTP transport), authenticated with a project API key sent as an Authorization Bearer hea...

MCP SERVER

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security 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.

Uselemma Authentication

http · 1 scheme

SECURITY

Uselemma Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Uselemma Trust Center

trust center published

SECURITY

Resources

Every other property we hold for Lemma — 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 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Operate 3

Status, limits, changes, and where to get help

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/uselemma · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Lemma, 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.