Total provider spend
–
AWS + OpenAI API · Same reporting period
The cost of running TollChat
The cost of building, testing, and running TollChat. AWS infrastructure and OpenAI API usage, on one transparent bill.
–
AWS + OpenAI API · Same reporting period
–
Unblended cost
–
Organization-wide · Provider-reported
Last 30 completed days
Loading billing snapshot…
Daily costs in USD. Credits appear below zero. Billing may revise earlier days.
| Date | AWS | OpenAI | Total |
|---|
Month to date · Available AWS sources
EC2 – Other is AWS’s billing category for costs such as storage and data transfer. OpenAI API spend is shown separately above.
Month to date · Available AWS sources
Shared infrastructure supports the project across environments. Unallocated charges are included in the total; they have no recognized environment billing tag.
A different question
Measured model usage in repeatable conversations, priced at standard API rates.
–
Includes measured failed agent calls. An answer is one completed assistant turn, which may use several model calls.
–
Agent + simulated user + judges, per attempted conversation
| Role / reasoning | Calls | Run spend | Per conversation |
|---|
Luna 6 · Actor low · TollChat medium · Judges xhigh. Real model calls with frozen tool results; these are benchmark settings, not a statement about the deployed configuration. Public-chat attribution remains unmeasured. Infrastructure and tool execution are excluded; inference estimates are not added to the provider bill.
AWS uses Cost Explorer unblended cost for this deployment’s account. The production dashboard also reads development’s published AWS aggregate. OpenAI uses its organization Costs API, without project filtering. A combined total requires every source to cover matching UTC dates in USD. Development combines its AWS account with organization-wide OpenAI costs, which include all environments. Production counts OpenAI once, directly from the provider. AWS-hosted model charges remain within AWS. Token estimates are never added again.
All spend in these accounts and this OpenAI organization is treated as TollChat spend, including development and evaluations. No returned charges are excluded. Credits and adjustments retain their sign. AWS uses the lowercase environment tag: production, development, or shared; other charges are unallocated. OpenAI workload allocation is not established.
Queries cover the union of month to date and the last 30 completed days, ending at midnight UTC today. On the first of a month, month to date has no completed days. Requested dates are not a guarantee that providers have finished reporting them. Neither source confirms a finalized-through date here. Development refreshes at 08:00 UTC and production at 09:00 UTC daily. Failed refreshes retain the last valid snapshot; publication older than 48 hours is flagged.
Agent charges across all attempts are divided by completed assistant turns. Actor, agent, and judge conversation averages divide each role’s spend by attempted conversations. Failed calls with known usage count; incomplete usage prevents publication. This dated sample is refreshed manually, separately from daily billing. Caching reflects the measured run and may differ in public chat.
Rates and source load with the benchmark.