# Costco US Licensed Feed Qualification (`dromb/costco-us`) Actor

Search Costco US products, resolve the nearest warehouses from a ZIP code, and collect public online prices, local warehouse prices, stock signals, brands, sizes, categories, images, ratings, and product mappings. Use it for regional price comparison, assortment research, product matching.

- **URL**: https://apify.com/dromb/costco-us.md
- **Developed by:** [Dmitriy Gyrbu](https://apify.com/dromb) (community)
- **Categories:** Automation, Developer tools, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.30 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Costco US Products, Prices & Warehouse Finder (Unofficial)

Search Costco US products, resolve the nearest warehouses from a ZIP code, and collect public online prices, local warehouse prices, stock signals, brands, sizes, categories, images, ratings, and product mappings. Use it for regional price comparison, assortment research, product matching, and local availability analysis.

This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by the retailer.

### Operations

- `search`: lightweight product cards for a shopper query. Requires `query`; optional `limit`.
- `item`: the richest exact public product card available. Provide `productId` or `url`.
- `batch`: bounded item lookups. Requires `productIds`; optional `limit`.
- `warehouses`: nearest Costco locations with address, distance, coordinates, hours, phone, and services. Uses `postalCode`.

For product operations, `postalCode` is normally all you need. The Actor resolves the nearest warehouse and state through Costco's public locator, then applies that context to prices and availability. `shipToState`, `warehouseId`, `productWarehouseNumber`, and `deliveryLocationIds` remain available as advanced manual overrides.

### Quick start

```json
{
  "operation": "search",
  "query": "coffee",
  "postalCode": "60601",
  "limit": 10
}
```

Use the returned `id` with item:

```json
{
  "operation": "item",
  "productId": "ID_FROM_SEARCH"
}
```

Find nearby warehouses:

```json
{
  "operation": "warehouses",
  "postalCode": "10001",
  "limit": 5
}
```

### Normalized product card

Every dataset row follows one consumer contract:

- Identity: `id`, optional `sku` and `barcode`, `name`, `brand`, `source_url`.
- Price: `price` is the verified Costco.com price for the postal context. `warehouse_price` is the separately verified price for `warehouse_id`; it is never mislabelled as an online discount. `discount_price` appears only for a verified lower price in the same channel.
- Unit comparison: `price_per_unit_price`, `price_per_unit_quantity`, `price_per_unit_unit`, and `size`.
- Discovery: `category`, `category_id`, and `breadcrumbs` when exposed by the public source.
- Promotion: `promotion_type`, `promotion_label`, `multi_buy`, and promotion dates when exposed.
- Availability: `availability`, `stock_status`, `in_stock`, `fulfillment_options`, and explicit price/location/warehouse scopes.
- Media and trust: `image`, `images`, `rating`, `review_count`, `source`, `retrieved_at`, and `data_quality_warnings`.
- Item enrichment: `description`, `ingredients`, `allergens`, `nutrition`, `specifications`, and `variants` only when the exact public item provides them.

Empty optional fields are omitted. The Actor never copies facts from a similar product and never invents a price, barcode, promotion, availability, ingredient, or specification.

### Search versus item

Search intentionally stays lightweight and fast. Item may make additional public requests to enrich the exact product. A warning explains when protection or source limitations force an item result to use verified listing-level data.

### Output and export

Product, offer, and store rows are written to the default dataset. Store rows use `record_type: "store"` and include the resolved warehouse context. The `OUTPUT` key-value record contains run status, counts, source-call totals, warnings, and structured errors. Export the dataset as JSON, CSV, Excel, XML, or RSS through Apify.

### Limitations

Costco.com and physical-warehouse prices can differ by location. The Actor keeps them in separate fields and attaches both requested ZIP and effective warehouse context. Member-only prices are never inferred; missing or rejected enrichment is disclosed in `data_quality_warnings`.

Public websites change. Run bounded tests before depending on a field, respect the retailer's terms, and use the data only where lawful.

# Actor input Schema

## `operation` (type: `string`):

Choose a consumer workflow. Search returns product cards; item returns the richest exact card; batch performs bounded lookups; warehouses finds nearby Costco locations by ZIP code.

## `query` (type: `string`):

Required for search. Use the same words a shopper would enter on the retailer website.

## `productId` (type: `string`):

Required for item unless url is provided. Use the retailer product identifier returned as id.

## `url` (type: `string`):

Optional item input. A public product URL alternative to productId.

## `productIds` (type: `array`):

Required for batch. Up to 50 exact IDs or public URLs returned by search.

## `limit` (type: `integer`):

Optional explicit cap for customer-visible dataset rows. If omitted, the complete selected native source page or response is preserved; item naturally returns at most one row.

## `postalCode` (type: `string`):

Public Costco ship-to postal context.

## `autoResolveLocation` (type: `boolean`):

Recommended. Resolves the nearest Costco warehouse and state from postalCode for store-aware price and availability.

## `shipToState` (type: `string`):

Advanced override. Two-letter US state code; normally resolved automatically from postalCode.

## `warehouseId` (type: `string`):

Advanced override for the public GDX warehouse context. Leave empty to resolve the nearest warehouse from postalCode.

## `productWarehouseNumber` (type: `string`):

Public product GraphQL warehouse context.

## `deliveryLocationIds` (type: `array`):

Advanced override. Leave empty for automatic postal-to-warehouse resolution. When provided, these IDs and the manual warehouse/state context are used as-is.

## Actor input object example

```json
{
  "operation": "search",
  "query": "coffee",
  "postalCode": "95050",
  "autoResolveLocation": true,
  "productWarehouseNumber": "847"
}
```

# Actor output Schema

## `results` (type: `string`):

Normalized product or warehouse rows.

## `summary` (type: `string`):

Status, counts, warnings, and structured errors stored under OUTPUT.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "coffee"
};

// Run the Actor and wait for it to finish
const run = await client.actor("dromb/costco-us").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "query": "coffee" }

# Run the Actor and wait for it to finish
run = client.actor("dromb/costco-us").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "coffee"
}' |
apify call dromb/costco-us --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dromb/costco-us"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/DHywzwb8wsFKP29bn/builds/mUKSjpxI5g9yDr5If/openapi.json