Polylane Developers

Everything you need to build against Polylane: the API, the MCP server, the CLI, the SDK, and how to authenticate. Agents: this page is also available as markdown at /developers.md.

Polylane quickstart

  1. Get access — Polylane is pre-launch; join the waitlist on the homepage (or POST https://polylane.com/api/auth/email).
  2. Sign in — once invited, sign in at console.polylane.com and connect a cloud account or repository.
  3. Mint an API key — create a key (sk_...) in the console settings.
  4. First request:
    curl https://api.polylane.com/v1/auth/whoami -H "x-api-key: sk_..."
  5. Connect an agent — point any MCP client at https://mcp.polylane.com/mcp. OAuth clients register themselves at https://mcp.polylane.com/register.

Polylane API

Polylane MCP servers

  • Product (OAuth 2.0 or API key): https://mcp.polylane.com/mcp — tools search, execute, searchTools, runTool, runCode. Server card.
  • Docs (no auth): https://docs.polylane.com/mcp — list and read every documentation page.

Polylane CLI

Built to be driven by coding agents: structured output and non-interactive flags everywhere.

curl -fsSL https://polylane.com/install.sh | bash        # macOS / Linux
irm https://polylane.com/install.ps1 | iex               # Windows
polylane auth signup --email you@example.com

SDK

Rate limits

Requests are rate limited per credential. When you exceed a limit the API returns 429 — back off and honour Retry-After when present, with exponential backoff rather than tight-looping.

Versioning and deprecation

The API is versioned in the URL path (/v1). Breaking changes only ship in a new version. Deprecations are announced in the build log and documented before removal; deprecated surfaces keep working during the transition window.

Machine-readable entry points

Support

Email boris@coreplane.ai or reach us on X at @polylanehq.