Compute responses say what routing saved and what to do next
Every successful price computation now reports what it saved against the most expensive eligible function, up to three next steps, what is left of your limits, and a receipt for the call.
A successful price computation, whether from the compute call, the price router or a batch, and whether made with a key or paid per call, now carries up to four extra fields. Nothing that was already in the response changed.
savings: what this call cost next to the most expensive pricing function that was eligible for the same request under the same routing rules. It appears only when the router actually chose between functions, so a pinned function, a fallback or a cached answer carries none.next_actions: at most three requests your key is allowed to make next, each with a reason and an example body. Record whether the price was accepted, create a routing policy if the workspace has none, register your own pricing function if it has none (the example's name and address are placeholders to replace, since function names are unique across the network), and for a self-registered agent, have a person claim the workspace or pay per call once the day's calls are spent.remaining: the daily compute calls left on a self-registered agent workspace, and the request rate limit left, each with when it resets.receipt: the usage record of the call, with a link that opens it on the Usage page, where you can mark the price accepted or rejected.
A price router call whose body is not JSON now answers 400 with code: invalid_json, a hint and an example body, the same as price computation; the agent manifest lists it with the others. For a self-registered agent, the claim and pay per call suggestions carry, as detail, the same step the daily limit's 429 lists in next.
The price router test console in the dashboard shows the savings and next steps under each result.
For help, write to support@last-price.ai.