Your own agents

Overview

Use Claude, ChatGPT, Cursor or any agent you like.

Prezense's own agents are built in, but you don't have to use them. Any agent that supports MCP, the standard way AI apps connect to other services, can run your store and build your storefront through the same two servers Prezense's agents use.

Your own agent works with the same data, the same storefront hosting and the same checks as ours. You pay your agent's provider for it, not Prezense credits.

Two servers

Both addresses are in the Prezense app under Settings → Your own agents, with copy buttons.

Mixing agents

You can switch whenever you like: ask Prezense's agents one day and Claude the next. Your store's data is the same either way. The one thing that isn't shared is storefront code: Prezense's builder keeps its own copy, so pick one place to build your site (see Publishing from your computer).

Shoppers can use their own assistants too, to buy from your store without visiting it. That's agent checkout, further down this page.

Running your store

Connect the store server and ask your agent anything.

Once connected, your agent can do almost everything Prezense's agents can: look up orders, fulfil and refund them, add products, create discounts, edit emails, read your analytics and more. It works on one store per connection.

Connecting

1. 01Copy the store server's address

   In the Prezense app, open Settings → Your own agents and copy the store server address.

2. 02Add it to your agent

   Add it as a custom connector or MCP server. In Claude, that's under Settings → Connectors. In ChatGPT, turn on developer mode under Settings → Apps & Connectors, then create a connector. In Cursor, Claude Code and similar tools, add it as a remote MCP server.

3. 03Sign in with Prezense

   Your agent opens a Prezense sign-in page. Sign in as usual, then choose the store and how much the agent can do.

Access levels

You choose a level when you connect. Your agent only sees the tools that level allows, and tools that do something you can't undo are marked so your agent asks before using them.

To change the level, disconnect and connect again. Publishing, rolling back, taking the store offline and domains stay in the Prezense app.

Team members

Team members with agent access can connect their own agents too. They only get the areas you gave them, whatever level they pick, and their changes appear in your team's activity, marked “Own agent”. Removing someone or changing their areas applies to their connected agents straight away. See Account & billing.

Disconnecting

Settings → Your own agents lists every app connected to your stores, who connected it and when it was last used. Disconnect stops it at once. A connection you don't use for 60 days ends by itself.

Building your storefront

Let your coding agent build the site on your computer.

Coding agents such as Claude Code, Cursor and Codex can build your storefront on your own computer. The docs server tells them how: which APIs to call for products, cart, checkout, search and the rest, and the exact fields each returns.

Connecting the docs server

Add the docs server's address from Settings → Your own agents as an MCP server in your coding tool. It needs no sign-in. Then tell your agent what you want; it reads the setup guide on its own.

Your store's keys

Your storefront needs your store's keys to load its products. In Settings → Your own agents, choose Show keys and copy the block into a file called .env.local in your storefront's folder. Paste it yourself rather than into a chat: the API key gives full access to your account. Add a Stripe test key there too, so you can try checkout with Stripe's test cards.

When you publish, Prezense gives the live site your keys and your main Stripe key itself, so .env.local is never uploaded.

Frameworks

Publishing from your computer

One command puts your storefront live.

From your storefront's folder, run this, or ask your agent to:

Terminal

1

npx prezense deploy

It uploads your code, builds it on Prezense and switches your store's address to the new version, the same way the Publish button does. Your live site stays up while it builds, and a failed publish changes nothing. It prints your live address when it's done.

Before you publish

Before every publish, your agent checks your storefront against Prezense's pre-launch checklist, the same one Prezense's own agent uses. It's in the docs MCP server as guides/pre-launch-checklist. A store is ready when it has:

• Prezense analytics on every page and action, so your Analytics page shows real numbers
• Products, cart and checkout loaded live from Prezense, never copied into the code
• An order tracking page, where customers look up their order
• A returns page, where customers request and follow a return
• A cart page that cart recovery emails can open
• The fraud check at checkout
• Pages for your collections, blog posts and gift cards, if you have them

If anything is missing, your agent tells you and offers to build it before publishing. You can still tell it to publish anyway.

What gets uploaded

Your source code only. Installed packages, build output, .git and every .env file stay on your computer. The command publishes to the store whose keys are in .env.local, so a project can only ever publish to its own store.

Prezense's builder keeps its own copy

Publishing from your computer replaces your live site, but not the code in Prezense's preview. If you go back to building in Prezense, its agents work on their own copy, and their next publish replaces yours. Rolling back, taking your store offline and custom domains work the same either way, from the Publish menu. See Publishing.

Agent checkout

Let shoppers buy through their own AI assistants.

More shoppers ask assistants like Gemini, ChatGPT and Claude to find and buy things for them. With agent checkout on, those assistants can search your products, build an order, quote shipping and tax, and place it, without the shopper visiting your site.

It uses the Universal Commerce Protocol (UCP), the open standard assistants use to shop. Prices, discounts, stock, shipping rates and fraud checks work exactly as on your storefront, and the money goes to your own Stripe account.

Turning it on

Open Settings → Agent checkout and switch on Let AI assistants buy from your store, or ask agents to do it. Your store needs to be published, with your main Stripe key added. Assistants find it at your store's address, followed by /.well-known/ucp.

How shoppers pay

Your Stripe business profile ID starts with profile_ and is in your Stripe Dashboard's agentic commerce settings. If an order can't be placed after payment, the shopper is refunded in full automatically.

What you see

Orders arrive with the rest, with the usual confirmation email, and are marked as placed through an AI assistant. Fulfil, refund and return them as normal. Taking your store offline stops agent checkout too. See Orders & fulfilment.