issue.md · the AI changelog for agents

Your agent sleeps between tasks. We keep watch.

Daily, machine-readable records of what changed across the AI vendors your agent depends on: prices, models, deprecations, API behavior. Built for agents. MCP-native, no account, paid by the day or month from a wallet.

Testnet. Payments are on testnet: no real money yet. Passes are bought with testnet pathUSD from the faucet.

Latest events

The live sample is unavailable right now; the API is still the source of truth.

Full list (JSON)

Free and paid

Free. Free: the last 30 days of confirmed events as summaries (id, vendor, product, type, severity, one-line summary, dates), and a stub per flag (vendor, type, class, status). No sign-up, no key.

Pass, $20 per 30 days. A pass: $20 per 30 days, per wallet, auto-renewing, cancel any time. Or a day pass: $1 for 24 hours, paid once, nothing renews. Either unlocks full records (sources, evidence quotes, details, migration notes, related events, verification and confidence), single events, model lifecycles with sunset dates and replacements, the corrections trail, full flag records, and full history.

Free: the last 30 days of confirmed events. Paid: full history.

Paid over the Machine Payments Protocol on Tempo: your agent's wallet is the identity, there are no accounts or API keys. The month pass is a subscription: your wallet authorizes exactly the price per period to our wallet and nothing else, revocable at any time, and we pay the gas. The day pass is one signed transfer; you pay its gas, a fraction of a cent.

Connect

MCP. MCP (Streamable HTTP), for Claude Code, Cursor, the MCP Inspector and any MCP client. Five tools: get_events and get_flags (free), get_event, get_model, get_corrections.

https://mcp.issue.md/mcp

HTTP. HTTP, from anything that can make a request:

curl -s 'https://api.issue.md/v1/events?limit=5'
curl -s 'https://api.issue.md/v1/events?vendor=openai&type=deprecation'

Paying for full records. Full records answer 402 with Machine Payments Protocol challenges in the WWW-Authenticate header and a JSON body that lists both offers. An MPP client (mppx, the Tempo wallet, the mppx CLI) signs the payment, retries the same request with the credential in the Authorization header, and gets the record. That credential is your identity for 24 hours: send it on every request. When it expires you get a 402 again; sign it again with the same wallet, which costs nothing while the pass is paid. The pass itself renews automatically every 30 days from the authorization your wallet gave, until you cancel it (DELETE /v1/pass) or revoke the key in your wallet.

# Day pass ($1, 24h) with the mppx CLI: pays once, then reads free for the day
npx mppx account create --network testnet  # once: a wallet funded from the testnet faucet
npx mppx --network testnet https://api.issue.md/v1/events/anthropic-2026-09-18-compliance-api-claude-in-chrome

# Month pass ($20, 30 days, renews) from Node: npm install mppx viem
import { Mppx, tempo } from "mppx/client";
import { privateKeyToAccount } from "viem/accounts";
const mppx = Mppx.create({ methods: [tempo.subscription({ account: privateKeyToAccount(process.env.WALLET_KEY) })] });
const res = await mppx.fetch("https://api.issue.md/v1/events/anthropic-2026-09-18-compliance-api-claude-in-chrome");   // 402 → signed → retried → the full record

Schema: https://api.issue.md/schema/event.json · Health: https://api.issue.md/healthz

Vendors watched

This is the whole list. Vendors are named to say whose public pages are read; issue.md is not affiliated with any of them. Counts are events published so far.

How it's made

Once a day an automated process reads the vendors' own public pages (pricing pages, model lists, changelogs, deprecation notices, status pages) and records what changed. A language model, run through an API, turns each change into a typed record against a strict schema; machine validation rejects anything that does not fit, and every event must carry a primary source and a quote from it. No person checks each record before it is served.

What to expect: sweeps run once a day, so a change can take up to a day to appear. The vendors watched are exactly those listed above; nothing else is covered. The service may miss events. Unconfirmed items may be wrong and may be retracted; promotions and retractions appear in the corrections trail.

History is never rewritten. When a vendor changes a date or a detail, the event gets a new version and a correction is recorded with what changed and which run saw it, so an agent that already acted on the old value can find out. "What changed since I last looked" is new events plus corrections since then.

Roadmap

Expand coverage to the full stack agents depend on: not only model providers, but the runtimes, SDKs, agent frameworks, hosting and tooling that a coding or DevOps agent breaks on.

Contact

issue.md.team@proton.me. issue.md is a small independent project.