> ## Documentation Index
> Fetch the complete documentation index at: https://syntalic.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Pricing tiers

> Measure and direct-route prices, from $0.01 to $0.05.

Syntalic's paid endpoints come two ways: **measures**, one priced path per kind of question, and the per-endpoint routes they are built on, grouped by area (Shopper, Marketing, Analyst, Ontology, Taxonomy, Social, Scout). Each measure has one price, and each area has one price.

## Measures

Each [measure](https://syntalic.com/docs/reference/measures.md) is one path under `/v1/measures/`, answered by the endpoints below. Its price applies to every `by` split. `GET /v1/measures` lists available splits and measure prices for free. If anything on this page differs from the live OpenAPI spec or a 402 challenge, the live values are correct.

| Measure | Price | Answers |
| - | - | - |
| `offers` | \$0.01 | Who sells one product, and at what price, now |
| `prices` | \$0.02 | The price level and spread of a shelf |
| `trend` | \$0.02 | How prices moved, for a product, a shelf or a brand |
| `promotions` | \$0.01 | Who discounts, how often and how deep |
| `assortment` | \$0.02 | What is on the shelf, and who holds it |
| `attention` | \$0.03 | Share of social conversation, and how it is moving |
| `signals` | \$0.03 | What posts say, as labels: launches, reviews, stance, names, practices |
| `scout` | \$0.05 | Social attention set against the shelf |
| `resolve` | \$0.01 | A name, phrase or code to ids |
| `neighbors` | \$0.01 | What sits next to an id |
| `coverage` | \$0.01 | How much evidence stands behind an id |

A split answered by a cheaper endpoint costs the measure's price on the measure path. `prices` by `brand`, for example, is \$0.02 at `/v1/measures/prices` and \$0.01 at `/v1/marketing/price-positioning`. The [MCP tools](https://syntalic.com/docs/reference/mcp-tools.md) call the endpoint directly, so they pay the endpoint's price.

## Endpoints by area

The per-endpoint routes are grouped by the kind of question they answer. The API Reference tab uses the same groups, except that the Taxonomy routes are under **Reference** and the two Scout routes are under **Social**. Each area has one price, so a call to any endpoint in it costs the same. Most callers do not need them: a [measure](https://syntalic.com/docs/reference/measures.md) reaches the same answers with one path and one pair of arguments.

## Prices by area

### Shopper — \$0.01 / query

Point-in-time pricing answers for shopping assistants and price-tracking tools.

| Endpoint | Purpose |
| - | - |
| `best-price` | Ranked offers for the matched product across covered retailers; may contain last-seen prices |
| `price-history` | Time-series price for a product |
| `deal-finder` | Discounted in-stock products in a category or for a brand, measured against the retailer's list price |
| `price-drop-alert` | Whether one product's current price is below its average over the last N days, with the lowest price seen |

### Marketing — \$0.01 / query

Competitive intelligence for brand and category managers.

| Endpoint | Purpose |
| - | - |
| `competitive-landscape` | Every product on a category shelf with its current price, across retailers |
| `brand-tracker` | Day-by-day brand pricing, product and promotion counts |
| `promo-intelligence` | Promotion frequency and depth in a category, by brand or by retailer |
| `share-of-shelf` | Each brand's share of the observed product shelf, not sales market share |
| `price-positioning` | Where one brand's median price sits on a category's price ladder (entry, value, mid, premium or luxury) |
| `brand-breakdown` | A brand's assortment broken down by category |
| `retailer-assortment` | Which retail chains carry a brand or category |
| `availability-index` | Out-of-stock rates by retailer or category |

### Analyst — \$0.02 / query

Aggregated, statistical, multi-product queries — more expensive because they touch more rows.

| Endpoint | Purpose |
| - | - |
| `price-dispersion` | Spread of current prices on a shelf or for a product type: mean, spread and percentiles |
| `retailer-index` | Average pricing posture of a retailer vs. category baseline |
| `price-bands` | Price architecture of a supported shelf scope |
| `category-summary` | Category-level pricing distribution and stats |
| `category-concentration` | How concentrated a category is |
| `price-change-leaders` | Biggest price movers over 7, 30, or 90 days |

### Ontology — \$0.01 / query

What a name means, what sits next to an id, and how much evidence stands behind it. Use the ids they return to scope the other endpoints.

| Endpoint | Purpose |
| - | - |
| `resolve` | Names to ids across shelves, product types, brands and chains |
| `neighbors` | What sits next to an id |
| `coverage` | How much evidence stands behind ids, and which chains were scanned |

### Taxonomy — \$0.01 / request

GS1 GPC identity lookups, priced per request (up to 100 ids).

| Endpoint | Purpose |
| - | - |
| `classify` | Map Amazon browse node ids or product-type phrases to GS1 GPC codes |
| `reverse` | GPC codes back to the Amazon browse nodes mapped onto them |
| `brick-attributes` | GS1 attribute schema for a brick |

### Social — \$0.03 / query

TikTok and Instagram. Most social routes are scoped to one **Shopify taxonomy path**: a root such as `food-beverages-tobacco` or `health-beauty`, or any node under it (`food-beverages-tobacco/beverages/soda`). Retired browse roots such as `grocery-gourmet-food` are refused before payment, with the root to use instead. `emerging-brands` and `product-names` cover the whole tracked corpus and take no category, and `tactics` works with or without one. `subject_kind` on `series` is `brand` or `category` only. `organic_only=true` leaves out posts marked as ads.

| Endpoint | Purpose |
| - | - |
| `creator-index` | Creators ranked by mention volume |
| `brand-share` | Share of conversation by brand |
| `product-share` | The catalog products a category is talking about |
| `category-structure` | Subcategory ownership of a category's conversation |
| `brand-momentum` | Brands rising, falling, or newly appearing |
| `emerging-brands` | Brands creators keep tagging that the catalog does not carry yet |
| `topic-trends` | Emerging conversation topics |
| `product-type-trends` | Attention by product type |
| `brand-signals` | Launches, reviews, stance, retailers and prices posts attach to each brand |
| `product-names` | Product names read off posts that match no catalog product |
| `tactics` | Marketing practices creators describe brands using |
| `series` | Weekly mentions/views for one brand or category |

### Scout — \$0.05 / query

These routes bind tracked social conversation and the observed retail shelf to a shared category axis. Their paths are under `/v1/social/`, not `/v1/scout/`, and the API Reference tab lists them under Social.

| Endpoint | Purpose |
| - | - |
| `attention-vs-shelf` | Share-of-conversation vs share-of-shelf gap |
| `launch-buzz` | New shelf arrivals vs conversation around their brand |

## Why the gap between tiers?

Analyst answers aggregate across many products to produce statistical signals like price distributions and movers — they inform strategic, multi-product decisions. Shopper, Marketing, Ontology, and Taxonomy tiers serve lookup-style use cases. Social answers rank and compare activity across tracked TikTok and Instagram posts, so they are priced above Analyst. Scout combines that social data with the retail shelf data, so it is priced above Social.

Send the unpaid request first: a social view that isn't published yet is then refused with `404 NOT_PUBLISHED` before payment, so it is **not billed**. That is a gap in what we publish, not a finding that the category is quiet.

## Volume discounts

For high-volume use, contact us about pricing. [Get in touch](mailto:support@syntalic.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.