LawVu
LawVu is a New Zealand-founded legal technology company whose LegalOS is a connected workspace for corporate in-house legal teams, bringing matter management, contract lifecycle management, legal request intake, spend management and e-billing, document management, reporting and embedded AI into a single platform. LawVu publishes a public REST developer platform — a v2 API covering matters, contracts, fields and files, and a set of legacy v1 product APIs covering accounts, users, organisations, email threads, invoices and webhook subscriptions — secured with OAuth 2.0 authorization code, documented with OpenAPI 3.0.1, returning RFC 9457 problem details, and filtered and paged with a subset of OData. It also ships a first-party MCP server for connecting AI assistants to the LegalOS, a Microsoft Power Platform connector, and a Workato connector. LawVu is backed by Insight Partners.
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 LawVu the way a machine reads it — 33 machine-readable artifacts across 26 APIs, 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 — LawVu scores 59.3/100 (developing), with a separate agent-readiness read of 78/100 (agent native). 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 LawVu
Each block below is one kind of artifact we hold for LawVu. 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 26
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.
LawVu Auth API
The Auth API from LawVu — 1 operation(s) for auth.
LawVu ContractFiles API
The ContractFiles API from LawVu — 1 operation(s) for contractfiles.
LawVu ContractKeyDate API
The ContractKeyDate API from LawVu — 1 operation(s) for contractkeydate.
LawVu Contracts API
The Contracts API from LawVu — 12 operation(s) for contracts.
LawVu ContractStatusMessage API
The ContractStatusMessage API from LawVu — 1 operation(s) for contractstatusmessage.
LawVu ContractTemplates API
The ContractTemplates API from LawVu — 2 operation(s) for contracttemplates.
LawVu ContractUser API
The ContractUser API from LawVu — 1 operation(s) for contractuser.
LawVu Emails API
The Emails API from LawVu — 5 operation(s) for emails.
LawVu Features API
The Features API from LawVu — 1 operation(s) for features.
LawVu Fields API
The Fields API from LawVu — 5 operation(s) for fields.
LawVu Files API
The Files API from LawVu — 9 operation(s) for files.
LawVu Folders API
The Folders API from LawVu — 2 operation(s) for folders.
LawVu Invoices API
The Invoices API from LawVu — 3 operation(s) for invoices.
LawVu LookupFields API
The LookupFields API from LawVu — 4 operation(s) for lookupfields.
LawVu MatterCategories API
The MatterCategories API from LawVu — 2 operation(s) for mattercategories.
LawVu MatterFiles API
The MatterFiles API from LawVu — 1 operation(s) for matterfiles.
LawVu Matters API
The Matters API from LawVu — 11 operation(s) for matters.
LawVu MattersInvoices API
The MattersInvoices API from LawVu — 1 operation(s) for mattersinvoices.
LawVu MatterStatusMessage API
The MatterStatusMessage API from LawVu — 1 operation(s) for matterstatusmessage.
LawVu MatterTasks API
The MatterTasks API from LawVu — 1 operation(s) for mattertasks.
LawVu MatterTaskTemplates API
The MatterTaskTemplates API from LawVu — 2 operation(s) for mattertasktemplates.
LawVu Organisations API
The Organisations API from LawVu — 5 operation(s) for organisations.
LawVu Recents API
The Recents API from LawVu — 1 operation(s) for recents.
LawVu Teams API
The Teams API from LawVu — 1 operation(s) for teams.
LawVu Users API
The Users API from LawVu — 2 operation(s) for users.
LawVu WebhookSubscriptions API
The WebhookSubscriptions API from LawVu — 2 operation(s) for webhooksubscriptions.
Scroll within the panel for all 26 ·
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.
lawvu-mcp.yml
MCP SERVEREvent 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.
Lawvu Webhooks
ASYNCAPISecurity 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 LawVu — 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 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
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 4
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
← All providers · Data indexed from github.com/api-evangelist/lawvu · machine-readable index on apis.io