Skip to content
Levr API Documentation
Download OpenAPI specOpenAPI

Hand off to an AI agent

Copy instructions to your AI agent

Copy this guide into your AI agent. It links to the current REST API and MCP documentation.

You are helping someone integrate their system with Levr. Use Levr's published documentation and machine-readable contracts as the source of truth. Do not invent endpoints, fields, or MCP tools.

  1. Start with the Levr API documentation to choose between a server-to-server REST integration and a user-authorized MCP connection.
  2. For REST, read the Markdown REST API guide, choose the user’s task, then fetch only the relevant resource guide and operation Markdown. Resource indexes include task guidance. For funding recommendations, start with the Matchmaking guide. Use the OpenAPI specification for exact paths, authentication, parameters, and envelope schemas.
  3. For REST client intake, Deal applications, or project Criteria, fetch that resource's contract_url. Its Application Contract is the authority for the current questions, stable keys, repeatable groups, file-transfer steps, accepted answer shapes, conditional visibility, supported operation URLs, and integration instructions. Repeatable fields require the returned item_id. File bytes use the expiring upload_url and multipart field named file; they never belong in JSON. Do not substitute a static example or the latest application definition.
  4. For an AI client acting with a signed-in user's access, read the MCP connection instructions in Markdown first, then the Model Context Protocol guide if needed. Let the connected MCP server expose its current tools and input contracts; do not infer tools from the REST API. Read the relevant MCP resource guide and follow the discovered tool’s revision, file-transfer, and confirmation requirements.
  5. Use URLs from the record handoff when supplied; otherwise use this documentation environment. Keep API keys and file-transfer credentials out of browser code, logs, prompts, and source control.
  6. Before implementing a write, verify authentication, required inputs, idempotency, error responses, and retry guidance in the current contract. If an operation is not documented, do not assume it exists.

Early access

Request an integration

Tell us what your integration needs to do. Add an email if you want a reply.

API v1

REST API reference

Choose a resource to find its available operations, parameters, requests, and responses.

Base URL
https://api.levr.ai/v1/
Authentication
Bearer Portal API key
Format
OpenAPI 3.1

Read as Markdown

Resources

14 operationsBusinessesAdd businesses through a Lead source, complete their intake applications, and follow their progress.View endpoints 23 operationsClient intake applicationsComplete a business's intake application, check what is missing, and submit it.View endpoints 33 operationsProjectsA project is a funding goal for a business. Complete its Criteria, find matches, and create Deals.View endpoints 10 operationsDealsFollow a business's funding request to a recipient, manage its stage, and open its application.View endpoints 31 operationsDeal applicationsComplete a Deal's application, share it for review or editing, and submit it when ready.View endpoints 5 operationsPeopleBrowse the available operations for this resource.View endpoints 2 operationsLendersBrowse the available operations for this resource.View endpoints 2 operationsBusiness pipelinesBrowse the available operations for this resource.View endpoints 1 operationConnectionCheck which Portal your API key connects to and which resources it can read or update.View endpoints 2 operationsDeal pipelinesBrowse the available operations for this resource.View endpoints 1 operationDeal recipientsBrowse the available operations for this resource.View endpoints 2 operationsProject stagesBrowse the available operations for this resource.View endpoints 21 eventsWebhooksReceive signed events when something changes in Levr.View webhooks