APIs.json Schema
The JSON Schema definitions that underpin the APIs.json format. These schemas describe the structure of indexes, API entries, properties, and all the metadata needed to properly describe API contracts and operations.
AID
A unique identifier for the collection, consisting of [root domain]:[string] (ie. apis.json:spec-example).
View
APIs AID
A unique identifier for the api, consisting of [root domain]:[string] (ie. apis.json:spec-api).
View
APIs Name
URL of an image which can be used as an "icon" for the API if displayed by a search engine.
View
APIs Properties Type
Different properties of an API, see the list of APIs.json properties for a complete list.
View
Image
Web URL leading to an image to be used to represent the collection of APIs defined in this file.
View
Kind
Classifies the entity the APIs.json document is about, separately from the document `type`. Conventional lowercase values include `company`, `opensource`, `government`, `topic`, `standard`, `protocol`, and `non-profit`. Replaces the prior `x-type` / `xType` vendor extensions; new files should use `kind`.
View
Prompts
An optional collection of AI prompts that apply to the whole index (top level) or to an individual API. Each entry uses the same shape as a property (type, url or data, name, description, tags), with a type such as `Prompt`, `AgentPrompt`, or `PromptTemplate`. Introduced in 0.21.
View
Rules
An optional collection of governance rulesets that apply to the whole index (top level) or to an individual API. Each entry uses the same shape as a property (type, url or data, name, description, tags), with a type such as `SpectralRules`, `Rules`, or `GovernanceRules`. Introduced in 0.21.
View
Tags
This is a list of descriptive strings which identify the contents of the APIs.json file. Represented as an array.
View
Type
The document kind of this APIs.json file. Canonical value is `Index` — an index of one or more APIs and their associated properties. Reserved values are `Index`, `Collection` (multiple APIs), and `Blueprint` (a template for a new API). Use the separate `kind` field to classify the entity the document is about (company, government, opensource, topic, standard, etc.).
View
Workflows
An optional collection of multi-step API workflows that apply to the whole index (top level) or to an individual API. Each entry uses the same shape as a property (type, url or data, name, description, tags), with a type such as `Arazzo`, `ServerlessWorkflow`, or `Workflow`. Introduced in 0.21.
View