Skip to main content
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.

Discover the right source

The website’s content index 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.

Connect to a workspace

A person signs 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.
  • 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.
  • API keys: create a personal key in 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 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 and pagination.

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 for review and version-history behavior.

Limits and unavailable capabilities

Unlimited AI does not mean unlimited enrichment or automation runs. Check 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.