Skip to main content

Monitor your project

What you can watch, and where​

You want to seeConsoleAPI, with a virtual key
The spend of today, the last week or the last monthOverview › Spent, Spend over timeGET /usage/me: the spend of this month
The spend of each app, key and modelOverview › Per-app burn, Per-key burn, Model splitGET /usage/me: by_model, by_task
The calls that failed, and whyRequests › What failed, Attempt log—
The vendors that fail oftenRequests › Who is unreliable, Model healthGET /status/peek: the state of each vendor
The models and vendors that your project skips nowRequests › Model health › Retired now—
If the next call will be refused—GET /status/peek: tenant_capped
What to change to spend lessImprove › What to change—

The console pages are explained in Console screens.

Get an alert​

Proxium sends an alert to Slack, Discord, Telegram or a webhook when the spend of the project or of one app passes a level. See Get spend alerts.

Proxium also sends an alert to the same channels when your failover policy retires a model or a vendor. The alert is on by default. To turn it off, clear Send an alert in Routing › When a call fails.

Send call records to your own tools​

Proxium sends a record of each call to your webhook or OpenTelemetry backend. See Send call records to your tools.

Watch the spend from your own system​

To alert from your own system, read the spend on a schedule.

Example: a script that a scheduler runs each hour. It exits with an error when the spend of the month passes a level that you choose.

check-spend.sh
#!/bin/sh
used=$(curl -s https://proxium.tech/usage/me \
-H "Authorization: Bearer $PROXIUM_KEY" | jq '.credits.used_usd')
echo "Proxium spend this month: \$$used"
awk -v u="$used" 'BEGIN { exit (u > 50) ? 1 : 0 }'

To stop an app at a limit, do not wait for an alert. Set a limit, and Proxium refuses its calls above it. See Set budgets and limits.

What is not available yet​

FeatureState today
Spend alerts by emailNot available. Use Slack, Discord, Telegram or a webhook