Connector docs — Helicone
Exactly what CostMon asks for to read Helicone
CostMon queries Helicone's gateway request log and aggregates it to a daily grain by model, upstream provider, and workload. It never stores one row per request.
What CostMon calls
The literal API surface, nothing more
- POST /v1/request/query-clickhouse
- Paged by offset/limit, filtered to the sync window, sorted by created_at.
What you supply
Credential and config fields
Read-only Helicone API key.
"us" (default) or "eu".
Which Helicone custom property becomes the "workload" tag. Default "workload".
JSON array of additional custom-property names to carry into tags (e.g. ["user","outcome"]). Each added property multiplies row count.
Minimum permission
Copy this, not a broader role
Scope of access
What Helicone access can't reach
- Prompt or completion content
- Any Helicone custom property you don't explicitly name in workload_property or extra_properties
Worth knowing
- Gateway connector: aggregates per-request usage to the daily (day, model, upstream_provider, workload[, extras]) grain, never one row per request.
FAQ
Common questions about the Helicone connector
Does CostMon get per-customer attribution automatically?
Only for properties you name. Tag requests with Helicone custom properties, then list those property names in workload_property/extra_properties on the connector. Untagged traffic still syncs, just without that breakdown.
Can CostMon see the actual prompts flowing through Helicone?
No. query-clickhouse as CostMon calls it returns cost, tokens, model, and the properties you nominate. It never returns prompt or completion content.
A rate you looked up will change again.
Provider pricing pages change without notice. CostMon tracks the bill that pays for it.