AI spend controls

See what AI costs you, by model, before the invoice lands.

Pleaxy reads the AI lines on the cloud billing you already connected - Amazon Bedrock, Vertex AI, Azure OpenAI and OCI Generative AI - and from the AI providers you connect directly, such as OpenAI and Anthropic. It shows your AI spend by invoicer, model vendor and model, month to date and forecast, against the purchase order it will land on.

Get started Talk to us

Already using Pleaxy? Sign inSee pricing AI spend in the docs

How it works

AI lines from your cloud bills and AI providers
A connected cloud account shows its AI services by model and token type through the read-only billing access it already has, with nothing new asked of your account. OpenAI, Anthropic and other AI providers you pay directly connect with a read-only key, and their lines are read daily beside the cloud ones.
The supplier is whoever invoices
The model vendor is on the line, not a supplier of its own. Claude on Bedrock is AWS spend with Anthropic as the vendor, Claude on Vertex AI is Google Cloud spend, and an invoice from Anthropic is Anthropic's. Group by vendor to see what you spend on Claude, by invoicer to match invoices, and nothing is counted twice.
Ask whether this month fits the PO
Ask the agent whether this month's Bedrock forecast fits the purchase order and it answers with what's left on it. When it won't, raise the next order from the same conversation. The MCP server answers the same through get_ai_spend and check_ai_spend.

Good to know

AI providers you pay directly connect with a key you create in their console and can revoke: a read-only admin key for OpenAI and Anthropic, and for Mistral where your organization has its Admin API (Mistral Enterprise only). OpenRouter, Databricks and CoreWeave connect too, and for Snowflake Pleaxy generates a key pair. Pleaxy checks the key before saving it, stores it encrypted and never uses it to change anything at the provider. It still never asks for your cloud passwords or access keys.
Each AI invoice line is checked against the PO line and contract term for its model, the list price for its month and the usage the provider reported. Attribution rules put AI spend on cost centers, so budgets count it as it accrues. Spending ceilings at the provider are opt-in: an approved order line sets one with a separate credential you create, and an Azure ceiling only alerts.
Public list prices come from rate cards Pleaxy keeps, with the date each price took effect, so the agent can tell you what a model cost on any day. You can't edit them; your contract's rate or discount overrides them.
Every figure is in the invoicer's billing currency, never converted or added up across currencies.

See it in action

Play the conversation to see the agent handle it.

Invoices that don't match actual usage
- Buyers
The problem
Usage-based services make invoices difficult to verify. The invoice may be mathematically correct while the underlying quantities, tiers, rates or commitments are not.
How Pleaxy helps
Connect your cloud billing read-only and Pleaxy compares each cloud invoice with the metered usage behind it - holding the invoice for review when the two don't agree.
Pleaxy Assistant
Procurement · Buyer
Buyer: Does Cirrus Cloud's September invoice match our usage?
Assistant:
No. INV-7790 bills $18,620, but your metered usage for September comes to $14,300 - $4,320 more than you used, so it's held for review.
Buyer: What's behind the extra $4,320?
Assistant:
Nothing in your account's metered usage accounts for it. The invoice stays with the reviewer, alongside the usage figures, until Cirrus Cloud explains or corrects it.
Assistant: Hi! Here's how I handle this one.
Invoices with no PO - or not enough PO
- Buyers
- Suppliers
The problem
An invoice arrives before a PO is created, or the remaining PO balance isn't enough to cover it. The invoice gets blocked, approvals restart and payment is delayed.
How Pleaxy helps
Pleaxy draws down every PO as invoices land against it, so you always know what's left - and your agent can tell you when the next invoice won't fit, while there's still time to raise another PO.
Pleaxy Assistant
Procurement · Buyer
Buyer: Is PO-8842 ready for AWS's October invoice?
Assistant:
Not yet. PO-8842 has $4,200 left, and AWS billed $47,900 for September - an October invoice that size would go over the PO and be held.
Buyer: Raise a PO to cover October.
Assistant:
Raised PO-8903 for $50,000 and routed it to Manager and Finance. Once approved it goes to AWS - weeks before their October invoice, so it lands on a PO that can take it.
Assistant: Hi! Here's how I handle this one.

See where Pleaxy fits

Tell us how your team buys and pays today. We're in Vancouver and Seattle, and happy to walk you through it.

Talk to us

See what AI costs you, by model, before the invoice lands.

How it works

AI lines from your cloud bills and AI providers

The supplier is whoever invoices

Ask whether this month fits the PO

See it in action

Invoices that don't match actual usage

Pleaxy Assistant

Invoices with no PO - or not enough PO

Pleaxy Assistant

More in Verify charges

See where Pleaxy fits