COMMERCIAL CONNECTIVITY TIERS · OLIVE BASALT

Turn multi-machine agent setup into connecting each host to your account.

Run Mizpah locally for free, or subscribe to an active connectivity entitlement (`fleet_pro_monthly` or `fleet_team_monthly`) to mint machine enrollment tokens, monitor live fleet presence, and relay sessions across machines without port forwarding.

01 · CONNECTIVITY PLANS

Entitlement-gated plans for single hosts and distributed fleets.

Every tier uses the same open-source Terra gate and Cartograph widget engine. Paid tiers activate cloud machine enrollment, live heartbeat presence, and cross-machine session brokering.

OPEN SOURCE · SINGLE HOST

Local Workstation

$0 forever · local loop

Run the Flutter desktop hub, Terra evidence map, and local agent sessions on a single workstation.

  • Unlimited local projects, briefs, and Terra evidence gates
  • Local CLI, IDE, and desktop launches for Claude, Codex, Antigravity & Grok
  • Full Cartograph widget validation and local library check-in
  • Zero cloud account required for single-machine work
TEAM · SHARED FLEET

Fleet Team

$79 per month · fleet_team_monthly

High-capacity multi-machine brokering and webhook-audited entitlement control for engineering labs.

  • Up to 128 inventory items per machine and 512 relay frames per brokered session
  • HMAC-SHA256 signed billing webhook lifecycle (`trialing`, `active`, `past_due`, `canceled`)
  • Immediate fleet-wide relay cutoff when an entitlement expires or is canceled
  • Strict cross-account isolation: zero source code or transcript storage

Mizpah.ai never runs model calls or stores source code or conversation transcripts. Billing checkout (`POST /api/v1/billing/checkout`) and signed webhooks (`POST /api/v1/billing/webhook`) govern `connectivity_entitled` in real time.

02 · SUBSCRIPTION & ENTITLEMENT LIFECYCLE

How billing state governs machine enrollment and relay.

Every enrollment and broker endpoint checks the account's live entitlement before minting tokens, accepting heartbeats, or relaying frames.

  1. 01

    Create Account & Sign In

    AUTH · /API/V1/ACCOUNTS

    Register via POST /api/v1/accounts/signup and sign in via POST /api/v1/accounts/signin to receive an authenticated bearer session token (`st_...`). New accounts start in `unsubscribed` status (`connectivity_entitled: false`).

  2. 02

    Initiate Plan Checkout

    BILLING · /API/V1/BILLING/CHECKOUT

    Call POST /api/v1/billing/checkout with `plan_id: "fleet_pro_monthly"` (or `fleet_team_monthly`) using your bearer session token to create a checkout session URL bound to your account ID.

  3. 03

    Verify Signed Webhook Transitions

    ENTITLEMENT · HMAC-SHA256

    POST /api/v1/billing/webhook verifies the `x-mizpah-signature` HMAC-SHA256 header. Statuses `trialing` and `active` grant `connectivity_entitled: true`; `past_due` and `canceled` revoke entitlement immediately.

  4. 04

    Enroll Machines & Broker Sessions

    ENROLL & RELAY · 401/403 GATED

    While entitled, mint single-use `et_...` tokens and run `mizpah connect --token et_<token>` on each host. Unauthenticated (401) and unentitled or cross-account (403) requests are deterministically refused.

03 · CHECKOUT & ONE-COMMAND ENROLLMENT

Activate Fleet Pro and connect your first host.

All account, billing, and enrollment operations are exposed over clean JSON endpoints and the `mizpah connect` CLI command.

# Create a Fleet Pro checkout session
curl -sS -X POST https://mizpah.ai/api/v1/billing/checkout \
  -H "Authorization: Bearer $MIZPAH_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"plan_id":"fleet_pro_monthly"}'
# Enroll a workstation with one command
mizpah connect --token et_<enrollment_token> --name gpu-workstation

Need to inspect your enrolled machines right now? Open the Account & Machine Connectivity Dashboard at /connect.