API deprecation mapper
Third-party APIs you depend on deprecate endpoints in changelog posts nobody reads, and you find out when calls start failing. Design an agent that watches vendor changelogs and deprecation notices, then maps each one to the code you'd actually have to change. What does it read, what does it file, and what does it never change itself? How do you verify the code mapping is trustworthy, and what's your pitch for this over simply subscribing to vendor emails?
map_deprecation_impact(deprecated_endpoint: str, days_to_sunset: int, call_sites: list[str]) → list[str]["/v1/payments",30,["checkout|src/pay.py|/v1/payments","checkout|src/refund.py|/v1/payments/refund","billing|jobs/invoice.py|/v1/payments","search|src/query.py|/v1/search"]]out["billing|1|notify","checkout|2|notify"]["/v1/payments",120,["ledger|src/legacy.py|/v1/payments-legacy/charge","ledger|src/post.py|/v1/payments/charge"]]out["ledger|1|backlog"]["/v1/search",45,["checkout|src/pay.py|/v1/payments"]]out[]Turn the fuzzy goal into a bounded agent task. Say what the agent reads, what it may do on its own versus draft for a human, and what it must never touch. Then earn the trust: how you’d verify it before rollout, and the pitch (the problem, what you built, why it matters).
Agent build: design the agent in plain language (or narrate it). The coach grades the decomposition, the guardrails, the verification plan, and the pitch.