Agentic group buying. Agents pool demand into chains that clear at a group price. Waitlist is open.
Scored across 19 tools
Several tools are direct duplicates or clearly marked as obsolete replacements: hold/join/join_chain, leave/release, park/park_intent. This creates significant ambiguity about which to call, and waitlist also overlaps with want. The descriptions try to disambiguate by saying 'use X instead', but having both present still causes misselection risk.
Naming is inconsistent: some pure verbs (hold, park, release), some verb_noun (get_chain, list_chains, want_gym), some nouns (status, my_agent). There are also legacy names that don't follow the pattern (join, leave, park_intent). The want_* group is consistent, but overall no clear pattern.
19 tools is on the heavy side (16-25 range). Many are redundant due to deprecated aliases, so the effective surface is smaller, but the count is still inflated by tools that direct you elsewhere. Not extreme, but borderline over-stuffed.
The core workflow is covered: adding wants (want plus specialized variants), holding and releasing spots, getting status and lists, syncing wishlists. Missing update operations (e.g., modifying a hold) but that's a minor gap likely workaroundable by release and re-hold.
Counts at a glance: live, queued, filled. Use status for the live product.
Inputs: no named parameters.
Hold your human a spot on the live product. Needs their email. Returns the price this spot locks and a link where they save a card; the spot is held once they do. The first spots lock at the early price; every spot after locks at the group price. The result says which one this spot got. Nothing is charged now. If the product fills, the deposit is charged and applied to their purchase; they pay the balance to the brand. If it doesn't fill, nobody pays. Stripe test mode. Test cards only, no real money moves.
Inputs: email (required), ref, name, chain, +2 more.
The old name for hold. Hold your human a spot on the live product. Needs their email. Returns the price this spot locks and a link where they save a card; the spot is held once they do. The first spots lock at the early price; every spot after locks at the group price. The result says which one this spot got. Nothing is charged now. If the product fills, the deposit is charged and applied to their purchase; they pay the balance to the brand. If it doesn't fill, nobody pays. Stripe test mode. Test cards only, no real money moves.
Inputs: email (required), ref, name, chain, +2 more.
The old v1 join. Use hold instead.
Inputs: id, team_name, monthly_commit_usd.
The old name for release. Release a held spot. Needs the product slug, the email that holds it, and the commitment id from hold or status. Nothing is charged for a released spot.
Inputs: chain (required), email (required), commitment_id (required).
Every product btw has run or queued: the live one, what's up next by wants, and what filled or closed. Use status for the live one.
Inputs: no named parameters.
What your human's btw agent is watching, with a status on each thing: watching (counting the other agents), group forming (enough want it that btw is talking to the brand), or live (there's a price and a deadline, hold a spot). Takes their email. The list opens once they've clicked the confirm link btw emailed them the first time you called.
Inputs: email (required).
Old style: park what your human wants in plain words with the most they'd pay. Prefer want with a link.
Inputs: description (required), max_price_usd (required), email.
The old v1 park. Use want with a link instead.
Inputs: note, category, provider, monthly_cap_usd, +1 more.
Release a held spot. Needs the product slug, the email that holds it, and the commitment id from hold or status. Nothing is charged for a released spot.
Inputs: chain (required), email (required), commitment_id (required).
What's live: the product, its list and group price, how many buyers unlock the price, how many are committed, how many want it, spots left, and the deadline if one is set. Give a slug to ask about another product, and an email to also see that person's spot.
Inputs: chain, email.
Read a public wishlist and add every item to your human's btw agent. Amazon wishlists and Steam wishlists. Takes the list link plus their email; a new email gets an agent. Returns the items found and how many other agents want each one. If the server can't read the list, the reply says so; then open the list yourself and pass the ASINs, or call want once per product link. btw doesn't buy from Amazon. The link is how we know what you want; the group price comes from the brand.
Inputs: email (required), url, asins.
Old style: put your human on the list to hear when the next product goes live. Prefer want with a link, or hold on what's live. Needs their email. Optionally say what they want to buy and which agent platform you are.
Inputs: want, email, platform, referral.
Add something to your human's btw agent. Takes a link or an ASIN plus their email; a new email gets an agent. A hotel link becomes a stay (give month, and nights if known), a subscription link becomes software (give plan), anything else is gear. Or set type and the fields outright: stay needs hotel and month, home needs job and zip, software needs product and plan. Their agent starts watching it and the reply says how many other agents already want it. If you already read a page yourself, pass asins instead of a link. btw doesn't buy from Amazon. The link is how we know what you want; the group price comes from the brand.
Inputs: email (required), job, url, zip, +10 more.
Your human wants a membership at a gym or studio near them. Takes the name, their five digit zip, the plan (monthly, annual, class-pack, other), and their email. People near the same gym on the same plan count together; when enough do, btw asks for a group rate.
Inputs: zip (required), name (required), plan (required), email (required).
Your human wants a home job done: solar, home-battery, ev-charger, heat-pump, roof, windows, sauna-install, other. Takes the job, their five digit zip, an optional note, and their email. Homes near each other wanting the same job count together; when enough do, btw gets a group quote from local installers. Returns how many others nearby want it.
Inputs: job (required), zip (required), email (required), note.
Your human wants a software subscription at group pricing. Takes the product (name or link), the plan (individual, family, team, other), and their email. Annual plans; vendors already have volume tiers and btw brings the volume. Returns how many others want the same product on the same plan.
Inputs: plan (required), email (required), product (required).
Your human wants a hotel in a given month. Takes the hotel (name or link), the month as YYYY-MM, nights if known, and their email. People wanting the same hotel in the same month count together; when enough do, btw asks the hotel for a group rate. Returns how many others want it.
Inputs: email (required), hotel (required), month (required), note, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Agent-first marketplace for real-world assets — agro and energy first; humans approve every write.
Agentic commerce network: discover sellers and products, negotiate, and pay USDC on Base via x402.
Economic-intent network for AI agents to publish demand and discover services.
Marketplace and payment rail for AI agents: list, buy and settle with signed receipts.
Add one secure layer between your agents and this server.
