Which AWS limit is actually current? An agent that proves it, 32 vs 5 vs 16

Description and use

An agent that determines the current AWS limit by reconciling official sources and live API, exposing discrepancies and preventing production errors.

Problem

AWS documentation, pricing pages, and Service Quotas console often disagree on quota values, leading to stale or incorrect numbers used in production.

Outcome

The agent accurately reports EC2 vCPU quota as 5 (console), 32 (old guide), and 16 (live), exposing drift and preventing production errors.

Workflow

• 1. Load typed facts from a Sanity Context Knowledge Base.
• 2. Apply a deterministic rule to pick the winner among the sources.
• 3. Show the reconciled value and the superseded value with source links.
• 4. Call the read‑only live AWS API to verify the reconciled record.
• 5. Present all three numbers (docs, console, live) to the user.

Evidence

For one AWS fact, three official pages can each give you a different number.

Source

It reads typed facts from a Sanity Context Knowledge Base, picks the winner with a deterministic rule the model is not allowed to override, and shows both the current value and the one it replaced, each with its source.

Source

On the EC2 vCPU quota it turns up three different numbers, docs 32, record 5, live 16, and puts all three on the screen.

Source