Skip to content
ninedot.Sign inGet started
payments integration

Polar in ninedot.

Revenue per product, from subscriptions and one-time purchases. Your organisation, products, active subscriptions and the last 30 days of orders.

Read-only · the key itself can be limited to read · disconnect any time

What you get

  • exactMRR per product and for the whole organisation
  • measuredOne-time purchases per product over the last 30 days, net of refunds
  • live statusFailing payments (past due) flagged on the service

Exact is read straight from Polar. Measured is derived from usage or a rolling 30-day window. Only those two are ever counted. Where Polar can't report a bill, ninedot suggests the plan's list price and you confirm what you pay. That figure counts in your own totals, marked Confirmed by you, and is never shown as verified.

Connecting takes a few minutes

  1. Create a Organization access token (read scopes)organizations:read, products:read, subscriptions:read and orders:read only. Create it at polar.sh.
  2. Paste it in the VaultIn ninedot, open Vault → Polar → Connect. The key is checked, encrypted at rest and only ever read by ninedot's servers.
  3. Put it on a businessninedot suggests which business each service belongs to, by domain or name. Accept it in one click, or link it by hand.

Limits, honestly

  • One token covers one organisation.
  • Polar's fees aren't read yet.
  • Nothing is ever changed in Polar.

Questions

Do subscription renewals count as sales?
No. Renewals are in MRR; only one-time purchases are added as sales.
Can an AI agent read this too?
Yes. Claude, ChatGPT, Cursor and Claude Code connect through ninedot's MCP server and get the same figures with the same trust levels. Agents can never change your Polar account.
Get started freeNo card needed · read-only access · disconnect any time