> ## Documentation Index > Fetch the complete documentation index at: https://crushrewards.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. # Price band and tiers for a category node > The price architecture of one shelf: the comparability window that defines 'similarly priced' there, and the shelf's price tiers. Scoped by ladder NODE (a category path like 'electronics/headphones'), because a band is a property of one shelf. The window is derived in log space from the shelf's own robust spread over a 90-day window, so it is relative rather than a fixed dollar range - tight where a shelf clusters (video-game accessories run ±10%), wide where it spreads (car-care tools run ±60%). Tiers are equal-population, so 'premium' means the same thing on a $5-$40 shelf and a $400-$4,000 one. A shelf with too few products to define a distribution inherits its parent's window (disclosed in band.inherited_from) with the tier ladder re-centred on its own median; a shelf where a fifth of products share one price reports fewer than five tiers rather than an empty one. ## OpenAPI ````yaml https://api.syntalic.com/openapi.json get /v1/analyst/price-bands openapi: 3.1.0 info: title: 'Syntalic — Data Analytics for Agentic Commerce ' version: 1.0.0 contact: name: Syntalic email: support@syntalic.com url: https://syntalic.com description: >- Competitive pricing data across US and Canadian e-commerce retailers (Amazon, Walmart, Target, Best Buy, Home Depot, etc.). Serves price comparisons, deal alerts, brand tracking, promotional intelligence, and market analytics to AI agents via x402 and MPP micropayments. x-guidance: >- This API has three endpoint groups organized by use case: **Shopper endpoints** ($0.01/query): Use these for price comparisons and deal hunting. Start with /v1/shopper/best-price?q= to find the cheapest option across retailers. Use /v1/shopper/deal-finder?category= to find discounted products. Use /v1/shopper/price-drop-alert?q= to check for recent price drops. **Marketing endpoints** ($0.01/query): Use these for competitive analysis. /v1/marketing/competitive-landscape?category= shows all products in a category with pricing. /v1/marketing/brand-tracker?brand= tracks a brand's pricing over time. /v1/marketing/share-of-shelf?category= shows brand market share. **Analyst endpoints** ($0.02/query): Use these for market-level insights. /v1/analyst/inflation?category= shows price trends over time. /v1/analyst/price-dispersion?category= shows price spread across retailers. All endpoints accept an optional 'country' parameter (us or ca, defaults to us). Query parameters use 'q' for free-text search and 'category' for category-level queries. Marketing and analyst responses carry a `meta` block (served_from, freshness_seconds, schema_version) for staleness budgeting and a `resolved` block describing how the category input was matched against the taxonomy. Every response also sends an X-Data-Freshness-Hours header. **Free pre-payment rejection:** requests that cannot be served are rejected BEFORE any payment challenge — invalid params (400 INVALID_PARAMS), retailers that are not serving-eligible (404 RETAILER_NOT_SERVING_ELIGIBLE, with the catalog quality status and the serving_eligible_retailers list in error.details), and shopper queries that resolve to nothing in the catalog (404 NO_RESULTS). You only pay when the API can actually execute your query. Retailer values are case-insensitive (amazon == Amazon). servers: - url: https://api.syntalic.com security: [] paths: /v1/analyst/price-bands: get: tags: - Analyst summary: Price band and tiers for a category node description: >- The price architecture of one shelf: the comparability window that defines 'similarly priced' there, and the shelf's price tiers. Scoped by ladder NODE (a category path like 'electronics/headphones'), because a band is a property of one shelf. The window is derived in log space from the shelf's own robust spread over a 90-day window, so it is relative rather than a fixed dollar range - tight where a shelf clusters (video-game accessories run ±10%), wide where it spreads (car-care tools run ±60%). Tiers are equal-population, so 'premium' means the same thing on a $5-$40 shelf and a $400-$4,000 one. A shelf with too few products to define a distribution inherits its parent's window (disclosed in band.inherited_from) with the tier ladder re-centred on its own median; a shelf where a fifth of products share one price reports fewer than five tiers rather than an empty one. operationId: getPriceBands parameters: - name: node in: query required: true schema: type: string description: >- Ladder node as a category path — 'electronics', 'electronics/headphones', or a deeper rung. example: electronics/headphones - name: brand in: query required: false schema: type: string minLength: 1 description: >- Optional. Locate one brand within the tiers: each tier gains brand_products, the count of that brand's products in it. Omit for the market view. example: Apple responses: '200': description: Price band content: application/json: schema: type: object properties: node: type: string level: type: string enum: - root - l2 - l3 - l4 products: type: integer price_range: type: object properties: p05: type: number nullable: true median: type: number nullable: true p95: type: number nullable: true band: type: object properties: half_width_pct: type: number example: type: object nullable: true properties: price: type: number lower: type: number upper: type: number inherited_from: type: string nullable: true tiers: type: array items: type: object properties: name: type: string enum: - entry - value - mid - premium - luxury upper_bound: type: number nullable: true from: type: number nullable: true to: type: number nullable: true products: type: integer brand_products: type: integer '400': description: >- Invalid query parameters or unsupported enum values. Rejected by preflight BEFORE the payment challenge — no payment is requested or charged for malformed requests. content: application/problem+json: schema: type: object required: - type - title - status properties: type: type: string format: uri-reference title: type: string example: Bad Request status: type: integer const: 400 detail: type: string instance: type: string error: type: object properties: code: type: string message: type: string details: type: object additionalProperties: true additionalProperties: true additionalProperties: true '402': description: Payment challenge required before executing paid work content: application/problem+json: schema: type: object required: - type - title - status properties: type: type: string format: uri-reference title: type: string example: Payment Required status: type: integer const: 402 detail: type: string instance: type: string error: type: object properties: code: type: string message: type: string details: type: object additionalProperties: true additionalProperties: true additionalProperties: true '404': description: >- No matching result. error.code distinguishes the cases: NO_RESULTS (the query resolves to nothing in the catalog), RETAILER_NOT_SERVING_ELIGIBLE (the requested retailer exists but is not serving-eligible — error.details carries its catalog quality_status and the serving_eligible_retailers list to retry against), or NOT_PUBLISHED (a social rollup the current publish run does not compute yet — a gap in what we publish, not a finding about the category). Structurally-unservable requests are rejected by preflight before any payment challenge. content: application/problem+json: schema: type: object required: - type - title - status properties: type: type: string format: uri-reference title: type: string example: Not Found status: type: integer const: 404 detail: type: string instance: type: string error: type: object properties: code: type: string message: type: string details: type: object additionalProperties: true additionalProperties: true additionalProperties: true '429': description: Rate limit exceeded content: application/problem+json: schema: type: object required: - type - title - status properties: type: type: string format: uri-reference title: type: string example: Too Many Requests status: type: integer const: 429 detail: type: string instance: type: string error: type: object properties: code: type: string message: type: string details: type: object additionalProperties: true additionalProperties: true additionalProperties: true '500': description: Unexpected server error content: application/problem+json: schema: type: object required: - type - title - status properties: type: type: string format: uri-reference title: type: string example: Internal Server Error status: type: integer const: 500 detail: type: string instance: type: string error: type: object properties: code: type: string message: type: string details: type: object additionalProperties: true additionalProperties: true additionalProperties: true ````