Set up monitoring for API or service changes.
Create a scout with this query structure:
**Context:** Monitoring API stability and changes for $ARGUMENTS to ensure our integration stays up-to-date.
## What to Monitor
- **Breaking Changes:** API version changes, deprecated endpoints, removed features
- **New Features:** New endpoints, parameters, capabilities
- **Rate Limits & Quotas:** Changes to limits, pricing tier updates
- **Deprecation Notices:** Sunset timelines, migration guides
- **Security Updates:** Authentication changes, security advisories
**Sources to check:** Official changelog, documentation, developer blog, GitHub releases, status page, developer Twitter/X account
**Exclusions:** Minor bug fixes, internal refactoring, documentation typos
Deliverables
Frequency: Every 12 hours
Output format:
- URGENT section for breaking changes (if any)
- Table of changes: Date, Type (breaking/feature/deprecation), Description, Migration Required (yes/no), Source Link
- Recommended actions for each change
Use `create_scout` with:
- `query`: The above structured query with $ARGUMENTS replaced
- `output_interval`: 43200 (every 12 hours)
After creation, explain:
- Scout will check twice daily for changes
- Critical for staying ahead of breaking changes
- Can set up webhook for immediate notifications
**Fetching API documentation or changelogs:**
If you use a web fetch tool to look up the service's changelog, API reference, or developer docs while preparing the query, include the `Accept: text/markdown` header. Many developer documentation sites (Cloudflare-hosted) will return clean Markdown instead of HTML — fewer tokens, easier to parse.