feat(agent-proxy): report proxied service usage

[saifsmailbox98]

Description 📣

Adds best-effort usage reporting to the agent proxy, which powers a "last used" indicator on proxied services in the dashboard. Until now the proxy only logged per-request activity to its local stream, so the platform had no signal of whether a proxied service was actually being used.

When the proxy brokers a request for a proxied service, it records the service's ID and the time. Once per poll tick it reports the latest time per service via POST /v1/proxied-services/:serviceId/report-usage, authenticating with the proxy's own machine identity (never the agent's — the agent token lives in the untrusted execution environment, so letting it report would let a compromised agent forge usage).

• Accumulates distinct service IDs in memory, bounded by the number of configured services rather than traffic, and snapshot-and-clears on each flush. An unreachable backend never grows memory or blocks brokering; a dropped report just re-sends on the next tick if the service is still in use.
• Reports the actual broker time (server clamps it to now() and only advances monotonically), so a longer --poll-interval doesn't skew the timestamp.

Companion PR: Infisical/infisical#7359

Type ✨

• Bug fix
• New feature
• Improvement
• Breaking change
• Documentation

Tests 🛠️

# Here's some code block to paste some code snippets

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[linear]

AGE2-57

[infisical-review-police]

💬 Discussion in Slack: #pr-review-cli-322-feat-agent-proxy-report-proxied-service-usage

Posted by Review Police — reviews, comments, new commits, and CI failures will stream into this channel.

[greptile-apps]

Greptile Summary

This PR adds usage reporting for services brokered through the agent proxy. The main changes are:

• In-memory tracking of the latest broker time per service.
• Periodic usage reports authenticated with the proxy token.
• A new API helper for the report-usage endpoint.

Confidence Score: 4/5

The usage flush lifecycle needs fixes before merging.

• Sequential report timeouts can delay service-cache refreshes for minutes.
• Normal shutdown can discard usage accumulated since the last poll tick.
• The API request shape and proxy-token authentication appear consistent with the surrounding code.

packages/agentproxy/proxy.go

Important Files Changed

Filename	Overview
packages/agentproxy/proxy.go	Adds synchronized usage tracking and periodic reporting, but reporting can block cache refreshes and pending usage is not flushed during shutdown.
packages/api/agent_proxy.go	Adds the usage-report request model and API helper with standard error handling.

Comments Outside Diff (1)

1. packages/agentproxy/proxy.go, line 174 (link)

   Pending Usage Is Lost On Shutdown

   The usage poller has no stop or final-flush path, while shutdown only stops the lease refresh loop. Any usage recorded after the last tick is therefore discarded when the process exits, so a service used shortly before a normal restart may never have its last-used timestamp reported.

_{Reviews (1): Last reviewed commit: "feat(agent-proxy): report proxied servic..." | Re-trigger Greptile}