For merchants: issue MasaDeals a code
MasaDeals is a verified promo-code feed for AI shopping agents. When an agent reaches your checkout, it asks MasaDeals for one code that fits the cart — or accepts our certified answer that none does. The codes agents trust most are the ones a merchant issued to the publisher asking. This page is how to issue one to us.
The checkout moment, without an extension
Browser extensions earn their place by being installed before checkout. Agents have no install step — they call a feed. Ours is live: an MCP server and REST API at masadeals.com/mcp and /api/v1, listed on the official MCP Registry as io.github.MKagesawa/masadeals. An agent sends the merchant and the cart; we return up to three codes whose constraints already fit, ranked by recent verified checkout success, each with a dated verification receipt — or no_verified_code with the merchant’s test coverage, so the agent stops searching coupon sites for that cart.
Why issue a code instead of letting us find one?
- Addressed inventory works; scraped inventory mostly doesn’t. In our first verification round (October 31, 2026), codes sourced from merchants’ own pages verified 3 of 3 in real carts, while widely listed third-party codes failed at a rate the industry knows well: published measurement puts scraped-code success near one in four. A code you issue to MasaDeals is born into the channel agents actually query.
- Attribution without a click. A code issued to a specific publisher attributes the sale to that publisher when the code is used — including orders where no affiliate link was clicked first. That is how networks’ coupon-attribution programs already work, and it is the cleanest way to pay for agent-referred sales.
- You set the terms; we enforce them mechanically. Offer, dates, eligible categories, minimums, geography, customer type, stacking — constraints you state are checked against the cart before the code is ever returned, and the code is retired the day your terms say it ends or you tell us to pull it.
- Your public codes stop competing with themselves. Every code in the feed carries its provenance. A code issued to us is labeled issued; a code we merely found is labeled found, with its source and date. We never present a found code as issued, and we never publish another publisher’s exclusive code.
What you get back
- A verification receipt before serving. We test the issued code in a real guest cart under its stated conditions before it is served as an offer. If it does not apply, you hear that from us — with the cart’s own message — not from a customer.
- Outcome reporting. Agents that use the feed report every checkout attempt back through
report_outcome: accepted or rejected, the discount observed, the merchant’s rejection reason. Those reports keep the code’s success statistics current in public, dated form. - Freshness discipline. Verdicts decay. A code that stops being confirmed goes stale and stops being recommended; failing re-tests retire it. Your expired campaigns do not linger as zombie offers.
- Honest negatives. When no code is verified for a merchant, the feed says so — dated, with the test record behind it. Merchants in that position are not filled in with scraped guesses.
Commission never buys rank
Codes are ranked by observed checkout success — never by commission. That rule is published, and it is enforced by an automated test on the ranking function; see How We Verify and the Affiliate Disclosure. An issued code gets no ranking boost, no earlier “verified” label, and no protection from a negative verdict. What issuance buys is presence and attribution in the channel — the same deal an extension publisher gets, stated in the open.
What we ask
- A unique code string issued to MasaDeals — exclusive to us, or shared, as you prefer — with the offer stated in writing: discount, start/end dates and time zone, eligible products or categories, minimums, geography, customer type, and stacking rules.
- The attribution method: code-based attribution, a network program we join, or a tracked link — and the commission or bounty terms that go with it.
- Permission per surface, stated separately: this website, and our REST API / MCP answers to third-party shopping agents. If you authorize only the narrower surface, we serve only there.
- A change process: who to contact, and how much notice you will give before changing or killing the code, so no shopper meets a dead code we called verified.
If your program already runs on CJ, Awin, Rakuten Advertising, or impact.com, we can work inside that program instead — tell us the network and program name and we will apply there rather than asking for a side arrangement.
Where the program stands
Stated plainly: MasaDeals launched on October 30, 2026. The feed, the verification pipeline, the hosted endpoint, and the registry listing are live; the merchant-issuance program is new, and we are not claiming traffic figures or existing merchant partnerships we do not have. The first issuance conversations start now, ahead of the holiday catalog build. If your team wants the verification ledger behind the claims on this page, ask — it is the same record we publish from.
Contact: [email protected]. Page generated 2026-11-01 03:04:17 UTC.