Lev
Lev is an AI platform and product system for commercial real estate (CRE) teams, used by sponsors, financing brokers, investment-sales brokers, lenders, capital-markets teams, and enterprise operators. The platform is organized in four layers: CRE apps (CRM, pipeline, vault/data rooms, checklists, memos, commissions), source-backed AI agents (Lev Agent, Lev Memo, Lender Search, Lev Match, Lev Index), CRE data (lender, market, contact, property, and recent-terms data), and a developer platform. That platform layer is the API Evangelist interest: a versioned REST API at api.lev.com covering deals, documents and vaults, checklists, contacts, companies, the lender directory, term sheets, placements, pipelines, market data, account, and billing; a hosted remote MCP server at mcp.lev.com with roughly 60 tools and OAuth 2.1 discovery; and a first-party Python CLI. The API publishes an OpenAPI 3.1 description, scoped API keys, cursor pagination, Idempotency-Key support on writes, request-id correlation, and a documented error-type and rate-limit contract.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Lev the way a machine reads it — 57 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 — Lev scores 67.9/100 (exemplar), with a separate agent-readiness read of 55/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. 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
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Lev'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/lev/"
title="Lev on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lev.svg"
alt="Lev Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/lev/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lev/"
title="Lev on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lev/card.svg"
alt="Lev 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 Lev
Each block below is one kind of artifact we hold for Lev. 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 16
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.
Lev Account & Team API
The Account & Team API from Lev — 4 operation(s) for account & team.
Lev API Keys API
The API Keys API from Lev — 2 operation(s) for api keys.
Lev Billing API
The Billing API from Lev — 2 operation(s) for billing.
Lev Companies API
The Companies API from Lev — 4 operation(s) for companies.
Lev Contacts API
The Contacts API from Lev — 5 operation(s) for contacts.
Lev Deal Financials API
The Deal Financials API from Lev — 1 operation(s) for deal financials.
Lev Deal Properties API
The Deal Properties API from Lev — 1 operation(s) for deal properties.
Lev Deal Team API
The Deal Team API from Lev — 1 operation(s) for deal team.
Lev Deals API
The Deals API from Lev — 21 operation(s) for deals.
Lev Lender Directory API
The Lender Directory API from Lev — 3 operation(s) for lender directory.
Lev Lev API Documentation API
The Lev API Documentation API from Lev — 1 operation(s) for lev api documentation.
Lev Market Data API
The Market Data API from Lev — 2 operation(s) for market data.
Lev Pipelines API
The Pipelines API from Lev — 3 operation(s) for pipelines.
Lev Placements API
The Placements API from Lev — 4 operation(s) for placements.
Lev Quickstart API
The Quickstart API from Lev — 1 operation(s) for quickstart.
Lev Term Sheets API
The Term Sheets API from Lev — 2 operation(s) for term sheets.
Scroll within the panel for all 16 ·
Postman Collections 16
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Lev Account & Team API
POSTMANLev Account & Team Deals API
POSTMANScroll within the panel for all 16 ·
Open Collections 17
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 COLLECTIONLev Account & Team API
OPEN COLLECTIONLev Account & Team API Keys API
OPEN COLLECTIONLev Account & Team Billing API
OPEN COLLECTIONLev Account & Team Companies API
OPEN COLLECTIONLev Account & Team Contacts API
OPEN COLLECTIONLev Account & Team Deal Financials API
OPEN COLLECTIONLev Account & Team Deal Properties API
OPEN COLLECTIONLev Account & Team Deal Team API
OPEN COLLECTIONLev Account & Team Deals API
OPEN COLLECTIONLev Account & Team Lender Directory API
OPEN COLLECTIONLev Account & Team Lev API Documentation API
OPEN COLLECTIONLev Account & Team Market Data API
OPEN COLLECTIONLev Account & Team Pipelines API
OPEN COLLECTIONLev Account & Team Placements API
OPEN COLLECTIONLev Account & Team Quickstart API
OPEN COLLECTIONLev Account & Team Term Sheets API
OPEN COLLECTIONScroll within the panel for all 17 ·
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.
Lev
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Lev Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Lev Rate Limits
RATE LIMITSSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Lev — 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 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lev · machine-readable index on apis.io
This is an independent, third-party profile of Lev, 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.