FullCup.ai
Create a Cup

↑↓ navigate · Enter open · Esc close · ? Keyboard shortcuts

Keyboard shortcuts

⌘ K · Ctrl K
Search or run
?
Show shortcuts
J
Next item in the list
K
Previous item in the list
N
New post (in the studio)
Esc
Close dialog or menu

Standard Commitment

The text a creator signs when publishing a cup. The signature is recorded publicly, so anyone can check what was agreed and when.

Version v3 · sha256 be0ef98e9923e8b8071ace72a71f7f7cc03085a8be274a6a3c77cc1210ff5341

Canonical text, in English. Translations are made with legal review, not automatically.

FullCup Standard Commitment — v3 (draft, pending legal review)

By publishing a Cup, you agree to the following terms. This text is hashed and the hash is recorded on FullCup's public, tamper-evident ledger together with your roadmap, so that anyone can verify what was agreed and when — without having to trust FullCup's word for it.

1. What a Cup is. A Cup is a Goal — one sentence describing what will exist when it succeeds — decomposed into 2 to 5 Milestones, each with an expected time window, an expected amount of compute capacity, and a named deliverable. Publishing a Cup means committing to this Goal and this Milestone breakdown.

2. What you receive. You never receive money. Backers fund your Cup with compute capacity; when that capacity is provisioned, you receive a scoped API key. FullCup never converts that capacity to cash on your behalf, and you agree not to represent it as cash.

3. What every request produces. Every request made through your key produces a signed receipt (Ed25519) recorded on the public ledger. Receipts never contain your prompts or completions — only consumption metadata (model, token counts, cost, timestamp). Anyone can verify a receipt's signature independently, using the public key FullCup publishes.

4. How the price breaks down. A contribution buys managed compute capacity from FullCup.ai. Most of it becomes capacity for the cup; the rest is what FullCup.ai charges for providing and verifying it. That charge is a percentage of the contribution plus a small fixed amount, so the effective percentage is higher on a small contribution and lower on a large one — which is why this Commitment states the rule rather than a single number. The exact split for the amount being contributed is shown to every backer before they contribute, on every contribution, with no exception and no hidden spread. FullCup.ai never passes money to you — you receive scoped capacity, and the backer buys it from FullCup.ai, not from you.

5. Reporting on Milestones. For each Milestone you close, you write one short note describing what happened and link to a verifiable deliverable. If actual consumption differs from what you declared, that difference is published as-is — it is information, not a penalty. FullCup does not penalize you for missing an estimate.

6. Revising the roadmap. You may revise a Milestone's title, deliverable, expected window, or expected amount at any time, with a stated reason. Revisions are public and are never treated as a broken commitment. What is not acceptable is silence: a Milestone with no consumption and no update for an extended period may cause your Cup to be paused.

7. Unused capacity. Capacity your Cup does not consume by the time it concludes returns to FullCup's shared pool, to fund the next round of projects. It is never converted to a financial return, for you or for your backers.

8. No equity, no revenue share, no security. This Commitment grants backers no ownership, equity, profit share, or right to repayment — and you agree not to offer any of those in return for funding a Cup on FullCup.ai. Raising capital for your project by other means, with other people, is your business and not ours. What you may not do is make it the counterpart of a contribution made here. FullCup.ai does not record, index, publish or score any such offer, and will not act as a registry for one: a Cup funds compute capacity and nothing else. A Cup found to carry a financial counterpart is paused.

9. Capacity class substitution. If FullCup ever substitutes the underlying compute your Cup draws from, the replacement stays within the same declared capacity class, and the substitution is never silent.

10. Everything above is verifiable, not just promised. Every event described in this Commitment — your roadmap, your Milestone updates, every receipt, every contribution — is recorded on an append-only, hash-chained ledger that a third party can independently verify without asking FullCup to vouch for it.

By signing below, you confirm you have read this Commitment and agree to it for this Cup.

See the projects