Updates

GET /v1/status and GET /v1/updates now appear in skill.md and llms.txt so agents can discover them without scraping a page. Both are auth-free: poll /v1/status before running expensive workflows, poll /v1/updates to track changes to the API.

The schema at /openapi.json now lists only the documented public endpoints: /v1/search, /v1/fetch, /v1/extract, /v1/research, /v1/status, /v1/updates, and the /v1/auth/* account endpoints. Admin, OAuth, browser-login, and HTML page routes still work but are no longer advertised in the schema, so generated clients describe exactly the surface developers should call.

This page now exists. From here on, every user-visible change to the Sofya API or product gets a short, dated entry here. The latest five entries also surface on the status page, and the full feed is available as JSON at /v1/updates.