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.

REST API reference

Projects

A project is a funding goal for a business. Complete its Criteria, find matches, and create Deals.

Read as Markdown

Work on a funding goal

A project records a business’s funding goal. Start by creating or reading the project, then complete its Criteria and find recommendations in the Matchmaking guide.

Available operations

GETList Projects/projects/POSTCreate a Project/projects/GETRetrieve a Project/projects/{project_id}/PATCHUpdate Project facts/projects/{project_id}/PATCHMove one Project to a workflow stage/projects/{project_id}/stage/

Matchmaking

GETRetrieve the matchmaking application contract/projects/{project_id}/matchmaking-application/contract/GETRead shared matching criteria/projects/{project_id}/matchmaking-request/PATCHEdit shared matching criteria/projects/{project_id}/matchmaking-request/GETList shared matchmaking application answers/projects/{project_id}/matchmaking-application/answers/PATCHUpdate shared matchmaking application answers/projects/{project_id}/matchmaking-application/answers/GETList repeatable answer items/projects/{project_id}/matchmaking-application/answers/repeatable-items/POSTCreate a repeatable answer item/projects/{project_id}/matchmaking-application/answers/repeatable-items/PATCHUpdate a repeatable answer item/projects/{project_id}/matchmaking-application/answers/repeatable-items/DELETEDelete a repeatable answer item/projects/{project_id}/matchmaking-application/answers/repeatable-items/GETList answer files/projects/{project_id}/matchmaking-application/answers/files/POSTRequest an answer-file upload/projects/{project_id}/matchmaking-application/answers/files/POSTUpload an answer file/projects/{project_id}/matchmaking-application/answers/files/{upload_id}/DELETEDelete an answer file/projects/{project_id}/matchmaking-application/answers/files/GETGet matchmaking application autofill preparation/projects/{project_id}/matchmaking-application/autofill-preparation/POSTStart matchmaking application autofill/projects/{project_id}/matchmaking-application/autofill-runs/PATCHUpdate matchmaking application autofill preparation/projects/{project_id}/matchmaking-application/autofill-preparation/POSTUpload one autofill preparation file/projects/{project_id}/matchmaking-application/autofill-preparation/files/GETPoll matchmaking application autofill/project-matchmaking-application-autofill-runs/{run_id}/GETList matchmaking application autofill suggestions/project-matchmaking-application-autofill-runs/{run_id}/suggestions/POSTAccept autofill suggestion/project-matchmaking-application-autofill-runs/{run_id}/suggestions/{suggestion_id}/accept/POSTRetry unfinished matchmaking application autofill work/project-matchmaking-application-autofill-runs/{run_id}/retry/POSTCalculate recipient matches/projects/{project_id}/matchmaking-runs/GETPoll a match calculation/project-matchmaking-runs/{run_id}/GETList persisted match results/project-matchmaking-runs/{run_id}/results/GETRead shared recipient choices/projects/{project_id}/matchmaking-selections/PATCHMerge shared recipient choices/projects/{project_id}/matchmaking-selections/POSTRetry failed recipient matches/project-matchmaking-runs/{run_id}/retry/POSTCancel unresolved recipient matching/project-matchmaking-runs/{run_id}/cancel/