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.

Save reviewed application form draft

Read as Markdown

All MCP tools

matchmaking_application_editor.replace

Replace the complete draft using the exact config and state tokens from validate_config. Preserve question identities; omitted questions are removals. Save the validated draft directly without requesting approval. Unsupported conversions remain blocked. This stages changes only and does not change submitted answers or notify participants. Publishing requires its own publication review and consent, including notifications. For stale state, read and validate again; for an uncertain outcome retry identical arguments with the same client_request_id. Use review_undo or review_reset to recover draft changes. This toolset requires a specific grant and is not assigned by default; request access through Support. Saved drafts and published question changes can mark earlier matching results as out of date. These tools do not rerun matching, contact recipients or create Deals.

Operation
write
OAuth scopes
mcp

Availability depends on your assigned tools. Scopes do not grant record access. Read the tool description and current resource before changing it; follow the required revision and idempotency fields below.

Inputs

Name and descriptionRequired
allow_destructive_changesLegacy compatibility field. Draft saves do not delete stored answers; publishing requires its own destructive opt-in and approval.No
client_request_idUnique request identity. Retry an uncertain result with identical arguments and the same key.Yes
configSee the input schema for constraints.Yes
expected_draft_revisionCopy draft_revision from the same current action review.Yes
expected_live_revisionCopy live_revision from the current action review.Yes
provider_slugProvider workspace returned by providers.list.Yes
review_digestCopy review_digest from validate_config for this exact config.Yes
user_confirmedLegacy compatibility field; draft saves do not require confirmation.No
workspace_slugMatching workspace from projects.list or projects.get; use workspace_slug, not the Project id.Yes
View exact input schema

Result

Check the structured result for success or an error before continuing. Read the affected record to confirm your change.

View exact output schema

For this workflow’s steps and prerequisites, read the Matchmaking criteria editor guide.