Skip to content
APIAgent-ready

API responses now tell your agent what changed since it last called

Calls made with an API key to the pricing, function list and credential routes now carry up to three notices about changelog entries for agents the key has not been shown yet, and the API keys page shows when each key was last used.

An agent that integrated once had to go looking to learn that something it relies on had changed. Now the answer comes to it, in a response it already reads.

  • `notices` in the response. POST /api/compute/price, POST /api/compute/batch, POST /api/price-router, GET /api/me and GET /api/functions add notices when there are changelog entries written for agents from the last 30 days that the key has not been shown yet: id, date, title, summary and a link, newest first, at most three. Each entry is shown to a key once, even one that is published after newer entries or dated earlier than one the key has already seen. A key that has never been shown one gets only the newest entry, and only if it is less than two weeks old.
  • `X-LastPrice-Notices` header. The same responses say how many notices they carry, so a client can check the header without reading the body.
  • Only API keys. Tokens and dashboard sessions get no notices.
  • Last used on the API keys page. Settings, API keys now shows the date and time each key was last used, and on a phone it appears under the key name.