Usage & Qualified Active Days
Three generic signals. No feature events, no payloads about what happened inside.
POST
/api/v1/usageauth ·
gat_… or gk_live_…{ "kind": "session" | "heartbeat" | "activity" } with the person's access token, or { "user_id": "<uuid>", "kind": … } with your API key
kind
- sessionthe app opened
- Cheap to send, and on its own it never qualifies a day. Opening something is not using it.
- heartbeatstill in use
- Send while the person is actually working, not on a timer that runs against an idle window.
- activitythey did the thing
- Whatever counts as real use in your product: a render, a save, a message sent. You decide what the bar is; we never ask what it was.
Deduplicated per person × product × day downstream. Calling every thirty seconds is safe; it is also worth nothing more than calling once.
What it feeds
Qualified Active Days are the unit behind two things that pay or promote: the Creator Pool split, which divides Member revenue by verified use rather than by negotiation, and the GSP seal, which a product cannot earn without them. A product that never reports usage can still be listed, sold and included — it just cannot be shown to have succeeded.