Ask a merchant's haggl.ai sales agent for a personalized offer, then hand it to checkout.
ai.haggl/haggl MCP Server
This MCP server is an integration that connects to a merchant’s haggl.ai sales agent. It asks the agent for a personalized offer and then passes the resulting offer to checkout.
🛠️ Key Features
Uses haggl.ai sales agent to request a personalized offer
Hands the offer to checkout
🚀 Use Cases
Obtain merchant-specific, personalized offers via haggl.ai
Apply a returned offer during the checkout step
⚡ Developer Benefits
Provides a single flow from offer request to checkout handoff
Exposes a clear purpose tied to the haggl.ai “sales agent” workflow
⚠️ Limitations
The provided details only describe offer request and checkout handoff; other behaviors, tooling, and capabilities are not specified
Captured live from the server via tools/list.
haggl_list_vendors
List 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.
Parameters
No parameters.
Raw schema
{
"type": "object",
"properties": {}
}
haggl_start_negotiation
Start 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.
Parameters4
vendor_id
string
required
Vendor id from haggl_list_vendors, a haggl-vendor meta tag, or a haggl-negotiate URL.
data
object
optional
Optional available buyer context; together with ask, requests an opening quote in this same call.
ask
object
optional
Optional requested products, quantities or service, in the same shape as the haggl_submit_offer ask. Supply known context upfront.
haggl_id
string
optional
Optional: the user's haggl ID from haggl_create_haggl_id, so this offer and its code are kept with their other offers.
Raw schema
{
"type": "object",
"properties": {
"vendor_id": {
"type": "string",
"description": "Vendor id from haggl_list_vendors, a haggl-vendor meta tag, or a haggl-negotiate URL."
},
"data": {
"type": "object",
"description": "Optional available buyer context; together with ask, requests an opening quote in this same call."
},
"ask": {
"type": "object",
"description": "Optional requested products, quantities or service, in the same shape as the haggl_submit_offer ask. Supply known context upfront."
},
"haggl_id": {
"type": "string",
"description": "Optional: the user's haggl ID from haggl_create_haggl_id, so this offer and its code are kept with their other offers."
}
},
"required": [
"vendor_id"
]
}
haggl_search_catalog
Search 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.
Read 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.
Request 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.
Parameters4
session_id
string
required
Session id from haggl_start_negotiation or session.id from REST initialization.
expected_offer_version
integer
optional
Optional state.offer_version last read, to avoid submitting against a session changed by another actor.
data
object
optional
Optional buyer context and consented evidence. Omit or use {} for an opening quote without evidence.
ask
object
optional
What the buyer wants; the offer then says exactly which items the discount covers. Store catalogs: { items: [{ product_handle, quantity }] }. Campaign catalogs (catalog.type "campaign"): { items: [{ variant_id, quantity }] } or { recipe_id }, required for a campaign offer. Otherwise describe the product or service, e.g. { product }.
Raw schema
{
"type": "object",
"properties": {
"session_id": {
"type": "string",
"description": "Session id from haggl_start_negotiation or session.id from REST initialization."
},
"expected_offer_version": {
"type": "integer",
"minimum": 0,
"description": "Optional state.offer_version last read, to avoid submitting against a session changed by another actor."
},
"data": {
"type": "object",
"description": "Optional buyer context and consented evidence. Omit or use {} for an opening quote without evidence."
},
"ask": {
"type": "object",
"description": "What the buyer wants; the offer then says exactly which items the discount covers. Store catalogs: { items: [{ product_handle, quantity }] }. Campaign catalogs (catalog.type \"campaign\"): { items: [{ variant_id, quantity }] } or { recipe_id }, required for a campaign offer. Otherwise describe the product or service, e.g. { product }."
}
},
"required": [
"session_id"
]
}
haggl_accept_offer
Accept 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.
Parameters3
session_id
string
required
Session id of the negotiation to accept.
expected_offer_version
integer
required
state.offer_version from the quote reviewed and approved by the buyer.
round
integer
optional
Legacy offer round. If supplied it must match the current or already reserved offer.
Raw schema
{
"type": "object",
"properties": {
"session_id": {
"type": "string",
"description": "Session id of the negotiation to accept."
},
"expected_offer_version": {
"type": "integer",
"minimum": 1,
"description": "state.offer_version from the quote reviewed and approved by the buyer."
},
"round": {
"type": "integer",
"minimum": 1,
"description": "Legacy offer round. If supplied it must match the current or already reserved offer."
}
},
"required": [
"session_id",
"expected_offer_version"
]
}
haggl_search_discounts
Find 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.
Parameters1
query
string
required
A business name, website (e.g. "degrenne.fr") or kind of product.
Raw schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "A business name, website (e.g. \"degrenne.fr\") or kind of product."
}
},
"required": [
"query"
]
}
haggl_create_haggl_id
Create 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 retention and deletion rules in our privacy policy (https://www.haggl.ai/privacy). Your haggl ID expires 12 months after your agent last uses it to ask a merchant for an offer. It cannot be used or renewed after expiry and is then automatically deleted, usually within a day." If they decline, go on without a haggl ID. Send consent_version "2026-10-16.4" and statement: the user's words of agreement, quoted, without names or contact details. If the user is not in this conversation to read the text but their own standing instructions to you say they agree to this consent version, send channel "standing_instruction" with those words as the statement; otherwise use haggl_request_haggl_id_confirmation instead, then call this with its confirmation once they confirmed. The ID is returned once: keep it with the user's settings, and never share it with anyone else.
Parameters4
consent_version
string
optional
The consent text version the user agreed to: "2026-10-16.4".
statement
string
optional
The user's words of agreement, quoted (for example "Yes, I agree"); no names, emails or phone numbers.
channel
string
optional
How the user agreed: in this conversation (agent_relayed, the default), or in standing instructions they wrote to you beforehand (standing_instruction).
confirmation
string
optional
Instead of consent_version and statement: the confirmation from haggl_request_haggl_id_confirmation, after the user confirmed at its confirm_url.
Raw schema
{
"type": "object",
"properties": {
"consent_version": {
"type": "string",
"description": "The consent text version the user agreed to: \"2026-10-16.4\"."
},
"statement": {
"type": "string",
"maxLength": 200,
"description": "The user's words of agreement, quoted (for example \"Yes, I agree\"); no names, emails or phone numbers."
},
"channel": {
"type": "string",
"enum": [
"agent_relayed",
"standing_instruction"
],
"description": "How the user agreed: in this conversation (agent_relayed, the default), or in standing instructions they wrote to you beforehand (standing_instruction)."
},
"confirmation": {
"type": "string",
"description": "Instead of consent_version and statement: the confirmation from haggl_request_haggl_id_confirmation, after the user confirmed at its confirm_url."
}
}
}
haggl_request_haggl_id_confirmation
Get 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.
Parameters
No parameters.
Raw schema
{
"type": "object",
"properties": {}
}
haggl_get_my_offers
Read 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.
Have 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.
Parameters3
haggl_id
string
required
The user's haggl ID.
query
string
optional
What the user is after, e.g. "hotel in Barcelona, 4 nights in December". Sets the category when category is omitted.
category
string
optional
Optional: the brand index category, e.g. "travel".
Raw schema
{
"type": "object",
"properties": {
"haggl_id": {
"type": "string",
"description": "The user's haggl ID."
},
"query": {
"type": "string",
"description": "What the user is after, e.g. \"hotel in Barcelona, 4 nights in December\". Sets the category when category is omitted."
},
"category": {
"type": "string",
"description": "Optional: the brand index category, e.g. \"travel\"."
}
},
"required": [
"haggl_id"
]
}
haggl_delete_haggl_id
Delete 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.