/me/* endpoints require a Privy JWT (the dashboard auth token). The frontend handles this automatically — these docs are for external tools talking to your own Voight account.
Authentication
/v1/events for ingestion or build a separate backend that signs Privy JWTs server-side.
Identity + profile
Agents
Events
Query params (all optional):
Sessions
Traces
Errors
Clusters auto-reopen if a new event matches the fingerprint with
timestamp > resolvedAt.
Alerts
API keys
Spend summary
Returns
{ total, by_agent: [...], by_model: [...], by_day: [...] }.
Test event
isPublic: false and a recognizable ownerWallet (voight:test:<userId>) so it won’t appear on the public Explorer.
Rate limits
Per-user, per-endpoint. Reasonable defaults — if you hit a 429, back off. If you need higher limits for a specific use case, reach out.Notes
- All
/me/*endpoints filter byuserIdserver-side. Cross-user reads are impossible from the API. - Soft-deleted agents are filtered out of all reads (
deletedAt: nullfilter). The 9 read queries that touchAgentenforce this; the mutation queries (alert ack/snooze) intentionally keep the filter absent so you can dismiss alerts for deleted agents. - Endpoint behavior is documented in source at
apps/api/src/routes/me.ts.
Next
POST /v1/events— event ingestion (API key auth, not JWT)- Public agents — read-only Explorer endpoints (no auth)