Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Legora website screenshot

Legora

Legora is a Stockholm, Sweden-based collaborative AI workspace for lawyers, founded in 2023 as Leya by Max Junestrand (CEO), Sigge Labor (CTO), and August Erséus, and rebranded to Legora in 2025. The platform delivers an agentic operating system, Legora aOS, that helps law firms and in-house legal teams execute document review, legal research, drafting, advisory work, and regulatory monitoring at scale. Core product surfaces include Agent (end-to-end execution of complex legal work), Monitors (regulatory change tracking), Lists (workflow organization), Tabular Review, Workflows, Legal Research, Portal, Editor, a Word Add-in, an Outlook Add-in, and a mobile app, with practice-area solutions spanning M&A, litigation, banking, tax, and insurance. Legora is built on Azure OpenAI Service, holds ISO 42001, ISO 27001, and SOC 2 Type II certifications, operates under GDPR with EU and US data residency options, supports BYOK encryption, and commits not to train AI models on customer data. The company closed a $550M Series D led by Accel in March 2026 at a $5.55B valuation. Legora's commercial model is enterprise SaaS sold to law firms and in-house teams; there is no public developer API, SDK, OpenAPI specification, GitHub organization, or open-source release for the Legora platform.

human only

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.

Kin Score

API Evangelist profiles Legora the way a machine reads it — 1 machine-readable artifact, 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 — Legora scores 10.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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 10.1/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 1.6 / 20
Operational Transparency 1.4 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Legora

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

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.

Legora Ai Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Legora — 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.

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Access & Security 3

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/legora-ai · machine-readable index on apis.io