Syntalic
Analyze price inflation trends for a category or department
Offering
- Provider
- Syntalic
- Method
- GET
- Offering type
- Api Endpoint
- Transport type
- http
- Category
- Financial Analysis
- Delivery
- Not provided
- Pricing model
- Not provided
- x402 version
- 2
Endpoint context
- URL
https://api.syntalic.com/v1/analyst/inflation- MIME type
- application/json
- First seen
- 2026-10-16T01:50:03.310Z
- Last seen
- Tags
- X402, pricing, retail, Amazon, walmart, price-tracking, shopping
Payment pricing
x402 payment terms are the authoritative price for calling this endpoint.
- Payment option 1
- 0.02 USDC
Atomic price: 20000 · Network: solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp · Asset: USDC · Scheme: exact - Payment option 2
- 0.02 USDC
Atomic price: 20000 · Network: eip155:8453 · Asset: USDC · Scheme: exact
Raw x402 terms
[
{
"scheme": "exact",
"network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
"asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
"amount": "20000",
"payTo": "2hYY7wHhXsoWnskQRzYFUNH7YboXNMEqbGnAFHpRuB2W"
},
{
"scheme": "exact",
"network": "eip155:8453",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "20000",
"payTo": "0xe2e662cF219025AFC0C9Bf850b6a2B0a0b5517fe"
}
]Observed health
- Status
- Reachable
- Latest latency
- 67 ms
- Average latency
- 66 ms
- HTTP status
- 400
- Last checked
- Reachability
- 92.3% over 13 checks
Latency is measured to the first response headers. A reachable result does not verify response accuracy or merchant identity.
Input schema
{
"type": "http",
"method": "GET",
"queryParams": {
"type": "object",
"properties": {
"to": {
"type": "string",
"format": "date",
"example": "2026-06-01",
"description": "End date (ISO 8601, defaults to now)"
},
"from": {
"type": "string",
"format": "date",
"example": "2026-05-01",
"description": "Start date (ISO 8601, defaults to 30 days ago)"
},
"country": {
"enum": [
"us",
"ca"
],
"type": "string",
"default": "us",
"example": "us",
"description": "Country (us or ca)"
},
"category": {
"type": "string",
"example": "electronics",
"minLength": 1,
"description": "Product category in the Shopify product taxonomy. Accepts a display path (e.g. 'Electronics > Computers > Laptops'), its slug form (e.g. 'electronics/computers/laptops'), a single path segment (e.g. 'laptops', 'headphones'), or an everyday shelf name (e.g. 'apparel', 'beauty', 'grocery'); matched against the catalog's category tree (exact node, subtree, or whole path segment). Also accepts a GS1 GPC code (exactly 8 digits, e.g. '10001159') to filter by PRODUCT TYPE instead of by shelf placement — the same product type is shelved under different categories by different retailers, so a category filter answers from a fraction of the data while a GPC code spans them. Coarser codes (class/family/segment) match every brick beneath them. Resolve a phrase to a code with /v1/reference/classify?q=... ; when a code is used, resolved.match_source is 'gpc'. For analyst endpoints, supply either `category` or `department`; both may be supplied to narrow the scope."
},
"retailer": {
"enum": [
"amazon",
"walmart",
"target",
"bestbuy",
"homedepot",
"costco",
"ikea",
"samsclub",
"cvs",
"dillards"
],
"type": "string",
"example": "amazon",
"description": "Filter to a specific retailer platform (long-tail specialty stores are also present; any platform key is accepted)"
},
"department": {
"type": "string",
"example": "Electronics",
"minLength": 1,
"description": "Top-level department (root category), e.g. 'Electronics', 'Beauty', 'Home & Kitchen'. Case-insensitive; matched against the category tree's root segment. For analyst endpoints, supply either `category` or `department`; both may be supplied to narrow the scope."
},
"granularity": {
"enum": [
"daily",
"weekly",
"monthly"
],
"type": "string",
"default": "weekly",
"example": "weekly",
"description": "Time granularity for the series"
},
"time_window": {
"enum": [
"last_30_days",
"last_60_days",
"last_90_days",
"month_to_date",
"previous_month",
"month_over_month",
"quarter_to_date",
"custom"
],
"type": "string",
"example": "last_60_days",
"description": "Historical window preset. Explicit `from`/`to` takes precedence and is reported as `custom`; `time_window=custom` requires both `from` and `to`. Date-only ranges use UTC calendar boundaries with inclusive `from` and exclusive `to`."
}
}
}
}Output schema
{
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}