# Polar: L1 · Needs a person

As of 12 Oct 2026, an AI agent can't use Polar on its own: Cloudflare Turnstile on the email sign-in.

Source: https://agentdrives.com/tools/polar?via=md · driven 12 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

Needs a person before it does anything: L1 · Needs a person. Our agent stopped at signup: email sign-in on /auth shows a Cloudflare Turnstile widget, and it answered "Verification failed. Please try again." to our agent's browser. Other routes are Google, Apple or GitHub OAuth; none lets an API or CLI create an account. Dynamic client registration works headless, but authorizing still routes through that same Turnstile sign-in, so no token, no first call, no work done. Docs are agent-ready: llms.txt, Markdown pages, OpenAPI, a CLI, an OAuth MCP server. Paying and leaving stay untested: plan switches sit behind that same human sign-in, and the API has no operation to delete an account.

_Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_

L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level.

- Find: Docs for agents (llms.txt, an OpenAPI and an MCP server)
- Access: Can't sign up
- Use: Work not reached
- Pay: Payment not reached
- Leave: Leaving not reached
- Next: let an agent sign up on its own
- With an account set up by a person: not measured yet.

## Level history

- 6 Oct 2026: L1 · Needs a person
- 12 Oct 2026: L1 · Needs a person

## 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: Turned away when they send the sign-up form.
- Signed agents: The sign-up page opens. The check on the form still applies.
- 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: llms.txt at /docs/llms.txt, .md pages and Accept: text/markdown, OpenAPI 3.1.0 at /docs/openapi/2026-10.openapi.json
- **Sign up**: Needs a human: Email sign-in on /auth shows a Cloudflare Turnstile widget; it failed our agent's browser ('Verification failed. Please try again.'). Other routes are Google/Apple/GitHub OAuth; no API or CLI sign-up.
- **Verify**: Not reached: No code mail sent: the Turnstile check failed first.
- **Key**: Not reached: Organization access tokens are dashboard-only; DCR (POST /v1/oauth2/register) works headless but /oauth2/authorize sends to the same Turnstile sign-in. No device flow, no CIMD.
- **First call**: Not reached: GET /v1/products/ -> 401 Unauthorized without a token.
- **First action**: Not reached: No token.
- **Pay**: Not reached: Free Starter plan; Pro $20/mo, Growth $100/mo, Scale $400/mo switched in the dashboard behind the human sign-in. No 402, x402, MPP, Stripe Projects listing or billing API found. We paid nothing: no 402 asking for USDC.
- **Cancel**: Not reached: not tested: no plan or trial was started. Docs: plans can be switched anytime in the dashboard; downgrading to Starter moves to 5% + 50c.
- **Delete**: Not reached: No account was created; the OpenAPI has no user or organization delete operation.

## Does Polar (polar.sh) have an MCP server, and can an agent connect to it?

Yes. Polar has an official MCP server. The server signs an agent in with OAuth.

A new agent can't get in on its own: in the drive of 12 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 1 attempt worked.

## How does an AI agent get a Polar (polar.sh) API key?

Not reached: in the drive of 12 Oct 2026, sign-up stopped our agent first (it needs a person). Organization access tokens are dashboard-only; DCR (POST /v1/oauth2/register) works headless but /oauth2/authorize sends to the same Turnstile sign-in. No device flow, no CIMD.

## Paying the agent way

Payment not reached.

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.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
Ways to pay checked 12 Oct 2026.

## What an agent can do

- Read the full docs as Markdown via llms.txt and .md URLs
- Download the versioned OpenAPI spec
- Register an OAuth client headless via DCR

## What it cannot do

- Sign up or sign in: Cloudflare Turnstile on email sign-in failed our signed agent browser; other routes need Google/Apple/GitHub accounts
- Get an API token: Organization access tokens are dashboard-only; OAuth authorize goes through the same sign-in
- Use any product capability: No token
- Upgrade or pay for a plan: Only in the dashboard; no agent payment rail or billing API

## Tips for the owner

1. Let verified agents pass sign-in Turnstile
2. Add an API route to create access tokens
3. Offer device flow for CLI and MCP
4. Add a plan and billing API
5. Document and expose account deletion

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 Payments

- [Stripe](https://agentdrives.com/tools/stripe.md?via=md): L3 · Does the work · [Polar vs Stripe](https://agentdrives.com/compare/polar-vs-stripe?via=md)
- [Lemon Squeezy](https://agentdrives.com/tools/lemonsqueezy.md?via=md): L1 · Needs a person · [Polar vs Lemon Squeezy](https://agentdrives.com/compare/lemonsqueezy-vs-polar?via=md)
- [Mollie](https://agentdrives.com/tools/mollie.md?via=md): L1 · Needs a person · [Polar vs Mollie](https://agentdrives.com/compare/mollie-vs-polar?via=md)

## Tips for agent builders

- Read docs via https://polar.sh/docs/llms.txt and .md page URLs
- A human must sign in once and create an organization access token (Settings > Developers) or approve MCP OAuth
- Use https://sandbox-api.polar.sh with a sandbox token for tests; sandbox.polar.sh disallows all crawlers in robots.txt