fundid — did you fund it?
=========================

Every app on fundid runs on a communal fuel jar: a public balance that pays
the app's server bill. Nothing else. Anyone can top it up — guest checkout,
no account. Runway is always shown as time ("funded through Sep 30"), never
as a balance. When a jar hits zero the app hibernates: the machine stops, the
data stays safe indefinitely, and any payment wakes it in seconds.

Base URL: https://fundid.app

READ A JAR  (public, CORS open — what the embeddable gauge reads)
  GET https://fundid.app/api/jar/<slug>
  -> { "state": "healthy|low|critical|hibernating", "balanceUsd", "burnRateUsdMo",
       "runwayDays", "fundedThroughDate", "funderCount", "recentFunders", "reviveUsd" }

TOP UP A JAR  (humans and agents alike)
  POST https://fundid.app/api/checkout/<slug>   {"amountUsd": 10, "funderName": "maya"}
  -> { "url": <Stripe Checkout> }
  $5 card minimum. Add "revive": true to wake a hibernating app.

PUT AN APP ON FUNDID  (invite-gated, human-reviewed)
  1. Get an invite code: the waitlist at https://fundid.app/#waitlist
  2. POST https://fundid.app/api/intake
     {"inviteCode": "...", "appName": "...", "slugRequest": "...", "url": "...",
      "burnTier": "<estimated hosting cost, USD per month>", "contactEmail": "..."}
  3. A human reviews it; the invite is only consumed on approval.
     Approved apps are born hibernating.
  4. The first top-up wakes the app. There is no free tier, on purpose.

EMBED THE LIVE GAUGE
  <script src="https://fundid.app/widget.js" data-app="your-slug" async></script>
  No-JS fallback: <a href="https://fundid.app/<slug>"><img src="https://fundid.app/<slug>/card.svg" width="600"></a>

THE RUN HOST
  GET https://<slug>.fundid.run/
  Answers for the jar: agents get the jar as JSON — 200 while awake, 402
  Payment Required while asleep, with the exact checkout call that wakes it.
  Browsers are redirected to the jar page. Every 402 is a real clock: payment
  really is the one thing that wakes the machine.

OTHER PUBLIC ENDPOINTS
  GET https://fundid.app/api/stats · GET https://fundid.app/<slug>/card.svg
  POST https://fundid.app/api/notify/<slug> · POST https://fundid.app/api/waitlist

THE RULES OF THE JAR
  - Money in a jar buys server time. Nothing else. The platform cut is 20%,
    taken once at top-up and shown at checkout; burn is pass-through at cost.
  - Jar credits are closed-loop: they never convert to cash, for anyone.
  - Hibernation is not deletion. Data is never hostage; anyone can revive.
  - The gauge never nags: a countdown is shown to a person at most twice.
  - Every countdown is a real clock on a real machine.