Price range organization

Organize around bucketed or bounded outcomes without implying that Studio supports end-to-end range ingestion yet.

Guardrails

Treat this as a preview of the information architecture, not a live ingest path.
Do not imply range semantics are supported until the underlying surface flow exists.
Keep users on Explore or direct API workflows for unsupported range families.

What this family is for

Use this family for bounded or bucketed questions such as BTC between 90k and 100k, CPI in a range, or rate range buckets.

Current status

Studio does not yet provide an end-to-end route for range or between semantics. This page exists to organize the future UX, not to imply supported ingestion today.

What to use meanwhile

Use Explore to inspect currently available surfaces, or call the documented API directly once the corresponding range-oriented surface support exists.