Build on Leni’s intelligent runtime platform, powered by your data and context

Sandbox, development, and production project keys call https://api.prod.ca-central-1.leni.co. The key itself determines its environment, limits, and billing behavior; there is no separate sandbox hostname.

curl -sS "https://api.prod.ca-central-1.leni.co/users/custom-analysts" \
  -H "X-Api-Key: $LENI_API_KEY"

• Sandbox keys are limited to 5 requests per minute and a monthly trial quota.
• Development keys are limited to 60 requests per minute.
• Production keys are limited to 120 requests per minute. Metered analysis uses included subscription credit first, then funded API credits when available.
• Respect Retry-After on 429 responses and use idempotent retry behavior.
• Supported attachments are limited to 50 MB per decoded file.

Start with the four-step HTTP API quickstart and use the retry and async lifecycle guide before sending production traffic.

The authenticated project-key owner is the security principal for these routes. User and organization identifiers supplied by a client cannot be used to impersonate a different account.

See the detailed HTTP API reference for request fields, response shapes, examples, limits, uploads, polling, Context, and custom analyst contracts.

The Leni intelligent runtime exposes account-scoped real-estate, financial, market-research, operating, and context tools to a compatible AI host. Each user signs in to Leni, sees the organization and requested permissions, and grants access through OAuth.

Applicable MCP limits overlap; the most restrictive one wins. Respect Retry-After after a 429 response.

See the complete MCP runtime reference for OAuth discovery, scopes, every advertised tool, structured-query bounds, rate limits, token lifecycle, and troubleshooting.

Give your organization an assistant with its own name and icon, such as Aria. Teammates can message it, ask follow-up questions, attach documents, and work with their connected sources. Leni provides the analysis infrastructure, while replies use the registered app name. The examples below use Aria as an example name; use your own app name when messaging or mentioning your assistant.

Ordinary replies do not need a powered-by footer. The assistant explains that it is powered by Leni's infrastructure when asked about its provider or when explaining accounts, connections, billing, or privacy. Leni account links, product names, and quoted source material keep their original names.

Set up the app

A Leni organization owner or administrator with an eligible paid account sets up the app. Availability depends on your organization's rollout and Slack or Microsoft app policies.

Choose Slack or Teams

• For Slack, open Slack app setup, choose branded setup, and create your Slack app from the supplied manifest. Register its credentials in Leni, configure the exact app-specific callback URLs shown, and complete installation.
• For Teams, open Teams app setup. Use a dedicated single-tenant Entra application and Azure Bot with the Teams channel enabled. Enter the app name, tenant ID, bot App ID, client secret value, and icons in Leni. Configure the returned messaging endpoint, then download the Teams package and have your Microsoft administrator approve and install it. Each branded Teams app belongs to one Microsoft tenant and one Leni organization.

Connect your teammates and sources

1. Ask each teammate to message the installed app and follow its secure connection link. Each person signs into their own eligible Leni account in the same organization and reviews the bot's trust prompt. Only link a customer-managed app whose operator you trust; that operator can receive the requests and answers handled by the bot.
2. Each person opens Connect in Leni and connects the sources they want to use, such as Outlook, SharePoint, OneDrive, Google Drive, Gmail, or Notion. Complete any required Microsoft admin consent. Installing a Slack or Teams bot does not connect those data sources automatically.
3. Start in a direct message. If your team needs shared replies, an administrator enables them and adds the app to the approved conversation. Mention the app by its registered name when asking it to help in a shared channel or Teams group chat.

Work with it like a teammate

Give the assistant a goal, name the sources, and describe the result you need. Use a private chat for these connected-app examples, with the relevant accounts connected and enabled. Ask for source links and missing information so you can review the answer.

Continue in the same conversation with requests such as "Focus on operating expenses" or "Turn this into a checklist." The email examples produce drafts in chat for you to review and send. They do not imply that the bot continuously monitors your inbox or acts without a request.

Attach files and review results

Official and branded chat apps accept PDF, Excel, Word, PowerPoint, CSV, TSV, plain text, Markdown, JSON, and common images. Attach the actual file with your request. Each request supports up to 10 files, with a maximum of 10 MiB per file and 25 MiB combined. These chat limits are separate from HTTP API upload limits. Protected, damaged, unsupported, or oversized files may need correction before the assistant can read them. Document macros are never executed.

In Teams, send incoming files in a personal chat, and upload images as files. Channel and group-chat uploads are directed to a personal chat. Teams file support requires an installed package with the file capability enabled. Accept the OneDrive consent card to receive a supported generated file. Declining the card does not upload the file.

When a task takes longer, wait for its final answer in the same conversation before retrying. If file delivery fails after an answer arrives, ask for the existing file again in the same conversation.

Check the app before inviting your team

1. Ask its name, then ask who powers it. Check the registered name and the Leni explanation.
2. Attach a small synthetic workbook and ask for a known value from a named sheet.
3. Try a private-chat request against a connected source and verify the returned source link.
4. Ask a follow-up in the same conversation and check that it uses the preceding answer.
5. In an approved shared conversation, test with Organization Context intended for that audience.

The response-naming update does not require existing users to reconnect or reinstall their app. Branded Slack apps now keep separate shared-thread histories; the first request in an older shared thread starts fresh context once. Direct-message history is preserved. If an administrator disconnects and re-registers an app, users must follow its new connection flow.

• Every MCP request is bound to the OAuth subject and that user’s active Leni organization.
• Direct portfolio queries receive server-owned organization and authorized-property filters.
• MCP clients cannot submit SQL, and direct Leni semantic-layer queries are read-only.
• One organization’s models, properties, Context, and analysis cannot be selected by another organization’s token.
• Context-file access revalidates the note under the signed-in user, organization, and model partition; clients receive a five-minute bearer link, never an S3 bucket or object key.
• Analysis uses the same included plan usage and funded API-credit spillover as Leni. When neither is available, Leni returns a usage-exhausted error.
• The account tool exposes percentage usage remaining, not the underlying dollar credit balance.

Read the developer integrations privacy notice for the data categories, connected-assistant flow, retention practices, and customer controls that apply to the HTTP API and MCP runtime.

Need help with an account or integration? Sign in to Leni and contact the team with the request ID, analysis ID, or failing endpoint. Never include a complete API key in a support message.