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.

Businesses

Read as Markdown

Choose an action to read its inputs, results, and usage guidance. Your connection determines which tools are available to you.

A business holds the client record, contacts, and intake application. Start here to organize a client; use a Project when you are working toward a funding goal.

Work with a business

  1. Find the business and read its details before making changes.
  2. Review its contacts and Lead source to understand who the client is and how they arrived.
  3. Complete its intake application, using readiness to identify missing answers. Changing the questions requires the separately granted Client intake application editor.
  4. Create or open a Project when the client is ready to seek funding.

Read the latest revision before updates. Follow collection cursors when a list has more pages.

Prepare a researched client

Use businesses.create with optional contacts, a private research note, and include_client_intake=true to include intake using the source's published template even when automatic intake is off. The flag defaults to false and never changes source settings or sends invitations.

Check client_intake_creation.status: created or existing intake is identified by client_intake_application.id; unavailable intake leaves the Business and research saved with a corrective message. Creation retries return the original outcome. After fixing setup, create intake on the same Business rather than create another Business.

Read the intake question contract and current answers, then populate supported facts with the current answers revision. Creation does not fill answers. Preserve unknowns, existing answers, and private research boundaries. Review Autofill suggestions when using larger evidence sets; sharing is a separate authorized action.

Move a pipeline stage

Use review_stage_move before move_stage. For a bulk move, select one to 100 records and a destination stage. Your AI must ask twice: first confirm the records and destination, then confirm the reviewed effects and final go-ahead. Send both acknowledgements and the current review token. Do not bypass this review through repeated single-record moves.

Moving a stage does not submit an application or change its application status.

Related resources

Intake applications

View tools and requirements

Client intake application editor

View tools and requirements

Available tools

businesses.listList businessesbusinesses.getGet business detailsbusinesses.createCreate businessbusinesses.create_pipelineCreate Business pipelinebusinesses.create_client_intakeCreate client intakebusinesses.review_client_invitationReview Business client invitationbusinesses.review_client_invitation_resendReview Business client invitation resendbusinesses.review_client_invitation_withdrawalReview Business client invitation withdrawalbusinesses.review_client_role_changeReview Business client role changebusinesses.review_pipeline_deletionReview Business pipeline deletionbusinesses.assignAssign businessbusinesses.invite_clientComplete Business client invitationbusinesses.resend_client_invitationComplete Business client invitation resendbusinesses.withdraw_client_invitationComplete Business client invitation withdrawalbusinesses.set_client_rolesComplete Business client role changebusinesses.upsert_noteCreate or edit Business notebusinesses.get_assignmentGet business assignmentbusinesses.get_client_accessGet Business client accessbusinesses.list_notesList Business notesbusinesses.list_peopleList business peoplebusinesses.list_pipelinesList Business pipelinesbusinesses.set_pinned_notePin or unpin Business notebusinesses.list_context_recordsRead business context recordsbusinesses.rename_pipelineRename Business pipelinebusinesses.set_peopleSet business peoplebusinesses.updateUpdate businessbusinesses.set_client_matchmakingChange client matchmaking accessbusinesses.get_client_matchmakingGet client matchmaking accessbusinesses.get_stage_configurationRead businesses stagesbusinesses.review_stage_moveReview move of businesses between stagesbusinesses.update_stage_configurationManage businesses stagesbusinesses.move_stageMove businesses between stagesbusinesses.review_delete_noteReview Business note deletionbusinesses.delete_noteDelete Business notebusinesses.delete_pipelineDelete Business pipeline