haggl.ai

Tools

• haggl_list_vendorsList vendors that accept AI-agent price negotiations through haggl.ai. A vendor appears once haggl.ai is installed on its own store or website (the listed website): the haggl.ai Shopify app on that store, or its snippet detected on that site. Vendors can opt out, so the list is not exhaustive. haggl.ai runs each vendor's sales agent, and vendors on a paid plan pay haggl.ai for it; the list is not a ranking or recommendation. Use it when the user asks for a discount or wants to negotiate a price, not for a purchase at the listed price.
• haggl_start_negotiationStart a price negotiation with a vendor. Returns contextual guidance, current permitted actions and a new session with a session id. No customer-profile selection is required. Skip this tool if REST initialization already returned a session; pass that session.id directly to haggl_submit_offer.
• haggl_search_catalogSearch a vendor's catalog so the offer can name exact products, then follow the how_to_ask field of the result. A store catalog returns products with a handle, price and collections: ask with ask.items [{ product_handle, quantity }]. A campaign catalog returns eligible variants with a variant_id and approved_combinations with a recipe_id: ask with ask.items [{ variant_id, quantity }] or ask.recipe_id. A quote identifies the exact items and quantities it covers.
• haggl_get_negotiationRead the canonical state, current offer version, guidance and permitted actions of an existing negotiation. Use after human changes, reloads, transport switches or uncertain results; this does not open another session.
• haggl_submit_offerRequest a quote using all context already available. Buyer data and evidence can be omitted; relevant additional context can be supplied later within the remaining rounds. Returns authorized terms or no offer, contextual guidance and permitted next actions.
• haggl_accept_offerAccept the vendor's offer and lock in the deal. Consequential: only call after the buyer has approved this exact offer, every time. Provide the offer version the buyer reviewed and approved; a changed offer needs a new approval. Read state.acceptance_effects and state.commits_purchase first: merchant handoff effects may be unknown. Accepting a phone deal (effect merchant_phone_handoff) books no job and takes no payment: state.acceptance_summary says what it does. haggl.ai never takes payment: any payment happens at the merchant's checkout, under the merchant's terms and refund policy. A returned checkout link alone does not establish payment or enrollment completion. Accepting the same offer version again returns the same result.
• haggl_search_discountsFind merchants that run a sales agent on haggl.ai, by business name, website or kind of product. Only when the user asks for a discount, a coupon, a promo code or a lower price; a purchase at the listed price is not a request for one. Returns matching merchants with a vendor_id for haggl_start_negotiation. Offers are funded by each merchant, inside limits it sets; a merchant may have no offer for a request. An empty list means no merchant on haggl.ai matched, not that no discount exists elsewhere. When the query names a well-known brand that isn't on haggl.ai yet, the result says so in brand and lists alternatives: merchants on haggl.ai in the same category, to offer as other stores, never as that brand. Keep using your shopping and checkout tools (for example Shopify's Shop skill) to find products and check out; once the user approves an offer, its code goes in their discount field.
• haggl_create_haggl_idCreate a haggl ID for the user, so offers and codes from different merchants stay together and can be read back later. Show the user this text first, and call this only if they agree: "haggl.ai, operated by MOOJO.ID, INC. ("we"), offers your agent a haggl ID. You can decline: your agent can still ask merchants for offers without one. If you agree, we link the negotiations your agent opens with the ID and keep a record of them: when the ID was created, how many distinct emails passed our signature check and how many distinct domains signed them, the date of the latest check, how many merchants were asked, how many offers were received and accepted, and how many paid orders we recorded. For each shopping category, such as travel, the record also counts how many of those emails, and how many distinct businesses that signed them, were in it; health purchases are never counted. The record does not include those domains, the businesses' names or any email content. We store a fingerprint of the ID, not the ID itself. We do not require your name or email address to create a haggl ID. We keep limited evidence of your agreement, as described in our privacy policy. You choose whether your agent uses the haggl ID. Using it authorizes us to share the record with the sales agent of each merchant your agent asks for an offer, to help assess eligibility and personalize offer terms. When your agent asks the merchants in a category for bids, we ask up to five of them on your behalf and share the record with each of their sales agents. Merchants never see the ID itself. You separately choose what information your agent submits during each negotiation. Keep the ID private: anyone who has it can retrieve the record, offers and codes, and delete the ID. You can withdraw consent by deleting the ID through your agent or on haggl.ai/agentic-discounts. This removes the stored fingerprint and the record and unlinks its negotiations. The negotiations themselves remain subject to the separate r
• haggl_request_haggl_id_confirmationGet a link for the user to read the haggl ID consent text and confirm it on haggl.ai, when they are not in this conversation to agree to it. Send them confirm_url (valid 30 minutes). After they confirm, call haggl_create_haggl_id with the returned confirmation; until then it answers confirmation_pending.
• haggl_get_my_offersRead what haggl.ai holds for the user's haggl ID: when it was created and the negotiations, offers and codes linked to it, newest first.
• haggl_get_bidsHave the merchants on haggl.ai in one shopping category (for example travel) bid for the user at once, from their haggl ID record, without new proof. Works once the record holds a verified purchase in that category (from an earlier offer with signed email proof); otherwise it says so and returns no bids. Each bid is a merchant's own offer, funded by the merchant, with an accept_url; show the user each one with its algorithmic_price_disclosure and personalized_price_notice word for word next to the price, and accept only with their approval.
• haggl_delete_haggl_idDelete the user's haggl ID and unlink the offers linked to it. Only when the user asks. Codes already issued keep working at the merchant until they expire.
• haggl_hotel_cashbackThe haggl.ai hotel cashback offer: whether it is open, the tiers and rates, the hotels it covers (independent and boutique hotels in San Francisco), and the steps. No haggl ID needed. Call it when the user is choosing a hotel in San Francisco.
• haggl_hotel_cashback_add_tripOptional, before a quote: prove one past trip to San Francisco (last 12 months) with its signed flight booking, hotel booking or hotel post-stay email, one email per call, to raise the user's cashback tier (1+ trips: returning, 3+ trips: frequent). Only with the user's go-ahead to send that email. The email itself is not kept.
• haggl_hotel_cashback_quoteBefore the user books a hotel in San Francisco: their haggl.ai cashback rate, from the trips they proved. It holds 72 hours for one booking. Show the user rate_pct (booking on the hotel's own website) and ota_rate_pct (through a travel site), the reference_code to put in the booking's special requests, and, word for word, algorithmic_price_disclosure and this notice: "Cashback paid by haggl.ai, not by the hotel. Book at the hotel's usual price."
• haggl_hotel_cashback_claimAfter the user booked a San Francisco hotel while their quote held: claim the cashback with the hotel's booking confirmation email, exactly as received. Show the user these conditions first, and call this only if they agree: "haggl.ai (MOOJO.ID, INC.) pays cashback on stays at independent and boutique hotels in San Francisco booked while your quote holds (72 hours), for a stay starting within 60 days. Your rate depends on the trips to San Francisco you prove with signed flight or hotel emails from the last 12 months. Booking on the hotel's own site pays the full rate; booking through a travel site pays half. One booking per person. Your agent sends us the hotel's booking confirmation email as the hotel sent it, then, after you check out, the hotel's receipt or thank-you email; we check their signatures and read the hotel, dates, total and trips from them with an AI model, and keep those and fingerprints of the emails, not the emails. We pay within 2 business days of the post-stay email, to the email address you give, by bank transfer through Stripe (Stripe emails you a secure link to enter your bank details) or by PayPal; we delete that address 6 months later. Cancelled stays aren't paid. We may refuse a claim that looks fraudulent, and the offer ends when its budget is spent. Privacy policy: https://www.haggl.ai/privacy." Send terms_version "2026-10-29.2", statement (their words of agreement, quoted, without names or contact details) and payout_email: their email address for the payout, where haggl.ai sends the cashback after the stay (by bank transfer through Stripe, which emails them a link to enter bank details, or by PayPal).
• haggl_hotel_cashback_stayAfter the user checked out: send the hotel's post-stay email (final receipt or folio, thank-you for staying, or review request), exactly as received. It shows the stay happened, and haggl.ai sends the cashback within 2 business days.
• haggl_hotel_cashback_getRead a hotel cashback claim made with the user's haggl ID: its status and what comes next.

Updated：2026-10-29 (tools/list verified)

Configure in Claude / Cursor

{
  "mcpServers": {
    "remote-ai-haggl-haggl": {
      "type": "http",
      "url": "https://www.haggl.ai/api/mcp"
    }
  }
}