# PlanetScale: L2 · Gets in As of 2 Oct 2026, an AI agent gets into PlanetScale on its own. Source: https://agentdrives.com/tools/planetscale?via=md · driven 2 Oct 2026 by AgentDrives's agent · Same level in 2 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 Gets in on its own: L2 · Gets in. Our agent signed up headless, no CAPTCHA, confirmed by email, logged in through the CLI's device flow, and pulled a service token for both the API and a hosted MCP server. It stopped trying to create a database: the API answered that it could not verify a card, and there is no free plan to work around that. Paying needs a card through Stripe Checkout; our agent never attached one, so it never reached core database work. Deleting the account needs the web UI: no API route exists for it. _Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_ L2 · Gets in: An agent gets in on its own, by any way the product offers: its own sign-up, a key by API, pay per call or no key at all. It does less than half the core work, or the work isn't measured yet. - Find: Docs for agents (llms.txt, an OpenAPI and an MCP server) - Access: Sign-up by email - Use: Work not reached - Pay: Card checkout - Leave: Leaves on its own (Nothing to cancel, deletes its account) - Ways in: Sign-up by email - Next: let a trial or free plan reach the core features - With an account set up by a person: not measured yet. ## Part scores - Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI found - Not measured in this drive: Holds up, Docs match ## Who gets in - Agents on a server: Get in on their own. - Signed agents: Not checked: its robots.txt asks crawlers to stay off the sign-up page. - Agents in a person's browser: Not measured yet. Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Checkpoints - **Docs**: Headless: docs/llms.txt (23.5 KB), .md twin of every page, an agent setup prompt (docs/agent-setup/prompt.md), OpenAPI at /docs/openapi.yaml (280 operations), pscale agent-guide --format json. - **Sign up**: Headless: Public sign-up form at auth.planetscale.com/sign-up posted with curl (email, password, ToS). No CAPTCHA, no phone, signed datacenter agent let through. It is a web form, not an API. - **Verify**: Headless: Verification mail arrived within seconds; opening the confirmation link with curl was enough. - **Key**: Headless: pscale auth login --format json starts an OAuth device flow; we approved the device code by posting the auth.planetscale.com/oauth/device form with our session cookie. Then pscale service-token create gave an API/MCP token. - **First call**: Headless: pscale org list --format json and GET api.planetscale.com/v1/organizations with the service token returned org an inbox; MCP tools/list returned 25 tools. - **First action**: Blocked: Creating a database (CLI, API) returns 422 'We were unable to verify your credit card. Please add your payment information.' No free plan; cheapest is single-node Postgres from $5/mo. MCP has no create-database tool. - **Pay**: Not tried: No x402/MPP/L402: api.planetscale.com answers 401 JSON, x402./mpp./agents. subdomains do not resolve, no /.well-known/ucp, no x-payment-info in OpenAPI, nothing in Bazaar or mpp.dev. CLI and MCP return a Stripe Checkout URL to attach a card; we stopped there (no card). Once a card is attached, creating and resizing paid databases is headless via CLI/API, so with a card this would be. Stripe Projects lists planetscale/postgresql but is a developer preview behind an access request. - **Cancel**: Not needed: Nothing to cancel: our agent started no paid plan. - **Delete**: In a browser: No delete-account or delete-org route in the API (OpenAPI) or CLI. Web UI Settings > Account > Delete account: type email, re-enter password (confirm-access), done. Verified: CLI token expired, password sign-in fails. ## Does PlanetScale have an MCP server, and can an agent connect to it? Yes. PlanetScale has an official MCP server. The server is hosted, lists 25 tools and signs an agent in with OAuth. A new agent can get in on its own: in the drive of 2 Oct 2026, our agent signed up, verified and got its key without a person. Through the MCP server, 0 of our agent's 1 attempt worked. ## How does an AI agent get a PlanetScale API key? In the drive of 2 Oct 2026, our agent got its PlanetScale API key over the API, without a browser or a person. pscale auth login --format json starts an OAuth device flow; we approved the device code by posting the auth.planetscale.com/oauth/device form with our session cookie. Then pscale service-token create gave an API/MCP token. ## Paying the agent way Card checkout. Ways to pay it offers an agent: Stripe Checkout; Stripe Projects (a third party's); Cloud marketplace billing (card checkout). What would let agents pay on their own: - Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card. From the drive of 2 Oct 2026. ## What an agent can do - Sign up, verify email and log the CLI in without a browser (form posts + OAuth device code) - Create, scope, use and delete service tokens for the API and MCP server - Connect to the hosted MCP server with a service token and call its tools - Create a team, add a member, and delete the team via CLI - Read the organization audit log, members, regions, cluster sizes and invoices via CLI - Measure latency to PlanetScale regions with pscale ping - Get a Stripe Checkout link to attach a card via CLI or MCP ## What it cannot do - Create any database (and so branches, SQL, deploy requests, replicas, backups, insights): No free plan: database creation requires a verified card on file - Pay without a human card holder: Only rail is a Stripe Checkout card form; no agent-native payment rail - Delete the account headless: Only in the web UI (with a password re-confirm); no API or CLI route ## Tips for the owner 1. Offer a card-free starter database for agents 2. Accept an agent-native payment rail 3. Add an account/org delete endpoint 4. Clean JSX out of MCP docs-search snippets Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month). ## Also in Databases - [Airtable](https://agentdrives.com/tools/airtable.md?via=md): L4 · Runs on its own · [PlanetScale vs Airtable](https://agentdrives.com/compare/airtable-vs-planetscale?via=md) - [NocoDB](https://agentdrives.com/tools/nocodb.md?via=md): L4 · Runs on its own · [PlanetScale vs NocoDB](https://agentdrives.com/compare/nocodb-vs-planetscale?via=md) - [Convex](https://agentdrives.com/tools/convex.md?via=md): L3 · Does the work · [PlanetScale vs Convex](https://agentdrives.com/compare/convex-vs-planetscale?via=md) - [Neon](https://agentdrives.com/tools/neon.md?via=md): L2 · Gets in · [PlanetScale vs Neon](https://agentdrives.com/compare/neon-vs-planetscale?via=md) - [Supabase](https://agentdrives.com/tools/supabase.md?via=md): L1 · Needs a person · [PlanetScale vs Supabase](https://agentdrives.com/compare/planetscale-vs-supabase?via=md) - [Baserow](https://agentdrives.com/tools/baserow.md?via=md): L1 · Needs a person · [PlanetScale vs Baserow](https://agentdrives.com/compare/baserow-vs-planetscale?via=md) - [MongoDB Atlas](https://agentdrives.com/tools/mongodb.md?via=md): L1 · Needs a person · [PlanetScale vs MongoDB Atlas](https://agentdrives.com/compare/mongodb-vs-planetscale?via=md) - [Turso](https://agentdrives.com/tools/turso.md?via=md): L1 · Needs a person · [PlanetScale vs Turso](https://agentdrives.com/compare/planetscale-vs-turso?via=md) ## Tips for agent builders - Install the pscale binary from GitHub releases and always pass --format json: every error comes back with issues and next_steps. - pscale auth login --format json prints a device URL and code; the human (or a logged-in session) approves it once; then create a service token for everything else. - Service tokens: REST uses 'Authorization: :'; the MCP server wants 'Authorization: Bearer ' (secret only). - Grant service-token access explicitly (pscale service-token add-access) or calls fail. - There is no free plan: ask your human to attach a card first (pscale billing payment-method update gives a Stripe Checkout URL), or use Stripe Projects if you have preview access. - pscale org team create needs --name; a positional name is rejected.