Use the API when your product needs structured model-change records: releases, updates, pricing, access, availability, sources, confidence, and timestamps.
API / MCP · private beta in preparation
Source-backed AI model-change data for builders and agents.
The same record behind the Modelmark app is being prepared for API and MCP access, so products and agents can retrieve model-change context with sources, confidence, timestamps, and correction history attached.
Being prepared for private beta — not yet public
The problem for systems
Model information changes faster than systems remember.
Model names, pricing, access, availability, capabilities, and deprecations can change across different sources. If your product or agent relies on stale or unsourced model facts, it can make outdated recommendations, route users poorly, or explain choices without evidence.
What Modelmark records
One typed record for each kind of change.
- Model releases
- Model updates
- Pricing changes
- Access changes
- Availability changes
- Capability changes
- Deprecations and retirements
- Open-weights releases
- Benchmark claims, as claims
- Corrections and supersessions
API vs MCP
Two surfaces, one record.
Use MCP when an AI agent needs to ask for model-change context and receive an answer with provenance attached.
Provenance
Provenance is the product.
A model-change record is only useful if you can see where it came from and how much confidence to place in it. Modelmark is being designed so source, confidence, timestamps, correction state, and methodology version travel with the record.
- Source URL
- Source type
- Captured or snapshot context where available
- Confidence label
- Happened / effective / detected / published / verified timestamps
- Correction or supersession state
- Methodology version
Example shape
What a sourced model-change response can look like.
A Modelmark response is meant to carry the record and the evidence together: what changed, when it was published, source type, publisher, confidence, and methodology version.
Illustrative private-beta response shape. Not public production API documentation.
RESTrequest
GET /v1/changes?since=2026-06-01T00:00:00Z{
"dataset_last_updated_at": "2026-06-12T08:55:00Z",
"query": { "since": "2026-06-01T00:00:00Z", "since_field": "published_at" },
"results": [
{
"id": "ce_8f3a1c20",
"canonical_model_id": "aperture-sonnet-2",
"event_type": "model_released",
"importance": "major",
"summary": "Aperture released Sonnet 2, available via API.",
"change": { "kind": "new_model", "field": "model.status", "new_value": "available" },
"published_at": "2026-06-09T18:20:04Z",
"confidence": "official",
"methodology_version": "1.0.0",
"sources": [
{
"url": "https://aperture.example/blog/sonnet-2",
"source_type": "official_blog",
"publisher": "Aperture",
"is_official": true,
"is_primary": true
}
]
}
]
}get_source_for_claim{
"claim": "Northwind Pro output price changed to $9.00 / 1M tokens.",
"confidence": "official",
"methodology_version": "1.0.0",
"source": {
"url": "https://northwind.example/pricing",
"source_type": "pricing_page",
"publisher": "Northwind",
"is_official": true
}
}Private beta status
API and MCP access are being prepared for private beta. There is no public firehose, public pricing, or public key issuance yet.