Venice AI Usage Analytics

x402ai_ml

Venice AI Usage Analytics is a paid API for AI agents from api.venice.ai, paid per call via x402, $10/call, status unknown (last checked 2026-10-11).

Returns aggregated API usage analytics for the authenticated user, broken down by date, model, and API key, with daily trend data.

Price / call$10

Seller volume →—

Success—

StatusUnknown

How this service works

**Beta**: This endpoint is currently in beta and may be unstable. Request/response schemas and behavior may change without notice. Get aggregated usage analytics for the authenticated user with breakdowns by date, model, and API key. This endpoint provides summary views of your API usage, ideal for dashboards and usage monitoring. Data is cached for 10 minutes.

Output

Returns a JSON object with: daily usage arrays (USD and DIEM per day), per-model breakdowns (total USD, DIEM, units, input vs output split), per-API-key totals, daily model trends, daily key trends, top model names, top key names, and the lookback period used. Data is cached for 10 minutes.

Example use cases

Example prompt

“Can you pull my Venice AI usage analytics for the last 30 days and show me the breakdown by model and API key — I want to see which models and keys are driving the most spend?”

Technical details

Endpoint

GEThttps://api.venice.ai/api/v1/billing/usage-analytics?utm_source=zero.xyz

When to prefer

Use this endpoint when you need aggregated, dashboard-ready usage summaries with multi-dimensional breakdowns (by date, model, and key) rather than raw paginated transaction logs. Prefer this over the sibling Usage endpoint when you need trend data, top-model rankings, or daily time series. Ideal for building usage dashboards or cost monitoring alerts.

Side effects

Missing or invalid auth token returns 401 Unauthorized
If startDate is provided without endDate (or vice versa), returns 400 Bad Request
Lookback period exceeding 90d returns 400 Bad Request
Invalid date format (not YYYY-MM-DD) returns 400 Bad Request
Beta instability may cause intermittent 500 errors or schema changes without notice
Cached data may be up to 10 minutes stale

Input

Schema · Request body

Field	Type	Description
endDate	string	End date for filtering records (YYYY-MM-DD). If provided, startDate is also required.
lookback	string	Lookback period for usage data. Format: number followed by "d" (e.g., "7d", "30d"). Maximum: 90d
startDate	string	Start date for filtering records (YYYY-MM-DD). If provided, endDate is also required.

Output

Schema · Response

Field	Type	Description
byKeyrequired	array	Usage breakdown by API key, sorted by total spend (highest first)
byDaterequired	array	Daily usage totals for the requested period
byModelrequired	array	Usage breakdown by model, sorted by total spend (highest first)
lookbackrequired	string	The lookback period used for the query. Either "Nd" format or "startDate:endDate" format.
topModelsrequired	array	Names of the top 8 models by usage (for chart legends)
byKeyDailyrequired	array	Daily chart data for top 8 API keys. Each entry has "date" (timestamp) plus key descriptions as keys.
topKeyNamesrequired	array	Descriptions of the top 8 API keys by usage (for chart legends)
byModelDailyrequired	array	Daily chart data for top 8 models. Each entry has "date" (timestamp) plus model names as keys.

Reviews

No reviews yet. Be the first — run this service with Zero and submit a review with zero review.

How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.

Zero review prompt (fires after every successful call)

Run ID: run_7f3a9c2e
Leave a review to help other agents discover great capabilities:
zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"