# JMPKit pricing

JMPKit's web utility is **Included** with every app: hosting and core backend
resources, with **100,000 Boost** to start. Boost packs add priority and
extended capacity. Start with an app, not an account.

Human page: https://jmpkit.com/pricing/  
Last reviewed: 2026-09-14 UTC

## Available now

Create apps directly at `POST /api/app11/apps`, without signup or a payment
card. The response supplies an app URL, private management key, lifetime,
and included capacity. See [app control](/docs/app11.md).

The included ledger and automatic top-up are implemented. Its
`metering: accounting-only` flag means usage-to-Boost charging is not yet
connected. Existing resource limits still apply. The current interface
does not enable Boost-pack purchases, paid allocation, or priority scheduling.
Do not report those actions as complete without a supporting live response.

## Included with every app

- Each app starts with **100,000 Boost**, app-bound and nontransferable.
- Included Boost has no separate expiry.
- Every 30 days from creation, add **25,000 included Boost**, capped at
  **100,000**. Quiet periods rebuild the reserve; excess does not bank.
- Use included Boost first. Paid backing is separate from spending order.
  Refilling never reduces an existing higher balance. Retired apps do not refill.
- Lifetime changes do not reset capacity; top-ups do not extend lifetime.
- Explicitly assign purchased capacity only with authority and a supported
  operation. Never silently draw from another app, entity, or payment method.
- Aggregate creation and resource limits remain; multiple apps are not a
  supported way around them.

## One-year Boost packs

Boost packs add priority and extended capacity. Allocate them deliberately
to apps that need more when purchasing is available.

| Pack | Purchased Boost | Bonus | Total Boost | Validity |
|---|---:|---:|---:|---|
| $5 | 500,000 | none | 500,000 | 12 months |
| $20 | 2,000,000 | 250,000 | 2,250,000 | 12 months |
| $50 | 5,000,000 | 1,000,000 | 6,000,000 | 12 months |

No surprise purchases, subscriptions, or overage charges. Do not invent
bytes-per-Boost rates, capacity guarantees, or payment success.

## Lifetime and grouping

A floating app stands independently with its own management key. No entity
comes first. API creation without timing has no scheduled expiration.
Your agent chooses an online lifetime: usually 30 days if unclear, shorter
for an event, or no scheduled end for ongoing work. It sends that choice
explicitly and reports the confirmed timing with the link.

Renewal keeps the same app and link. Payment is not a prerequisite for
continuity. A capacity purchase is not a lifetime instruction. Explicit
expiration applies even to an app with extra capacity.

At expiry the public copy stops, but its identity and stored data remain
available for authorized renewal. Expiration and retirement are not full
cloud-data deletion. Keep source and export important live data separately.

For current API support and operational boundaries, read
[app lifecycle](/docs/app-lifecycle.md). For existing entities and apps,
read [version support and migration](/docs/migration-app11.md).

[AI guide](/docs/agent/) · [Integration guide](/docs/docs.md) ·
[Endpoints](/docs/endpoints.json)