Retailed is a global developer-first platform providing retail and resale marketplace APIs with access to product data, pricing information, and inventory management from major platforms like StockX, GOAT, Chrono24, and 50+ retail websites including sneakers, streetwear, watches, and luxury goods.
Retailed is a global developer-first platform providing retail and resale marketplace APIs with access to product data, pricing information, and inventory management from major platforms like StockX, GOAT, Chrono24, and 50+ retail websites including sneakers, streetwear, watches, and luxury goods. On Nagent, Retailed is exposed as a fully-configurable ecommerce integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Retailed into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Retailed to automate the kinds of tasks ecommerce teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Retailed into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Retailed, with input parameters and output schema. Drop these into any step of an agent built in Helix.
RETAILED_GET_GOAT_PRICESTool to retrieve pricing information for a specific product on GOAT. Use when you need up-to-date size-based pricing. Call after confirming product_id.
Input parameters
Specific product size (if applicable).
Country/market code for pricing (e.g., 'US', 'UK', 'EU').
GOAT product ID to fetch prices for. Use numeric ID like '719082' or product slug.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
RETAILED_GET_STOCK_X_PRODUCTTool to retrieve detailed StockX product information, including variant-level data. Use when you need comprehensive metadata from StockX by SKU or URL. Response is structured per variant; aggregate price or inventory metrics across variants only after grouping by variant to avoid distortion.
Input parameters
StockX product SKU identifier StockX-specific; may not match SKUs from other marketplaces (e.g., GOAT). Normalize identifiers before cross-platform comparisons.
Direct StockX product URL
Whether to include detailed market data
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
RETAILED_GET_STOCKX_SEARCHTool to search StockX marketplace for products and pricing information. Use when you have a search term and need up-to-date listings on StockX. Note: SKU identifiers and size labels in results may differ from other marketplaces (e.g., GOAT); normalize these fields before cross-platform price comparisons.
Input parameters
Page number for pagination (default: 1)
Number of results per page (default: 10)
Search term for StockX products
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
RETAILED_GET_STOCKX_TRENDSTool to get the latest trending products from StockX. Use when you want to discover current trending items.
Input parameters
Page number for pagination (default: 1)
Sort order (ascending or descending)
Sort field (e.g., popularity, price)
Number of results per page (default: 20)
Filter by product type (e.g., sneakers, streetwear)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
RETAILED_GET_USAGETool to retrieve current API usage statistics. The only mechanism to check remaining API credits; call proactively before long-running analyses to prevent mid-run quota exhaustion.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
RETAILED_SEARCH_PRODUCTSSearch for products in Retailed database matching query criteria. Uses Retailed's granular querying language with support for filtering by name, SKU, brand. SKUs and size labels are not standardized across sources; normalize product IDs and size labels before comparing results across marketplaces.
Input parameters
Page number for pagination (default: 1).
Field to sort by. Prefix with '-' for descending order.
Number of products per page (default: 10, max: 100). Queries with many matches silently return only the first page; always manage `page` and `limit` explicitly when iterating full result sets.
Filter by domain (e.g., 'stockx.com', 'goat.com').
Filter by source/marketplace name (e.g., 'stockx-us', 'goat-us').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 70 agents privately built on Nagent that already use Retailed.
Build on Nagent
Connect Retailed to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Retailed, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Retailed is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Retailed is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Retailed steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Retailed event fires, the agent kicks off automatically.
Every Retailed action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Retailed ships with 6 pre-built ecommerce actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Retailed together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Retailed-based workflows tailored to your business.