AgentDeals · Schema
DealChange
Artificial IntelligencePricingDeveloper ToolsCloud InfrastructureConsumer Services
Properties
| Name | Type | Description |
|---|---|---|
| vendor | string | |
| change_type | string | |
| reports | string | What the record is about. 'vendor_offer' — the vendor changed its own offer, and a vendor page is where that can be read. 'our_index' — we changed what we list while the vendor's offer stood still, so |
| date | string | |
| summary | string | |
| previous_state | string | |
| current_state | string | |
| tier_direction | string | Whether the tier we list is worse, the same, or better under current_state than it was under previous_state, judged with both in hand rather than read off change_type. Where it says the tier did not g |
| impact | string | |
| source_url | string | |
| category | string | |
| alternatives | array | |
| resolution | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/agentdeals-dev/json-schema/agentdeals-dev-deal-change-schema.json",
"title": "DealChange",
"x-generated": "2026-11-01",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/agentdeals-dev-openapi.json#/components/schemas/DealChange",
"type": "object",
"properties": {
"vendor": {
"type": "string"
},
"change_type": {
"type": "string",
"enum": [
"free_tier_removed",
"open_source_killed",
"product_deprecated",
"limits_reduced",
"restriction",
"pricing_restructured",
"pricing_model_change",
"limits_increased",
"new_free_tier",
"new_tier",
"startup_program_expanded",
"pricing_postponed",
"rebranded",
"record_corrected"
]
},
"reports": {
"type": "string",
"enum": [
"vendor_offer",
"our_index"
],
"description": "What the record is about. 'vendor_offer' — the vendor changed its own offer, and a vendor page is where that can be read. 'our_index' — we changed what we list while the vendor's offer stood still, so no vendor page evidences it and the record carries no source_url. Absent means vendor_offer. Filter these out of any figure you present as vendor market activity."
},
"date": {
"type": "string",
"format": "date"
},
"summary": {
"type": "string"
},
"previous_state": {
"type": "string"
},
"current_state": {
"type": "string"
},
"tier_direction": {
"type": "string",
"enum": [
"narrowed",
"unchanged",
"widened"
],
"description": "Whether the tier we list is worse, the same, or better under current_state than it was under previous_state, judged with both in hand rather than read off change_type. Where it says the tier did not get worse we publish the record and take no risk verdict from it. Absent means we have not judged this record."
},
"impact": {
"type": "string",
"enum": [
"high",
"medium",
"low"
]
},
"source_url": {
"type": "string",
"format": "uri"
},
"category": {
"type": "string"
},
"alternatives": {
"type": "array",
"items": {
"type": "string"
}
},
"resolution": {
"$ref": "#/$defs/ChangeResolution"
}
},
"required": [
"vendor",
"change_type",
"date",
"summary",
"previous_state",
"current_state",
"impact",
"source_url",
"category",
"alternatives"
],
"$defs": {
"ChangeResolution": {
"type": [
"object",
"null"
],
"description": "Present when the change this record describes is no longer in force. state is 'reversed' when the vendor ended it and 'retracted' when the record was our error. date is the day from which it stopped being in force, or the day we established that, whichever we can source. resolved_by names the change record that ended it, when one exists. A record carrying this field never rates the vendor.",
"properties": {
"state": {
"type": "string",
"enum": [
"reversed",
"retracted"
]
},
"date": {
"type": "string",
"format": "date"
},
"detail": {
"type": "string"
},
"source_url": {
"type": "string",
"format": "uri"
},
"resolved_by": {
"type": "object",
"properties": {
"vendor": {
"type": "string"
},
"date": {
"type": "string",
"format": "date"
},
"change_type": {
"type": "string"
}
}
}
},
"required": [
"state",
"date"
]
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/agentdeals-dev-deal-change"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.