Set up Polylane for me. Do it yourself over the API. Ask me only for what only I can give you: how I want to sign up, the code Polylane emails me if I pick email, and credentials you cannot find on this machine.

1. Sign me up, and recommend Google or GitHub first: those arrive already verified, so there is no emailed code, and GitHub leaves me signed in for the App install in step 7. Send me to https://console.polylane.com, let the console create my workspace, then have me open Settings, API Keys, mint a key with the scopes in step 4 and paste it to you. That covers steps 2 to 4; read my workspaceId from GET https://api.polylane.com/v1/workspaces with x-api-key: <sk_ key>. If I would rather you ran the whole thing, sign me up with email and password instead: POST https://api.polylane.com/v1/auth/signup, header x-polylane-client: cli, body {"email","password"}. Ask me for the email, generate the password (8+ characters, upper, lower, digit, symbol) and show it to me so I can save it. Keep result.user.id.
2. Email path. Verify my email before anything else, because every authenticated route needs a verified account. Ask me straight away for the 6 digit code Polylane just emailed me: it lasts 15 minutes. POST https://api.polylane.com/v1/auth/verify_email, body {"email","code"}. Its result.token is a session token: send it as Authorization: Bearer <token> in steps 3 and 4. If the code has expired, POST https://api.polylane.com/v1/auth/resend_verification_code, body {"id":"<result.user.id from step 1>"}, and ask me again.
3. Email path. Create the workspace. POST https://api.polylane.com/v1/workspaces, body {"name":"<my company>"}. The name is 4 to 128 characters and unknown keys are rejected. Keep result.id as workspaceId. I am the owner, with every scope.
4. Email path. Mint a key. POST https://api.polylane.com/v1/api_keys, body {"workspaceId","name":"agent-setup","scopes":[...]}. Take agent_tools:read, agent_tools:write, local_source:write, cloud_accounts:read, cloud_accounts:write, integrations:read, integrations:write, repositories:read, repositories:write. Keep result.token, which starts with sk_. Steps 1 to 4 are plain HTTPS: MCP needs a key that step 4 is the first to produce, and workspace creation is REST only.
5. Register the MCP server in your own config: streamable HTTP at https://mcp.polylane.com/mcp, headers x-api-key: <sk_ key> and x-polylane-allow-writes: true. The key is the whole sign-in. Verify eight tools: search, execute, searchTools, runTool, runCode, startMapping, advanceMapping, getMappingStatus.
6. Connect what I run. Look on this machine first: AWS CLI credentials, a kubeconfig, provider tokens already in the environment such as CLOUDFLARE_API_TOKEN. Then ask me once, in one message, for whatever is left. POST https://api.polylane.com/v1/cloud_accounts and https://api.polylane.com/v1/integrations/connect, header x-api-key: <sk_ key>. Per-provider bodies are in the OpenAPI spec at https://api.polylane.com/v1/doc, or reach the same routes with the MCP execute tool.
   - One credential each: Cloudflare, Fly, Render, Railway workspace token, PlanetScale service token, Supabase personal access token, Turso platform API token.
   - Kubernetes: there is no credential to POST. Install the in-cluster agent with Helm: helm install polylane oci://ghcr.io/coreplanelabs/charts/polylane-k8s --namespace polylane --create-namespace --set polylane.apiKey=<sk_ key> --set config.cluster_name=<name>. The agent registers the cluster itself; the key from step 4 already carries cloud_accounts:write.
   - AWS: POST /v1/cloud_accounts {"workspaceId","provider":"aws","account","region"} returns result.s3Url, a presigned CloudFormation template. Download it, then run aws cloudformation create-stack --stack-name PolylaneConnector --template-body file://<path> --capabilities CAPABILITY_IAM --region <region>. The stack registers the account itself.
   - Integrations: Datadog, Honeycomb, Axiom, Better Stack, Devin, Cursor, Factory, Conductor.
7. Hand me the browser steps together, with links, once the rest is connected. Installing the GitHub App is mine to click, and GitHub is the only code host: POST https://api.polylane.com/v1/integrations/github/generate gives you the URL. Vercel, Slack and Sentry are OAuth: /v1/cloud_accounts/vercel/generate, /v1/integrations/slack/generate, /v1/integrations/sentry/generate.
8. Verify and report. searchTools returns only tools whose integration is connected, so it is the workspace's real state; if something you connected brought none, name it and stop. Then one line each: which services Polylane sees, what changed in production today, what issues it raised. Never guess a tool name; searchTools has them.

You are done after step 8. If a step fails twice, give me the step number and the exact error instead of working around it.

Docs index: https://docs.polylane.com/llms.txt. Per-client MCP setup: https://docs.polylane.com/coding-agents/platform-mcp. This prompt is published at https://api.polylane.com/v1/public/setup/prompt.md, so you can re-fetch it to confirm it is genuine.