- Home
- Skills
- Productivity
- API Deprecation Planner
Works with the AI Agents you already use
API Deprecation Planner
Plan a breaking API change: real usage inventory, segmented consumers, gates instead of dates.
$15
API Deprecation Planner
Example session with this skill installed
We want to remove the v1 orders endpoint and three fields from the customer response. It has been coming soon for a year. Here are 90 days of gateway logs with client ids.
- Read your context and instructions
- Compiled the api deprecation planner
Worked example — illustrative data.
Deprecation plan: /v1/orders
Verdict
41 consumers found, 23 active. Earliest safe removal: gate G3, estimated 74 days from announcement.
Inventory
| Consumer | Type | Calls/day | Last seen | Fields used | Owner |
|---|---|---|---|---|---|
| mobile-android | internal | 22,000 | today | legacy_status | mobile |
| acme-partner | external, instrumented | 4,100 | today | address2 | partner team |
| cron-legacy | unknown key | 96 | 2 days ago | all | unknown |
| reseller-42 | external, uninstrumented | 1,900 | today | phone | sales |
Migration shape
Add /v2/orders with the new shape and dual-serve both verbs for 60 days. Deprecated fields return in v1 only, with Deprecation and Sunset headers.
Gates
G0 announce and headers live. G1 direct contact at 30 days if still calling. G2 rate limit deprecated traffic at 60 days. G3 removal at zero calls for 14 days or a signed exception.
Comms
One migration page with the exact diff and a code example; direct email to each identified consumer; 7-day rollback promise if migration breaks them.
Verification
Zero calls for 14 consecutive days, or documented exceptions with owner and expiry. Replacement tested with recorded production payloads.
Open risk
cron-legacy has no owner; treated as uninstrumented external with a hard gate rather than assumed dead.
Connects securely to your tools. The creator never sees your data.
About this skill
API deprecation plan: usage inventory per consumer, migration path, comms sequence and dated removal gates.
Use this skill when:
- remove or change a public API
- find out who uses an endpoint
- plan a breaking change
- deprecate an API version
Who it's for: Platform teams retiring an endpoint or version.
Example request
We need to remove /v1/report in 90 days.
What the example returns
- Inventory: 23 consumers, 4 active
- Migration path per consumer
- Removal gates with dates
In the package: five files — SKILL.md with the trigger and workflow, README.md, references/METHOD.md (the full method), references/CHECKLIST.md (the pass/fail gate) and examples/EXAMPLE.md (a worked run you can copy).
Works with Claude Code, Cursor, Codex CLI and any agent that reads SKILL.md. Plain markdown: no API key, no account, no network access.

Produces a plan for human approval only; does not execute code changes or send emails. Requires access logs to build an accurate inventory.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 days ago