# Retire a decommissioned third-party endpoint

A third-party endpoint with a shutdown date, migrated before the date rather than after.

Category: Vendor and third-party migrations
Source: https://letsship.ai/use-cases/retire-a-decommissioned-endpoint
Published: 2026-08-25

## Goal

Migrate every caller off a third-party endpoint that is being decommissioned.

## Acceptance criteria

- No caller references the old endpoint
- Each migrated caller has a test against the new one
- The old client code is deleted
- The shutdown date is recorded in the description

## What lands as proof

A search showing no remaining references, plus tests against the replacement at each site.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Migrate off the decommissioned {endpoint}

Description: Migrate every caller off a third-party endpoint that is being decommissioned.

Acceptance criteria:
- No caller references the old endpoint
- Each migrated caller has a test against the new one
- The old client code is deleted
- The shutdown date is recorded in the description

Before you create the issue, find the deprecation notice and its date, and replace {endpoint} with the affected call.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: migrate every caller off a third-party endpoint that is being decommissioned. 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 every caller migrated, the old client deleted, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.