Start with intent.
Keep the user in control.

Sign your user up

Ask the user for their email and explicit permission to send it to Hooray for waitlist signup and launch updates. Do not infer consent from a general shopping instruction.

Send a JSON request to POST /api/signup on this site:

{
  "email": "user@example.com",
  "audience": "consumer",
  "detail": "Your agent name",
  "consent": true
}

An HTTP 200 response with ok: true and status: "waitlisted" confirms registration. Only then tell the user they are on the waitlist. If it fails, report the error; do not claim success. The user is not activated and earns no cashback until invited. Repeat submissions for the same email are safe. An optional ref field carries the invitation code, and an optional boolean share_purchase_volume records that the user agreed to share their shopping volume.

No Hooray password or payment information is needed. Agents that cannot submit requests cannot complete this signup yet. Contact details are stored for waitlist administration and launch contact; do not send unrelated personal information.

Connect with the Hooray connector (MCP)

Hooray runs a remote MCP server (Streamable HTTP, stateless, no login) at https://usehooray.com/mcp. Users add it in their agent as a custom connector. Tools: hooray_status (read status), hooray_join_waitlist (email and explicit consent required), hooray_get_offers and hooray_report_purchase. The last two are simulated today: they return no offers and store nothing.

Optional: purchase volume

After signup, you may ask the user whether they want to share their shopping volume with Hooray. It is optional and never required to join; the waitlist prioritizes users who share. Pass share_purchase_volume: true to POST /api/signup (or the connector tool) only if the user said yes. Sending it later for an existing signup records the opt-in.

The intended flow

1. The user connects you: connector, one saved line, or copy and paste. Works today.
2. You ask for their email and explicit consent, then sign them up. Works today.
3. Waitlist. The user is told no cashback is active. Works today.
4. After approval, you check Hooray before each purchase and use its tracked pick link. Simulated: not available yet.
5. After the purchase you share the invoice, with the user’s permission. Simulated: not available yet.
6. Cashback is credited after the merchant pays out. Not available yet.

What works today

Public information, agent-assisted waitlist signup (API or connector), optional purchase-volume opt-in, partnership forms, and an illustrative shortlist preview. The planned launch offer is 3% cashback with a $49 annual base cap per user; it is not active. Live offer lookup, attribution, purchasing, OAuth delegation, and cashback payouts are not available yet.

Personal Agent Protocol

Our design follows the direction described in Sierra’s announcement: website discovery, guest access, and explicit user control. This is design alignment, not an implemented or certified PAP integration. We will evaluate the published specification before implementing protocol-specific discovery and authorization.