Problems with Synthetic

[vk2r]

It appears Synthetic has changed its API, and this change seems to have occurred recently. Previously, the data was being retrieved correctly, but now it is no longer being retrieved, preventing the graphs from being displayed.

[prakersh]

Thanks for reporting this. We investigated and identified the root cause.

What changed: Synthetic updated their /v2/quotas API response format. Previously it returned three quota types (subscription, search.hourly, toolCallDiscounts), but it now only returns subscription:

{
  "subscription": {
    "limit": 135,
    "requests": 0,
    "renewsAt": "2025-09-21T14:36:14.288Z"
  }
}

API docs: https://dev.synthetic.new/docs/synthetic/quotas

What needs to change in onWatch:

• internal/api/types.go - QuotaResponse struct still expects search and toolCallDiscounts fields that the API no longer returns
• internal/api/client.go - Debug logging references removed fields
• internal/agent/agent.go - Snapshot creation, notifications, and session reporting still reference all 3 quota types
• internal/tracker/tracker.go - Tracker processes search/toolcall cycles with zero data, creating empty cycles
• internal/web/handlers.go and internal/web/static/app.js - Dashboard renders empty "0/0" cards for search and tool calls
• internal/testutil/fixtures.go and related test files - Mock responses use the old 3-quota format

Why we can't fix this right now: Our Synthetic plan has expired, and due to the increase in their pricing, we won't be renewing anytime soon. Without an active subscription, we can't test changes against the live API to verify the fix works correctly.

If you'd like to help: The fix itself is straightforward - update the response types to subscription-only, skip search/toolcall tracking when limit is 0, and conditionally hide empty quota cards in the dashboard. The DB schema stays unchanged for backward compatibility. If anyone with an active Synthetic subscription can contribute, that would be really appreciated!