Retailed for AI agents
Retailed provides pricing and inventory data from resale marketplaces like StockX and GOAT, covering sneakers, streetwear, and luxury goods. 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 Retailed.
Check a product's market price
Get a StockX product's pricing before deciding how to list or value an item.
Compare prices across platforms
Get GOAT product prices alongside StockX data to see where an item sells for more.
Track usage before a big pull
Get API usage to confirm there's room left before running a large batch of price lookups.
6 Retailed actions, graded by risk.
Every Retailed action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- retailed.get_usageGet API Usage
- retailed.get_goat_pricesGet GOAT Product Prices
- retailed.search_productsSearch Products
- retailed.get_stockx_searchStockX Search
- retailed.get_stockx_trendsStockX Trends
- retailed.get_stock_x_productGet StockX Product
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.
Retailed in three steps.
- 01Your users connect RetailedThey add their Retailed 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 Retailed through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('retailed', { 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 Retailed connects.
Users add their Retailed 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 Retailed 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 Retailed from any agent.
Retailed and Arc0, answered.
Can I use Retailed with Claude, ChatGPT or Cursor?
Yes. Connect Retailed 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 Retailed actions you allow.
How do users connect Retailed?
Users add their Retailed 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 Retailed actions can my agent take?
6 in total: 6 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Retailed?
Yes. Allow read actions and deny writes in the Retailed policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Retailed too?
Yes. The same Retailed connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Retailed into your agent.
Your users connect Retailed once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan