UK-based independent AI efficiency projectEvidence before claims ยท 2026

Measure at the Final Request Boundary

ONE CANARY + REUSABLE MEASUREMENT METHOD

Measure at the Final Request Boundary

A long-scroll visual companion to the article. It summarizes the article evidence boundary and method; it does not extend the underlying result.

At a glance

Measure at the Final Request BoundaryFour-step visual: VISIBLE PROMPT; SERIALIZED CONTEXT; PROVIDER BOUNDARY; USAGE FIELDS. The canary and its usage fields are one bounded observation; request components were not separately measured.ONE CANARY + REUSABLE MEASUREMENT METHOD1VISIBLE PROMPT2SERIALIZED CONTEXT3PROVIDER BOUNDARY4USAGE FIELDSEvidence labels and limits travel with the visual.
Count the final serialized request and preserve provider-returned usage categories. Do not infer layer shares from the total.

Evidence in scope

  • One related canary: 13,289 input
  • 0 cached input; 10 output
  • Layer-level attribution: unavailable

Evidence boundary: The canary and its usage fields are one bounded observation; request components were not separately measured.

How to use the diagram

Capture request/version identifiers, safe serialized size/tokens, tool definitions, history boundary, retries, and provider usage response.

What this visual explains: Count the final serialized request and preserve provider-returned usage categories. Do not infer layer shares from the total.

What it does not establish

No component-level allocation or general input/output ratio is supported.

โ† View article ยท Return to source article