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.

Get branding

Read as Markdown

All MCP tools

management_groups.get_branding

Read the current branding, domains, email sender, activation state, revision, and setup links. Read before changing settings and after correcting hostnames. DNS instructions: present every returned record from domains[].dns_records and email_sender.dns_records in an easy-to-copy format showing type, name, and target. Keep each value separately copyable. Use the exact returned names and targets; never invent records, including SPF. If the DNS editor appends the zone to Name, supply a relative name only for the confirmed DNS zone. The setup base domain is not necessarily that zone. The saved hostname must equal the returned name, never subdomain.domain.com.domain.com. Honor proxied=false as DNS only. Zone files: include the same complete records; use full record names and CNAME targets with trailing dots and preserve TXT values with valid quoting. Identify the import zone only when confirmed. Include email records when branded email is requested or configured. If requested sender records are missing, finish sender setup before presenting that DNS plan as complete. Domain-only setup does not require email. Use domain_activation for web readiness independently of email; verified DNS alone does not prove HTTPS readiness or activation. Once active, offer frontend_links.open_portal unchanged. Before reporting completed branding, verify the logo and color were applied to the requested portals. Stay within the requested task. Verified sender DNS does not prove a monitored mailbox or email delivery.

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
management_group_slugCopy management_group_slug from management_groups.list. Prefix: mgmt_.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 Branding guide.