Put real support behind a healthy action — for someone you love, or people you serve. This page is for sponsors. Everyday chat with Doc stays simple on the main app.
How a demand-side account works
On GreenDial, the supply side is the member who stakes leagues, tracks miles, and chats with Doc. The demand side is anyone who sponsors priced actions — fixed Universal Bounties or CPAA (cost per action) fitness payouts.
CPAA: set pricing_model: "cpaa", action_type (e.g. run_1mi, bike_3mi), and cpaa_rate. Members who complete matching GPS-tracked activities get paid per action — stack that on top of stake-league refunds so active players can earn more than they wager. See API docs.
Friends & family
Sign in with your GreenDial account on this page. Find someone who opted into discovery (or enter their username), draft a simple activity with AI help, choose one-time or recurring, and post. They see it as a priced suggestion in their app.
Institutions
Insurers, employers, and public programs use a demand-side X-API-Key to create UBs at scale via API — targeting known user_ids, previewing with /generate, and listing bounties programmatically. Full shapes live in the API docs.
Honor system: GreenDial records price, currency, and a wallet snapshot when the person completes the activity, and flags payment as pending. Settlement is off-platform today (you pay them how you already pay them). Not medical care; not escrow.
One-time bounty — offered once until they accept (or you delete it).
Weekly / monthly — after they complete one cycle, it can reappear for the next period.
Discovery — only people who turn on “Open to Universal Bounties” in Settings appear in the public directory. Everyone else can decline simply by leaving that off.
Create a bounty
Checking sign-in…
1. Find who to support
Search people who opted into the public bounty directory, or type a GreenDial username you already know.
Loading directory…
2. Describe the activity
Start typing — we suggest common healthy actions and a price. Default is intentionally simple.
API key workflow
For insurers, employers, and government programs. Request a key via the About FAQ email. Then integrate against the live API.
# Preview (profile-aware or description-first)
curl -X POST https://greendial.org/generate \
-H "X-API-Key: $DEMAND_API_KEY" -H "Content-Type: application/json" \
-d '{"user_id":"user_abc","description":"walk","recurrence":"weekly"}'
# Create
curl -X POST https://greendial.org/bounty \
-H "X-API-Key: $DEMAND_API_KEY" -H "Content-Type: application/json" \
-d '{"activity":"Take a walk sometime in the next day","health_area":"exercise",
"price":5,"currency":"USD","user_ids":["user_abc"],"recurrence":"once"}'
# Discover opt-in recipients
curl "https://greendial.org/bounty/directory?q="
# Autocomplete (no key)
curl -X POST https://greendial.org/bounty/autocomplete \
-H "Content-Type: application/json" \
-d '{"description":"sleep better","enrich":true}'
Member already uses GreenDial (or you onboard them to create an account).
You obtain a demand-side API key and map your member IDs to GreenDial user_ids (or usernames).
Optionally call POST /generate to preview wording from their health profile, or use /bounty/autocomplete for generic habits.
POST /bounty with user_ids, price, recurrence, and expiry. The member sees a priced suggestion (UB first in their list).
On accept → activity; on complete → wallet snapshot + payment_pending. Your ops settle payment off-platform and can mark paid in admin tools where applicable.
Weekly/monthly UBs re-surface after a completed cycle, so a subscription-style program needs only one bounty record.
Want to be findable by sponsors? In GreenDial → Settings → Universal Bounty → turn on “Open to Universal Bounties.” You can decline anytime by turning it off.