wudls.

APIs and MCP for dispensaries Build what is yours. Plug in what takes years to earn.

AI coding tools have made it realistic to build your own POS add-ons, menus, apps and dashboards. Do it. Then plug wudls in for the parts that take years to earn, and let your code and the AI you already use run them.

What you build, and what you plug in

Your build list is the part only you can design: the add-on your budtenders asked for, a menu that looks like your store, the dashboard your team checks every morning. The plug-in list is the part that does not come out of a weekend of prompting.

01

Sending reputation

Each store sends email from its own dedicated IP. Warm-up runs automatically, and sending pauses itself on complaint or bounce spikes.

02

Wallet passes and pushes

Signed Apple and Google Wallet cards with points and today's deal, artwork you change remotely, lock-screen notifications, claim links and QR sign-up.

03

Loyalty sync

Points and tiers kept in sync with your POS and shown on the card in your customer's phone.

04

Opt-out sync

Email goes only to opted-in people, every email carries an unsubscribe link, and unsubscribes stay in sync with Alpine IQ.

05

Purchase attribution

Which send moved which register ticket, dollar by dollar, at 1, 7 and 14 days.

Two ways in: MCP for your AI, REST for your code

Both are live. The MCP server covers Wallet cards and email; the partner REST API covers loyalty. Keys and docs come with your store's setup. More on the AI side on the MCP and AI control page.

Live · for your AI

MCP server

One server address for the AI you already use: Claude, ChatGPT, Codex, Cursor or another MCP client, connected with your store's key.

Wallet tools

  • Push offers to installed cards
  • Compose the promo image
  • Create claim links
  • Sync points
  • Schedule pushes
  • Read and change the card design
  • Install and campaign stats
  • Budtender attribution

Email tools

  • Create a campaign from your own HTML
  • Preview and build audiences
  • Send a test
  • Schedule and cancel
  • Repeat weekly
Live · for your code

Partner REST API

For the software you write: a POS add-on, an app or a dashboard that needs loyalty. Scoped keys cover members, points and wallet passes, so each tool gets only the access it needs.

  • Members
  • Points
  • Wallet passes
  • Scoped keys per tool

Guardrails before anything reaches a customer

  • Each store gets its own API key, stored hashed and revocable at once.
  • Every key has an access level: full, wallet only or email only.
  • Every call is rate-limited and written to an audit trail.
  • Anything that would reach customers returns a dry-run preview first and runs only after an explicit confirmation.
  • Real email sends go only to opted-in people, always with an unsubscribe link.

It is the same discipline we apply to sending: automatic warm-up, and a pause on complaint or bounce spikes, explained on the deliverability page.

What it looks like from your own AI

YouTonight at 5 pm, push the 20% off pre-rolls deal to everyone with our card. Tomorrow at 10 am, send the email we just designed to opted-in customers who haven't bought in 30 days.
Your AIDry run, nothing sent yet. Wallet: the offer tile with the pre-roll photos, to 1,180 installed cards at 5:00 PM store time, with a lock-screen notification. Email: a campaign built from our HTML, to 2,340 opted-in customers with no purchase in 30 days, tomorrow at 10:00 AM, unsubscribe link included. Send a test email to you first?
YouYes, send me the test.
Your AITest sent to your inbox. Ready to schedule the push and the email. Confirm?
YouConfirm.
Your AIBoth scheduled and written to the audit trail. I can pull install and campaign stats once they go out.

Illustrative session with a sample store. A real dry run shows your store's own counts.

Where we fit next to other cannabis tools

Most stores use more than one tool, and your AI can connect to several at once. Here is how we see the cannabis options, including two of our own.

Texting

Blackleaf, Springbig and AIQ

All three sell texting, and Blackleaf also sells a Regulated SMS API and a Messaging API for POS and software vendors. If texting is your core channel, start there; ours is an optional add-on in early access (see pricing). See wudls vs Blackleaf.

Loyalty

AIQ and Springbig

Both run cannabis loyalty programs. wudls keeps points and tiers in sync with your POS on Apple and Google Wallet cards, and runs next to AIQ with unsubscribes kept in sync. See vs Alpine IQ and vs Springbig.

POS data for your AI

Flowhub's MCP connector

Flowhub offers an MCP connector so AI tools such as ChatGPT, Claude and Gemini can work with a store's Flowhub data; write actions need the store's approval. Dutchie, Treez, Cova and Dispense have APIs too, and wudls connects to all five.

Market data

Hoodie Analytics

Hoodie Analytics offers an MCP connection to its cannabis market data, for questions about the wider market rather than your own store.

In-store screens

DopeCast

Our sister product: TV menu boards that update themselves from your POS, on the TVs you already have. Read menu screens for a custom POS.

Frequently asked questions

Build your part. Plug in ours.

Book 20 minutes. We'll connect your AI to the MCP server, run a dry-run push and a test email, and show you the audit trail behind them.

Book a DemoSee Pricing