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.

Partnerships

Read as Markdown

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

Available tools

provider_relationships.getGet partnership detailsprovider_relationships.create_connection_requestComplete partnership connection requestprovider_relationships.create_invitationComplete partnership invitationprovider_relationships.review_acceptanceReview partnership acceptanceprovider_relationships.review_connection_requestReview partnership connection requestprovider_relationships.review_invitationReview partnership invitationprovider_relationships.review_invitation_resendReview partnership invitation resendprovider_relationships.review_lifecycleReview partnership lifecycle changeprovider_relationships.review_rejectionReview partnership rejectionprovider_relationships.review_withdrawalReview partnership withdrawalprovider_relationships.set_lifecycleChange partnership lifecycleprovider_relationships.acceptComplete partnership acceptanceprovider_relationships.resend_invitationComplete partnership invitation resendprovider_relationships.rejectComplete partnership rejectionprovider_relationships.withdrawComplete partnership withdrawalprovider_relationships.upsert_noteCreate or edit private relationship noteprovider_relationships.list_invitations_and_requestsList partnership invitations and requestsprovider_relationships.updateUpdate partnership details