Upstream
# Upstream
Part of the **Toolweather suite**. The same tools are also available on the Toolweather MCP at `https://toolweather.toolweather.workers.dev/mcp` (proxied here). This Worker remains the source of truth for REST, digests and x402 payments.
Live status and breaking-change feed for the AI and developer APIs agents depend on: outages, model deprecations and retirements, pricing-page changes. ~40 providers.
- Site: https://upstream-api.pages.dev
- API: https://upstream.toolweather.workers.dev ([llms.txt](https://upstream.toolweather.workers.dev/llms.txt), [OpenAPI](https://upstream.toolweather.workers.dev/openapi.json))
- MCP: `https://upstream.toolweather.workers.dev/mcp`
## Free tier
500 calls/day with a free key (`POST /v1/keys`), 50/day anonymous, 1 free change-alert webhook. Above that, pay per call with x402 (Base mainnet, real USDC): `/status/:provider` $0.003, `/model/:id` $0.003, `/changes` $0.01, extra watch $0.05/30 days.
## Stack
Cloudflare Worker (free plan) + D1, Hono, `@x402/hono` with the PayAI facilitator (Base mainnet). Pay-to address, network and facilitator are env vars in `wrangler.toml`, so switching to mainnet is a config change.
Cron every minute: a quarter of the providers per run (each provider ~every 4 min), one tracked docs page every 5 min.
TDQS
Scored across 5 tools
The two check_* tools cleanly split provider-level health from model-level lifecycle, and list_providers is clearly the index helper for check_api_status. The main overlap is between list_recent_api_changes and get_digest, which both surface incidents/deprecations; the descriptions distinguish them (on-demand change feed vs once-a-day catch-up), so confusion is minor.
All names are snake_case verb_noun, with aliases documented (get_status, get_model, get_changes). Three verb families appear (check_, list_, get_), which is readable and mostly predictable, though not a single uniform verb pattern.
Five tools is a tight, well-scoped surface for an API/model monitoring service: status check, deprecation check, provider index, change feed, and digest. Each tool earns its place with no redundancy bloat.
Provider health, model deprecation, the provider index, recent changes and a daily digest cover the core monitoring lifecycle including lookups and alerts. A minor gap is the absence of a dedicated query for the MCP-server breaking changes mentioned in the digest, forcing agents to use the generic change feed.