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.

Move projects between stages

Read as Markdown · All MCP tools

projects.move_stage

Move one or up to 100 projects to the reviewed stage. Read projects.review_stage_move first. Bulk moves require two separate user confirmations: selection/count including archived records and destination; then all reviewed effects, difficult restoration of individual stages, and final approval. Set both flags true only after those replies; flags attest the conversation, not independent proof of approval. Never split a bulk request into single calls to avoid confirmation. Re-review and re-confirm if state or selection changes. Retry identical arguments with the same idempotency key. Application statuses and submissions are unchanged. Use application status-change tools for lifecycle decisions. Read the resource afterwards to verify.

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
destination_stage_idCopy the destination stage id from projects.get_stage_configuration for the selected pipeline.Yes
effects_confirmedBulk only: true after a separate second user confirmation of effects, difficult undo, and final go-ahead. Never infer either confirmation.No
idempotency_keySee the input schema for constraints.Yes
provider_slugCopy provider_slug from providers.list; named slugs are valid.Yes
record_idsCopy project_slug from projects.list. One record for a single move; 2–100 for bulk. Never infer an unreviewed selection.Yes
review_tokenSee the input schema for constraints.Yes
scope_confirmedBulk only: true after the user first confirms the exact records, count including archived records, and destination.No
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 Projects guide.