Now in closed beta.Book a demo to get started.
Use cases

Remove API endpoints with no traffic for a full quarter

Dead code and stale content|The work pauses for the plan, and the review bar is raised so that smaller suggestions also block the merge, not only serious findings.

Endpoints nothing has called in a quarter, removed on traffic evidence after a deprecation window.

The ticket

Remove API endpoints that have received no traffic for a full quarter.

Acceptance criteria

  • Traffic evidence covering a full quarter is attached
  • The endpoints return a deprecation signal for a stated window before removal
  • Known integrators are notified
  • Removal is a separate change from the deprecation

What lands as proof

A quarter of traffic evidence, then a deprecation window, then removal. All three, in that order.

Why teams defer it

  • An unknown integrator may call it once a quarter, so the evidence window is never quite long enough.
  • Removing an endpoint is irreversible for whoever was using it, which makes it a decision rather than a cleanup.

Questions

What does the agent actually change?
The ticket is scoped to one outcome: remove API endpoints that have received no traffic for a full quarter. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
How do I know the work is done?
The pull request carries the evidence, not only the diff. Here that means traffic evidence attached to the plan before anything is deleted, so a reviewer can confirm the result without reproducing the work locally.
How much oversight does this need?
The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.

Ready to put the fleet to work?

Contact us for a demo with an expert.