AlphaNeural includes a small set of usage and billing endpoints for tracking spend across API keys, users, and teams. These endpoints are designed for dashboards, internal chargeback, and debugging unusual spend patterns.
All endpoints use the same authentication as the rest of the proxy. The spend log object returned by these endpoints includes request metadata, token counts, and calculated cost.
View spend logs
Returns spend records. You can filter by request_id, api_key, user_id, and optionally a date range.
When start_date and end_date are provided:
summarize=true (default) returns aggregated spend grouped by date (legacy behaviour)
summarize=false returns individual log entries within the date range
GET/spend/logs
Query parameters
request_id (string, optional). Return logs for a specific request id
api_key (string, optional). Filter by API key
user_id (string, optional). Filter by user id
start_date (string, optional). Start of the window (commonly YYYY-MM-DD)
end_date (string, optional). End of the window (commonly YYYY-MM-DD)
summarize (boolean, optional, default true). Aggregate by date vs return raw logs
Example (curl)
Date range with individual logs:
Response
Returns an array of spend log objects.
View spend tags
Returns spend grouped by request tags. This is useful when you attach tags like project:search, env:staging, customer:acme to requests and want lightweight spend breakdowns.
GET/spend/tags
Query parameters
start_date (string, optional). Start of the window
end_date (string, optional). End of the window
Example (curl)
Response
Returns an array of spend log objects (tagged).
Calculate spend
Compute cost without running a request (estimate), or compute cost from an existing completion response (post hoc). This endpoint accepts the same inputs used for cost calculation.
POST/spend/calculate
Request body (one of)
model + messages (estimate before calling a model)
completion_response (calculate after you already have a response)