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 status

Read as Markdown · All MCP tools

client_intake_applications.review_status_change

Review one shared application lifecycle change without writing. Read businesses.get for client_intake_application.id. Use its application status, distinct from internal board placement. Returns current and target status, can_execute and blockers, stage effects, eligible optional communication recipients, automatic effects and a ten-minute state-bound review token. Submission uses the separate submit tool.

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
application_idClient Intake Application ID (ciappl_): copy client_intake_application.id from businesses.get.Yes
destination_stage_idOptional stage for your provider, from stage configuration. Must map to the target status and belong to the current pipeline. Omit to respect existing status-to-stage synchronization preferences.No
provider_slugProvider slug returned by providers.list; reuse a known value. Named slugs are valid.Yes
target_statuspre_submitted: Reopen intake; retains historical submission timestamp; action_required: Request further intake work; completed: Intake completed; withdrawn: Intake withdrawn; closed_not_proceeding: Close without proceedingYes
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 Intake applications guide.