MerchantPro for AI agents
MerchantPro is an e-commerce platform for managing storefronts, catalogs, orders, and customer data for online retailers running their own branded stores. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in MerchantPro.
Look up a product's inventory
Check a product's stock level and location before confirming to a customer that it can be fulfilled.
Pull a customer's order history
List a customer's past orders to answer a support question about a shipment, a read-only lookup.
Check recent orders for a location
List recent orders for a store location to summarize the day's activity for a manager, read-only.
10 MerchantPro actions, graded by risk.
Every MerchantPro action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
10Look things up. Allowed by default.
- merchantpro.get_productGet Product
- merchantpro.list_ordersList Orders
- merchantpro.get_inventoryGet Inventory Unit
- merchantpro.list_productsList Products
- merchantpro.list_customersList Customers
- merchantpro.list_locationsList Locations
- merchantpro.list_categoriesList Categories
- merchantpro.get_shop_taxonomyGet Shop Taxonomy
- merchantpro.list_catalog_partnersList Catalog Partners
- merchantpro.list_customer_subscriptionsList Customer Subscriptions
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
MerchantPro in three steps.
- 01Your users connect MerchantProThey add their MerchantPro api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls MerchantPro through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('merchantpro', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How MerchantPro connects.
Users add their MerchantPro api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same MerchantPro connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use MerchantPro from any agent.
MerchantPro and Arc0, answered.
Can I use MerchantPro with Claude, ChatGPT or Cursor?
Yes. Connect MerchantPro to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the MerchantPro actions you allow.
How do users connect MerchantPro?
Users add their MerchantPro api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which MerchantPro actions can my agent take?
10 in total: 10 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in MerchantPro?
Yes. Allow read actions and deny writes in the MerchantPro policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call MerchantPro too?
Yes. The same MerchantPro connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug MerchantPro into your agent.
Your users connect MerchantPro once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan