Receipts & Activity — ML Junction docs
A completed canonical response includes routing metadata, usage, warnings, and a request receipt. Authenticated users can fetch the durable activity record at GET /v1/activity/requests/{request_id}.
Evidence · What it answers selected_route · Which exact route answered? provider / provider_model · Which provider and upstream model were used? billing_mode / credential_source · Was the provider paid by platform or BYOK? fallback_used / attempts · Did retries or fallback occur? decision_reason · Why was this route selected? estimated_charge_usd · What was predicted before execution? actual_charge_usd · What was charged after actual usage? pricing_source · Where did the price evidence come from? cache receipt · Was provider prompt caching reported? privacy receipt · What privacy policy was enforced? warnings · What safe transformations or compatibility compromises occurred?
Use request IDs in support tooling. Public errors contain a support code, while authenticated activity exposes the user-safe execution history without leaking provider secrets.
Sessions, tasks, and content capture
Set session_id/session_name and task_id/task_name on canonical requests to build an app → session → task → request hierarchy. Every response returns both its request id and session_id. Reuse session_id across turns to group the complete execution history.
Endpoint · Purpose
GET /v1/activity/requests · Search/filter requests by IDs, names, prompt text, model, app, status, USD cost, and latency
GET /v1/activity/requests/{id}?include_content=true · Detailed route, retry, trimming, timing, guardrail, prompt, tool, and completion trace
GET /v1/activity/sessions · List grouped sessions
GET /v1/activity/sessions/{id} · All requests and events in one session
GET|PUT /v1/organizations/current/content-logging · Organization capture and retention policy
Exact prompt/completion capture is disabled by default. Owner/admin permission is required to enable or view it. API-key policies can inherit, enable, or disable request and completion capture. Retained content is automatically erased after 1-365 days.
Canonical URL: https://mljunction.com/docs/receipts-activity