> ## Documentation Index
> Fetch the complete documentation index at: https://octolane.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Octolane for AI agents

> Discover the docs, connect through MCP or REST, and work with CRM records and company knowledge using the connected user's permissions.

Octolane is a self-driving AI CRM built for agents and humans. Its own agents maintain records, find deals, and prepare follow-ups. External agents can read and update CRM data and query the company brain through MCP. Every plan includes MCP, the REST API, and webhooks; feature and usage limits still depend on the [plan](https://octolane.com/docs/account/plans-pricing.md).

## Discover the right source

| Resource | Use it for |
| - | - |
| [Product summary](https://www.octolane.com/llms.txt) | Product positioning, capabilities, pricing links, and agent entry points |
| [Docs index](https://www.octolane.com/docs/llms.txt) | Find individual documentation pages |
| [Full docs text](https://www.octolane.com/docs/llms-full.txt) | Read the documentation as one text resource |
| [Pricing Markdown](https://www.octolane.com/pricing.md) | Current prices, seats, limits, and feature entitlements |
| [FAQ Markdown](https://www.octolane.com/faq.md) | Current product and buyer questions |
| [OpenAPI schema](https://www.octolane.com/openapi.json) | REST operations, inputs, responses, and authentication |
| [API catalog](https://www.octolane.com/.well-known/api-catalog) | Discover API descriptions and service documentation |
| [MCP discovery](https://www.octolane.com/.well-known/mcp.json) | MCP endpoint, transport, and authentication metadata |

The website's [content index](https://www.octolane.com/llms-full.txt) lists published articles and case studies. It is separate from the full documentation text under `/docs/llms-full.txt`. Individual docs pages also have Markdown versions; for example, [MCP authentication](https://www.octolane.com/docs/mcp/authentication.md).

## Connect to a workspace

A person [signs up](https://www.octolane.com/auth/sign-up), starts the 7-day Founder trial or arranges a demo-led plan, and connects Gmail and Google Calendar. An agent uses the workspace after the person authorizes access.

* **MCP:** connect to `https://mcp.octolane.com/mcp` over Streamable HTTP. Use OAuth, or an API key in `Authorization: Bearer YOUR_OCTOLANE_API_KEY` if your client supports custom headers. Follow the [MCP quickstart](https://octolane.com/docs/mcp/quickstart.md).
* **REST:** use `https://api.octolane.com` with the paths in the OpenAPI schema and an API key in `x-api-key`. Follow the [API reference](https://octolane.com/docs/api-reference/introduction.md).
* **API keys:** create a personal key in [Settings → API keys](https://www.octolane.com/settings/api-keys). Requests use its creator's current workspace access.

## Work with the available tools

1. Discover the current MCP tools and input schemas with `tools/list`. Use the [tools reference](https://octolane.com/docs/mcp/tools-reference.md) to understand common workflows; the connected server determines which tools are available.
2. Check the connected identity and workspace before working with customer records. Use `get_current_user` when available.
3. Search for existing records, then reuse the IDs returned by the service. Resolve ambiguous names before changing records.
4. Read the current record before an update. Keep writes within the person's request and workspace permissions. API and MCP writes can change records directly; do not assume they all enter the in-app approval queue.
5. Follow response pagination and use field selection where supported. Verify the resulting record after a write and report failures or partial results accurately.

For REST, use each operation's schema rather than translating MCP tool arguments directly: identifiers, dates, and record-resolution behavior can differ. See [filters](https://octolane.com/docs/api-reference/v2/filters.md) and [pagination](https://octolane.com/docs/api-reference/v2/pagination.md).

## Query the company brain

The company brain is called **Knowledge** in Octolane. It is available on every plan and can be queried by people and agents through MCP. Discover the schemas for `memory_list` and `memory_get`, then list and read the applicable shared and personal knowledge. Pending suggestions are excluded by default; distinguish them from approved knowledge if explicitly requested.

Example request: “What objections come up in our sales conversations, and which responses have worked? Cite the available knowledge and distinguish it from your own suggestions.”

See [Company brain](https://octolane.com/docs/ai/company-brain.md) for review and version-history behavior.

## Limits and unavailable capabilities

Unlimited AI does not mean unlimited enrichment or automation runs. Check [usage limits](https://octolane.com/docs/account/plans-pricing.md#usage-limits). Honor rate-limit responses and retry guidance. If a capability or schema is unavailable, report that limitation rather than inventing an API route, tool name, or successful result.

Webhooks are included on all plans. For event types, payloads, delivery guarantees, and signing configuration not covered by the published schema, contact [help@octolane.com](mailto:help@octolane.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.