Perplexity cost tracking
Sonar API calls and Enterprise seats.
How does Camaze work with Perplexity?
Camaze connects to Perplexity with read-only credentials and pulls spend and usage into the same view as every other place you pay for AI.
What Camaze pulls from Perplexity
Camaze connects to Perplexity with read-only credentials and pulls spend and usage into the same view as every other place you pay for AI.
- Total spend, by billing period
- Usage by model, including input, output and cached tokens
- Cost by API key, project or workspace
- Rate of change, so a jump is visible the day it happens
See your Perplexity spend in context.
Book a walkthrough and we will show you Perplexity costs next to everything else you pay for AI.
Keep reading
Every integration
The full list of providers, tools, self-hosted sources and destinations Camaze connects to.
Read moreSpend visibility
How Perplexity spend joins every other source on one cost basis, in one number.
Read moreCost optimization
The standing list of what to cut, including findings specific to Perplexity usage.
Read moreQuestions people ask
What access does Camaze need for Perplexity?
Read-only billing and usage credentials. Nothing that can spend money, change a deployment, or read your prompts and completions. Details are on the security page.
Does it backfill historical Perplexity spend?
Yes. Camaze pulls the available history on connection, typically the last twelve months, so you start with a trend rather than an empty chart.
Can we split Perplexity spend by team or project?
Yes. Map keys, projects, workspaces or tags to your own org structure once, and every Perplexity charge is attributed from then on. See cost allocation.
Do we have to use Perplexity exclusively?
No. Camaze is built for the opposite case. Perplexity sits alongside every other provider, tool and self-hosted model in the same view, on the same cost basis. It is equally useful if Perplexity is the only thing you run: see single-provider visibility.