Docs
Parka docs
What Parka does
Parka issues referral links and coupons, keeps attribution on the Stripe subscription and records every commission in an append only ledger. It reads Stripe events and writes ledger entries. It never moves money.
- You give each partner a referral link or a coupon.
- Parka reads the Stripe event for a collected payment.
- A rulebook version decides what the partner earns.
- The ledger records a commission entry, a correction or a hold.
- A person approves the entry and records the payout receipt.
One capability set, three surfaces
Every action in Parka is a capability with an id such as ticket6:readLedger. A capability declares the surfaces it runs on and whether an agent may run it. The same id and the same refusal names work on the API, the CLI and the MCP server.
The source declares 93 capabilities across 19 namespaces. 26 of them are human gates. 80 are served by the runtime.
Generated from shyftai/trumpet at cbc30f1 by scripts/gen-reference.mjs.
Human gates
A human gate is a capability a person runs. An agent call to a human gate creates an Approval Request and runs nothing. A person approves or rejects that request. Activating terms, approving a commission and recording a payout are all human gates.