Cost Limits
Agent workflows can accidentally ask expensive questions. Cost control should be part of the source setup and prompt, especially for warehouses and analytics systems.
Where Cost Comes From
Section titled “Where Cost Comes From”- Warehouse scan volume.
- Provider API pagination.
- Large JSON responses.
- Repeated retries after ambiguous failures.
- Raw event exports instead of aggregate checks.
Query Habits
Section titled “Query Habits”Use query shape as the first cost control:
select date_trunc('hour', occurred_at) as hour, count(*) as eventsfrom analytics.eventswhere occurred_at >= current_timestamp - interval '24 hours'group by 1order by 1Avoid open-ended raw exports:
select *from analytics.eventsProvider Controls
Section titled “Provider Controls”Use provider-side budgets and role limits where available:
- BigQuery job budgets and project-level controls.
- Snowflake warehouse sizing and role scope.
- Athena workgroup controls.
- API pagination limits.
- Analytics endpoint date ranges.
Agent Instruction
Section titled “Agent Instruction”Add cost language to agent prompts:
Use aggregate queries first. Include explicit date windows and limits. Do not request raw event exports unless an operator approves the need.