-
-
Find the date that fills the class: Claude reads the group chat, and PayPal charges only when enough people reserve
-
The organizer pastes her group chat or a WhatsApp export. CommitPool finds who said what
-
Claude reads each person's own words against every date, in any language. Unclear answers aren't counted yet
-
Claude drafts one reply for the group and asks one question when unsure. Every number comes from CommitPool
-
Each participant approves a $45 PayPal hold. It's a hold, not a charge, until the class reaches its minimum
-
When the minimum is reached, all holds are charged: $135 collected, $8.19 PayPal fees, $126.81 net
-
Verify with PayPal reads every order, hold and charge back from PayPal: 9 of 9 records match
-
When the class starts, PayPal Payouts sends the organizer $126.81. If too few reserve, every hold is released
-
CommitPool is also an MCP server. An AI assistant can prepare the terms, but only the organizer approves them
-
On 60 test messages, Claude read 59 exactly and a keyword reader managed 17. The eval is published in the repo
CommitPool finds the date that fills a small paid class from the group chat itself, then holds each spot with PayPal, charged only if enough people reserve.
What's new compared with all-or-nothing group holds: the date is read from the real group chat, pasted or exported from WhatsApp; Claude asks one question tied to the class hours when a message leaves them open; and Claude words one reply for the group to paste back into the chat.
The proof: on 60 hand-written messages, Claude read 59 exactly, a keyword reader 17, and 0 of 10 prompt injections worked. On the hosted demo, Verify with PayPal matched 9 of 9 records with the Sandbox, and the organizer was paid $126.81 with PayPal Payouts (batch L8SSKBUKM5UF6, SUCCESS 32.8 s after closing reservations).
Try it in 4 minutes
Everything runs on the PayPal Sandbox; no real money moves.
- Open https://3-209-60-155.sslip.io and press Try it as Iris. Press Read the chat, then Add 6 people, and watch Claude read her group chat.
- Claude asks Grace a question about the class hours. Under Act as, press Grace Liu and answer it, for example: "No problem — I swapped Saturday. Sunday I'm still at the market." Saturday reaches 3.
- Press Open reservations. Act as Priya, Ben and Grace, and reserve with the PayPal Sandbox buyer from the testing instructions; PayPal remembers the login after the first checkout. The third hold charges all three: It's on.
- Press Verify with PayPal, then follow the guide: Close reservations now, Start the class now. The board reads "Class started · $126.81 paid out to Iris".
Inspiration
The hard part of a small paid class is the week before: a group chat full of "probably" and "I'm in if…", two possible dates, and a room that costs the same whether three people come or none. Nobody answers "Saturday: yes, Sunday: no". They write "only if we're done by 11:30" or "el domingo me viene perfecto", and someone has to work out which date reaches the minimum. Saying "I'm in" also costs nothing, and it shows. In PheedLoop's check-in data from more than 1,000 events, small free events of 10–49 attendees had a median no-show rate of about 37%, against about 17% for small paid ones. And many people run small classes: O*NET, using 2025 BLS data, counts 419,100 self-enrichment teachers and 388,400 exercise trainers and group fitness instructors in the US. All-or-nothing holds make a yes cost something. CommitPool starts earlier, in the chat where the date gets decided.
What it does
Iris Calder, the demo organizer, teaches life drawing for beginners at The Long Room in Red Hook, Brooklyn. The room and the model cost $120 a session, so at $45 a spot she needs 3 of her six easels filled. The class could run Saturday or Sunday, 10 AM–12 PM, New York time.
- She pastes the group chat, or uploads WhatsApp's Export chat
.txt. CommitPool finds who said what with plain code, no model. Claude reads each person's own words against every date, in any language: Lucía writes in Spanish, and Hannah's "only if we're done by 11:30" doesn't fit a class that ends at noon. - One question tied to the class hours. Grace wrote that mornings are tricky but she might swap one. In my test walk, Claude asked her: "The workshop runs 10 AM–12 PM on Saturday, November 21 and Sunday, November 22 (New York time) — can you make either morning, and which?" She isn't counted until she answers.
- Claude's reply for the group: one message to paste back into the chat, with the count per date, how many more are needed, the open question and the invite link. CommitPool supplies every fact; Claude only words it.
- Re-paste. Grace can answer in the group chat itself. Pasting the chat again reads only the new messages, as a follow-up to Claude's question, and Saturday goes from 2 to 3.
- Honest ties. Before that, both dates have 2, and the board says "Tied: Sat, Nov 21 comes first".
- CommitPool picks the date that reaches the minimum. Everyone reserves with a PayPal Orders v2
AUTHORIZEhold, on a checkout that shows the CommitPool brand. Once enough people reserve, the holds are captured. Otherwise every hold is released and any charge refunded. - The money:
$135.00 collected · $8.19 PayPal fees · $126.81 net, with "$6.81 to spare after PayPal fees" on her $120 cost. Verify with PayPal reads every order, hold and charge back from PayPal: 9 of 9 matched. When the class starts, Iris is paid the net with PayPal Payouts. - The rescue. When a class is still short with six hours or less to go, Claude proposes the one deadline extension the rules allow: once, before anyone is charged, within the three days PayPal honors a hold. Nothing moves until Iris approves.
- The MCP server. Iris's AI assistant can read who can come, check the payments against PayPal, and prepare opening reservations or the extension. She approves both on her own page, and no tool moves money.
- A demo guide walks a judge from the chat to "Class started · $126.81 paid out to Iris".
Claude reads, CommitPool decides, PayPal moves the money. The server counts, picks the date, and decides when to capture, release, refund and pay out. People approve every step that matters.
How I built it
- One Go binary (API, MCP server, payment worker and the embedded React app) over PostgreSQL, on one Amazon EC2 VM provisioned with Terraform.
- PayPal:
- Orders v2 with
AUTHORIZE; - Payments v2 for capture, void, refund and Verify's reads, with fees from
seller_receivable_breakdown; - Payouts under one
sender_batch_idper class; - verified webhooks that only trigger a read-back;
- a
PayPal-Request-Idon every money call, saved before it is sent.
- Orders v2 with
- Claude Sonnet 4.5 on Amazon Bedrock, through the Anthropic Go SDK. A strict JSON schema has the dates as an enum, and every message reaches Claude as data. Spend caps protect readings, and explanations and nudges fall back to plain text.
- Tested: 979 Go test functions and 3 fuzzers, run with
-race; 490 interface tests (Vitest); 29 Playwright tests in 13 files, with axe accessibility checks. On the hosted demo, with real Claude and the Sandbox, 6 of 6 chat answers were read in 15.9 s, a re-pasted reply moved Saturday from 2 to 3 in about 5 s, and there were 0 console errors. - Measured (
docs/eval.md): 60 messages in 9 categories, from negations that mean yes to Spanish, Portuguese and 10 injections. Claude counted nobody on a date they couldn't attend; the keyword reader did on 44 dates.
Challenges I ran into
- A reply only makes sense next to the question, so a re-pasted chat sends only the new messages, as a follow-up.
- A timeout is not an answer. Every ambiguous result is read back from PayPal before the local state changes.
- Paying out once, and not too early: at the class start, under one batch id per class.
- A pasted chat is untrusted text. The reading has no place for a price, a minimum or another date.
What I learned
- Let the model read and word, and keep every number on the server.
- Measure against a simple baseline: it showed where the costly mistake was.
- Design payments around the ambiguous cases first.
Limitations
- PayPal Sandbox and USD only.
- Reservations stay open at most 72 hours, extension included; there is no reauthorization.
- Money passes through CommitPool's PayPal account. The payout is final: a later refund or dispute is absorbed by the platform.
- Distinct buyers aren't enforced; the demo uses one buyer.
- No accounts, only private links. Emails are logged, not sent.
- No MCP tool imports a chat.
What's next
- Multiparty onboarding, so holds go to the organizer's own PayPal account.
- One spot per PayPal account.
- Reauthorization for longer windows, and more currencies.
Built With
- amazon-bedrock
- amazon-ec2
- anthropic-go-sdk
- aws-systems-manager
- caddy
- claude-sonnet-4.5
- docker
- go
- mcp-go-sdk
- model-context-protocol
- paypal-orders-v2
- paypal-payments-v2
- paypal-payouts
- paypal-sandbox
- paypal-webhooks
- pgx
- playwright
- postgresql
- react
- tailwind-css
- terraform
- typescript
- vite
- vitest