---
title: ToolRouter — Agent Use Case Guide
description: Step-by-step guide for completing a task with a specific AI agent using ToolRouter.
url: https://toolrouter.com/tools/web-archive/use-cases/track-content-changes/copilot
---
# How to Track Content Changes with Copilot

Copilot brings Wayback Machine access into your IDE for the moments when development requires historical context from the web. Check how a third-party API documentation looked six months ago, verify when a dependency changelog entry was added, recover deleted technical references, or investigate when a competitor shipped a specific feature -- all without leaving your editor or breaking your development flow. This integration is especially valuable when debugging integration issues that may trace back to upstream documentation changes.

## Setup

{"mcpServers":{"toolrouter":{"command":"npx","args":["-y","toolrouter-mcp"]}}}

## Steps

1. Add ToolRouter to Copilot MCP config
2. In Copilot Chat: "Get site history for docs.example.com using web-archive"
3. Copilot shows the archive coverage for the documentation site
4. Ask: "Find captures of the API reference page and identify version changes"
5. Use the data to track how documentation has evolved

## Example Prompt

```
Track changes to a third-party API's documentation over the past year using web-archive. Show me what was added or removed.
```

## Tips

- Use for tracking upstream dependency documentation changes
- Copilot can format change data into structured comparison documents
- Ideal for monitoring third-party service terms that affect your product
