Packet vs Retailed.io
How Packet and Retailed.io compare on StockX and GOAT data, marketplaces, sales history, price per 1,000 requests and rate limits.
On this page
- At a glance
- Price per request
- StockX and GOAT data
- Marketplaces and sites
- Developer experience
- Which one should you choose?
- FAQ
- Is Packet cheaper than Retailed.io?
- Does Retailed.io have a free plan?
- Which API has StockX sales history?
- Which API covers more websites?
- Can I switch from Retailed.io to Packet?
- Are Packet or Retailed.io affiliated with StockX or GOAT?
Packet (pckt.sh) and Retailed.io both sell API access to product and price data from resale marketplaces and retailers. They overlap on StockX, GOAT, Chrono24, Nike and Shopify, but they're built for different jobs.
- Packet is a market data API for resale. It goes deep on sneaker and streetwear marketplaces: asks and bids per size, checkout prices with fees, and full sales history. Requests are cheap enough to poll prices at scale.
- Retailed.io is first a reselling app (inventory, sales and expense tracking) with a data API alongside it. Its API reaches more fashion and luxury retailers, and it builds scrapers for new sites on request.
Short answer: for StockX, GOAT and other resale marketplaces, especially sales history or high request volumes, Packet costs roughly 5 to 7 times less per request. If you need retailers like Zara, Zalando, Farfetch or Dior, or a custom scraper, Retailed.io covers sites Packet doesn't.
We make Packet, so read this with that in mind. Every figure about Retailed.io comes from its public pricing page and documentation, checked on 13 November 2026.
At a glance
| Packet | Retailed.io | |
|---|---|---|
| Focus | Resale market data API | Reseller app, plus a data API |
| Free tier | 500 credits every month, plus up to 550 bonus credits | 50 credits, once |
| Entry plan | $39 / month, 50,000 credits | $49 / month, 18,000 credits |
| Cost of a StockX request | 1 credit live, 0.4 cached | 2 credits |
| StockX requests per month on the entry plan | 50,000 live or 125,000 cached | 9,000 |
| Rate limit | 1 to 25 requests / second | 7 to 30 requests / second |
| Unused credits | Stay on your balance | Reset every billing period |
| Top-ups | Yes, on every plan | Not listed |
| Endpoints available today | 58, across 15 marketplaces and Yahoo Finance | 21, with 94 more built "on request" |
| Custom scrapers | No | Yes, a setup fee may apply |
| SDK and spec | TypeScript SDK, OpenAPI spec, gRPC (Business and up) | Postman collection |
| Bulk datasets | StockX and GOAT as CSV or JSONL | Sneaker database API |
Price per request
Both use credits, but the same credit buys a different amount of data. On Retailed.io, StockX endpoints cost 2 credits because they need JavaScript rendering; standard endpoints cost 1. On Packet, a live StockX or GOAT request costs 1 credit, and the cached catalog costs 0.4 credits.
Here's what a month of live StockX requests costs on comparable plans:
| Budget | Packet | Retailed.io |
|---|---|---|
| ~$40 to $50 | Developer, $39: 50,000 requests, 4 req/s | Premium, $49: 9,000 requests, 7 req/s |
| ~$100 to $120 | Business, $119: 150,000 requests, 10 req/s | Premium+, $99: 20,000 requests, 10 req/s |
| ~$250 | Business + top-ups | Startup, $249: 55,000 requests, 15 req/s |
| ~$450 to $500 | Scale, $449: 600,000 requests, 25 req/s | Startup+, $499: 115,000 requests, 20 req/s |
| Per 1,000 StockX requests | $0.75 to $0.79 live, $0.31 cached | $3.77 to $5.44 |
Two more differences add up over a few months:
- Credits. Retailed.io credits reset at the start of each billing period. Packet credits stay on your balance until you use them.
- Running out. On Packet, any plan can buy a top-up, and paid plans can turn on automatic refills. Retailed.io's pricing page doesn't list top-ups, so you'd move up a plan.
Where Retailed.io is ahead: rate limits per dollar. Its $49 plan allows 7 requests per second against 4 on Packet's $39 plan, and its top plans go up to 30. If you send small bursts of very few requests, that matters more than the cost per request.
StockX and GOAT data
Both APIs return StockX and GOAT products with per-size prices, and both accept a country and currency. The difference is depth.
| Data | Packet | Retailed.io |
|---|---|---|
| Search, product, per-size prices | Yes | Yes |
| Asks and bids, per size | Full list of asks and bids | Lowest ask, highest bid and counts |
| Checkout price with fees | Yes, /v1/stockx/subtotal |
Not documented |
| StockX sales history | Every sale, paginated, plus daily averages | Last sale and number of sales in 72 hours |
| GOAT sales history | Yes, /v1/goat/history |
Not documented |
| Trending products | No (related products only) | Trending by category |
| Full catalog crawl | Yes, cursor-paginated cached catalog | Through the sneaker database API |
If you're building a price tracker, an arbitrage tool or anything that charts prices over time, sales history is usually the deciding factor.
Marketplaces and sites
Both: StockX, GOAT, Chrono24, Nike, Shopify.
Only on Packet:
- Resale marketplaces: Alias, Flight Club, Poizon, KREAM, Novelship, Kicks Crew
- Drops: SNKRS feed, threads and upcoming launches
- Second-hand: Vinted, Grailed
- Other: Amazon search, Yahoo Finance (securities and exchange rates)
- Shopify: any store URL, live or from the cached catalog
Only on Retailed.io (live today): Stadium Goods, Farfetch, Zalando, Zara, UNIQLO, Forever 21, Dior, Macy's and Best Buy, plus UPC and EAN barcode lookups.
On request at Retailed.io: 94 more endpoints, including Adidas, ASOS, Depop, Etsy, H&M, JD Sports, SHEIN, Supreme and Louis Vuitton. These are built when a customer asks, and a setup fee may apply.
Developer experience
| Packet | Retailed.io | |
|---|---|---|
| Authentication | Authorization: Bearer header |
x-api-key header |
| Spec | OpenAPI | Postman collection |
| SDK | TypeScript | Not listed |
| Protocols | REST; gRPC on Business and Scale | REST |
| Response times | Under 300 ms live, under 100 ms cached | Not published |
Which one should you choose?
Choose Packet if:
- you need StockX, GOAT or other resale marketplaces, especially Alias, Poizon, KREAM or Novelship;
- you need sales history, asks and bids, or checkout prices;
- you send more than a few thousand requests a month and cost per request matters;
- you want a free tier that refills every month.
Choose Retailed.io if:
- you need fashion or luxury retailers such as Zara, Zalando, Farfetch or Dior;
- you want a scraper built for a site nobody covers yet;
- you also want an inventory and sales tracker for your reselling business;
- you need the highest per-second rate limits on a small budget.
FAQ
Is Packet cheaper than Retailed.io?
For StockX, yes. A live StockX request costs about $0.78 per 1,000 on Packet and $3.77 to $5.44 per 1,000 on Retailed.io, depending on the plan. For cached StockX data, Packet costs about $0.31 per 1,000.
Does Retailed.io have a free plan?
Retailed.io gives 50 credits once, as a trial. Packet's Free plan gives 500 credits every month, plus up to 550 bonus credits for new accounts.
Which API has StockX sales history?
Packet returns every StockX sale, paginated, and daily averages. Retailed.io's StockX product endpoint documents the last sale and the number of sales in the past 72 hours.
Which API covers more websites?
Retailed.io lists more sites, mostly fashion retailers, but most of them are built on request. Packet has more resale marketplaces live today, including Alias, Poizon, KREAM, Novelship and Vinted.
Can I switch from Retailed.io to Packet?
Yes. Both are REST APIs with an API key. Packet uses a Bearer token and query parameters, and its endpoints are documented in an OpenAPI spec you can generate a client from.
Are Packet or Retailed.io affiliated with StockX or GOAT?
No. Both are independent services and aren't affiliated with, endorsed by or sponsored by the marketplaces they provide data for. All trademarks belong to their owners.
Create a free Packet account · Compare plans · StockX API · GOAT API