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.

Review application template attachment change

Read as Markdown

All MCP tools

matchmaking_application_editor.review_attachment_change

Review setting or removing the PDF template attached to a file question in this Portal's draft. Read get_config and open the draft first. For set, hash the exact PDF and provide filename, size_bytes and content_sha256; for remove, omit those fields. Signature blocks are unsupported. This does not stage bytes, publish, notify participants, or change submitted answer files. Review the returned effects before prepare_attachment_upload, set_attachment, or remove_attachment with this digest and revisions. 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
read
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
actionSet requires filename, content_sha256, and size_bytes. Remove forbids these file fields.Yes
content_sha256SHA-256 digest of the exact proposed PDF bytes.No
filenamePDF filename only, without a directory path.No
provider_slugProvider workspace returned by providers.list.Yes
size_bytesSee the input schema for constraints.No
stable_block_idExact stable_block_id of a file block from get_config; signatures are unsupported.Yes
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.

View exact output schema

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