AgentCosts Pricing
Price the beta around proof, not promises.
AgentCosts should charge when it can persist real usage, send savings reports, and warn before budgets drift. Automated routing is the next unlock, not the first paid claim.
For evaluating fit
Preview
Use the public tools before sharing any production traffic.
- Savings calculator and model directory
- Local dashboard preview with sample events
- Router onboarding application
For indie builders
Builder Beta
Pay only after onboarding when the dashboard can persist your usage.
- One beta ingest key and one workspace profile
- Persistent usage dashboard when Supabase is ready
- Budget alerts and weekly savings report
- Provider integration readiness review
For small AI teams
Team Review
A guided review for multiple workflows before routing automation.
- Shared workflow and budget review
- Multiple profile planning
- Provider key and policy checklist
- Priority onboarding call
What changes over time
The pricing ladder follows product maturity.
Estimator, local dashboard, gateway event contract, waitlist onboarding.
Persistent dashboard, ingest key, budget alerts, weekly savings report.
BYOK provider routing across cheap, fast, and premium lanes.
Pricing Principles
No provider token markup during beta; bring your own provider keys when routing opens.
Reports and alerts must prove value before automated routing is sold as the main feature.
Pricing should stay affordable for builders spending roughly $50-$500 per month on AI calls.