---
title: "Owner Savings"
method: GET
path: "/owner/savings"
---

# Owner Savings

`GET /owner/savings`

## Request

- Base URL: `https://mcp.physea.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://mcp.physea.ai/owner/savings`
- Auth: none declared

OWNER plane — Token Yield v2 (2026-07-09), THE product number: per COMPLETED task
(report_outcome worked=true), tokens the caller's model would have spent completing the
task ALONE minus what it actually spent using Liminality, summed.

Shape:
  {tokens_saved_total, usd_saved_total, tasks_completed, avg_tokens_saved_per_task,
   basis_breakdown:{measured, estimated}, by_caller, price_basis, legend}

tokens_saved_total/usd_saved_total/tasks_completed are CUMULATIVE across all completed
tasks; an uncompleted task (worked=false or never graded) contributes nothing — this
number only grows from real, reported completions, never from raw call volume. Pure read
over app/data/savings.json (savings.task_rollup); missing/corrupt store => an honest
all-zero rollup, never a 500. Admin-gated via the /owner/ prefix in metering.AUTH_PATHS
(same as /owner/telemetry). Savings is telemetry — it never gates anything.

## Response `200`

Successful Response

- unknown

---

[API](https://skmtc.dev/physea/apis/liminality-router-service.md) · [All operations](https://skmtc.dev/physea/apis/liminality-router-service/llms.txt) · [OpenAPI document](https://skmtc.dev/physea/apis/liminality-router-service/revisions/5f60ddd97544?raw)