Let your agent shop. With privacy focused human control.

A gateway that runs next to your agent. Your users’ data stays on your machine, and the card stays with the buyer.

View on GitHub

pre-alpha

planned setup

# 1 · run the gateway next to your agent
$ docker run -d -p 127.0.0.1:8787:8787 \
    -v intent-data:/data \
    ghcr.io/golden007eye/intent-gateway:0.1

# 2 · give your agent the shopping tools
$ claude mcp add intent --transport http \
    http://127.0.0.1:8787/mcp

› find running socks under $20
  ✓ 3 offers · cart ready · waiting for approval
  ✓ approved on phone · handed to store

PLANNEDNot released. Shape of the first build.

How it works

Three zones, one way through

Your agent never touches a card. Only allowed fields leave your machine. A person approves on intent’s page.

runs on your machineintent and the buyerdirection of data

Security and privacy

Safe by design, not by prompt

Each guard sits outside the model, so an injected instruction can’t talk its way past it.

No card in your agent

The buyer pays on the store’s own checkout. No card, wallet or keys ever reach your agent.

A person approves every order

On intent’s page, showing the store’s item and total, not your agent’s words. It can’t be turned off.

Your users’ data stays home

Your policy decides what leaves the gateway. Every field is logged on your machine before it’s sent.

Leaves your machine, if your policy allows

What to search for

query

Items in the cart

cart

A shipping region

region

Never sent to intent

Your users’ chats and agent context

—

Buyer name, address, email

store only

Card and payment details

store only

An account: the passkey is the only identity

—

Not a payment rail. intent doesn’t process payments or hold money. Spend caps and rate limits are enforced by Intent Cloud.

Be first to try the gateway

One email when the first build is ready. Nothing else.

Get the first build