Chai PotOpen demo potOne pot for the group.
An agent that pays the bills, within your rules.
Trips, flats and team outings run on one person fronting money and chasing everyone after. Chai Pot flips it: everyone chips in up front with PayPal, and an AI agent pays the group's bills from the pot, but only inside the limits the members set. Anything bigger waits for the group to approve.
The problem
Someone always fronts the money
One friend pays the villa, the cab and the dinner, then spends a week chasing UPI pings and spreadsheet math.
Shared cards have no rules
A joint account or a shared card means anyone can spend anything. Nobody wants that.
Agents can pay, but should they?
An AI that pays bills is only useful if it can't overspend. The limits must belong to the people whose money it is.
How Chai Pot works
1. Set the rules
Create a pot, add members, set a contribution target, a per-bill cap, a daily cap, allowed categories and how many approvals bigger bills need.
2. Fund with PayPal
Each member pays their share through PayPal Checkout. The server captures the order and records exactly what PayPal confirms. USDC on Base is optional.
3. Ask the agent
Snap a receipt or type “pay the $24 dinner at Saravana to host@example.com”. Gemini itemizes it and proposes a split.
4. Policy decides, PayPal pays
A deterministic policy engine checks caps, category and funds. Within limits: paid instantly with PayPal Payouts. Above: held for approvals. Every step lands in the audit log.
Why it's safe
- The AI only interprets. Money moves only when the rules engine says so.
- Prompt-injection in a request can't raise a limit: limits are not something the model controls.
- Contributions are recorded from PayPal's capture response, not from the browser.
- Unspent money goes back to the member through a PayPal refund on their own payment.