Build on kitty

The platform tier is for products that want kitty's engine inside their own: an accelerator giving every founder a validated idea, a CRM that scores the businesses in it, an agency tool that ships client sites. You get the same engine our own app runs on, over the MCP server and the REST API, billed on what your users actually consume.

How the meter works

There is one unit — Treats — and one price list, the same one the product itself is billed on. Work is priced per job, not per API call: listing ventures, reading a report or polling a task costs nothing. A deep analysis costs 80, a site build 10, an article 20. GET /api/v1/actions returns the live price of every action, so your own pricing never drifts from ours.

Failed work is never billed. A job reserves its cost when it starts and is charged only when it delivers evidence — a URL, a deploy id, row ids. A job that dies has its reservation swept and costs you nothing. That rule is not special-cased for the API; it is the same ledger.

What you pay

A committed monthly platform fee includes 6,000 Treats. Past that, usage is metered at $0.10 per Treats and invoiced monthly in arrears through Stripe — nothing stops mid-workflow because an allowance lapsed, which is the whole reason this tier exists. Committed Treats are cheaper than overage, so committing closer to your real volume is always the better deal.

You set a hard spend cap. Postpaid billing without a ceiling is one runaway agent away from an invoice nobody wants to send or receive. Past the cap, heavy jobs are refused with a 402 that names the cap — raise it whenever you like; nothing is lost and nothing is billed twice.

Reconciling and re-billing your users

One endpoint tells you what this period costs and where it went:

curl https://kitty.build/api/v1/usage \
  -H "Authorization: Bearer kitty_sk_YOUR_KEY"

{
  "creditName": "Treats",
  "periodStart": "2026-08-01T00:00:00.000Z",
  "plan": "platform",
  "metered": true,
  "credits": {
    "included": 6000,
    "balanceRemaining": 0,
    "spent": 8420,
    "overage": 2420
  },
  "overage": {
    "cap": 20000,
    "remaining": 17580,
    "usdPerCredit": 0.1,
    "estimatedUsd": 242.0
  },
  "byOp": [
    { "op": "analysis.deep", "credits": 6400, "count": 80 },
    { "op": "site.generate", "credits": 1200, "count": 120 }
  ]
}

byOp is your cost breakdown. Every charge is also stamped with the venture it was spent on, so attributing spend back to the customer who caused it is a grouping, not a guess. Our running total is an estimate for your dashboards; the Stripe invoice is authoritative.

Getting on the tier

It is sales-gated, because the committed allowance, the rate and the cap are set per contract. Email info@foundergem.com with the shape of what you're building and roughly how much of it you expect to run. Keys, access control and rate limits work exactly as they do on every other plan — see the MCP setup guide.