Community API Properties
Community-contributed properties that extend the core API Commons vocabulary. These represent patterns emerging from real-world API implementations and contribute to an ever-growing shared vocabulary for API operations.
AsyncAPI
AsyncAPI allows you to describe the surface area of event-driven APIs in a machine-readable way, providing a way of defining the protocol, channels, topics, messages, and the schema that are being published and subscribed to. AsyncAPI is a sister specification to the OpenAPI specification, sharing some common properties, as well as support of JSON Schema, but AsyncAPI provides a wider number of protocols than OpenAPI is designed to cover.
View
Blog Feed
An Atom or RSS feed for a blog or is still an essential item, and despise the demise of Google Reader, it is still a fundamental aspect of any blog. While blogging is not as popular as it once was, it is still a useful way to keep API consumers up to date with what is happening with change across each API they are depending on.
View
FinOps Framework
A FinOpsFramework property references a document describing how an API provider or platform aligns to the FinOps Framework — the operational framework published by the FinOps Foundation for managing cloud, SaaS, and AI financial operations. The 2025 Framework revision expanded coverage to four scopes — public cloud, SaaS, data center, and AI. A FinOps Framework alignment document describes which capabilities the provider supports, at what maturity level, and how they enable customer FinOps practices such as cost allocation, budgeting, forecasting, and unit economics.
View
FOCUS Billing Export
A FocusBillingExport property references an endpoint or documentation for a billing data export that conforms to the FOCUS (FinOps Open Cost and Usage Specification) schema — the cross-vendor open standard maintained by the FinOps Foundation for normalizing cloud, SaaS, and PaaS billing data. A FOCUS-conformant export allows API consumers, enterprise buyers, and FinOps tools to ingest cost and usage data in a consistent format without custom transformation.
View
FOCUS Conformance Report
A FocusConformanceReport property references a published document describing how a provider's billing data maps to the FOCUS schema — including any gaps between native fields and the FOCUS column definitions. The FinOps Foundation's certified conformance program requires providers to publish a native-to-FOCUS column mapping and a conformance gap report. Linking this document makes verifiable billing data compatibility discoverable by FinOps tools and enterprise procurement teams.
View
FOCUS Contract Commitments
A FocusContractCommitments property references an endpoint or document for commitment-based pricing data structured according to the FOCUS Contract Commitment Dataset (introduced in FOCUS v1.3). This supplemental dataset isolates reserved instance, savings plan, and enterprise discount program terms — including commitment start and end dates, remaining committed units, and commitment type — from per-row cost and usage data, enabling FinOps tooling to reconcile commitment purchases against actual consumption.
View
GHG Protocol Report
A GHGProtocolReport property references a published greenhouse gas emissions report for an API provider or platform, structured according to the GHG Protocol — the global standard for measuring Scope 1, 2, and 3 greenhouse gas emissions. Cloud provider carbon APIs from AWS, Azure, and GCP all align their calculations to GHG Protocol categories. Linking a GHG Protocol report from an APIs.json index makes the provider's emissions posture discoverable by enterprise customers with Scope 3 supply chain reporting requirements.
View
GitHub Organization
A GitHub Organization is commonplace for larger more organized API producers, establishing a place where you can find SDKs and other code used for integration, but also machine-readable artifacts, issues, discussions, and other useful outputs from everyday API operations that will help provide nutrients for an API ecosystem.
View
GitHub Repository
GitHub repositories are great for making SDK and other artifacts developers will need to put an API to work, but you can also publish OpenAPI, examples, and even run your entire API portal using GitHub pages. A GitHub repository has proven itself to be an essential building block of any public API program, and powers API Commons.
View
GraphQL Schema
The GraphQL Schema is a machine readable collection of schema organized into a graph. The GraphQL Schema has emerged as a proven way to stitch together much of the API sprawl that has emerged behind the infrastructure, integrations, and applications that we depend on to do business today.
View
Invoice Reconciliation
An InvoiceReconciliation property references documentation explaining how an API provider's billing data maps to issued invoices — including how to match billing export rows to invoice line items using invoice identifiers. FOCUS 1.2 introduced dedicated Invoice ID columns specifically to enable this reconciliation. For enterprise API consumers, the ability to tie API usage records to financial invoices is a compliance and audit requirement. Linking reconciliation documentation makes this mapping discoverable alongside the API.
View
JSONSchema
The JSON Schema allows for the validation of JSON objects, and is used by OpenAPI & AsyncAPI. JSON Schema is a fundamental building block of the enterprise, and is ubiquitous across operations, whether teams are aware of it or not. JSON Schema is essential to standardizing and streamlining API operations across REST, GraphQL, and event-driven APis.
View
Naftiko Capability
A NaftikoCapability property references a Naftiko capability YAML specification — a single declarative file that defines what APIs are consumed upstream, what surfaces are exposed (REST, MCP, Agent Skills), and what governance, identity, and telemetry rules apply. Capability specs are the deployable unit of the Naftiko platform: each one is validated by JSON Schema, committed to Git, and serves as both the implementation artifact and the governance contract. Publishing a capability spec makes it possible for AI agents, orchestration tools, and developer portals to discover and invoke governed API capabilities without direct knowledge of the underlying provider APIs.
View
OpenAI Plugin Manifest
OpenAI uses a plugin manifest that references an OpenAPI to allow for extending ChatGPT, and introduce more AI capabilities. Providing a ready to go OpenAI Plugin Manifest for API consumers to use when extending ChatGPT will become a new type of application or integration to consider.
View
OpenAPI
The OpenAPI Specification provides a formal standard for describing HTTP APIs, describing the surface area of request and response APIs. OpenAPI can be used to publish documentation, generate mock servers, and produce SDKs. An OpenAPI has become an expected artifact by API consumers and is widely considered to act as the technical contract between API produce and consumer and has become common for many leading API providers.
View
OpenCost Allocation API
An OpenCostAllocationAPI property references an API endpoint that exposes Kubernetes and cloud infrastructure cost allocation data in a format compatible with the OpenCost Allocation API specification. The OpenCost API returns workload cost data aggregated by namespace, deployment, pod, service, or label, and supports time-window queries and shared cost distribution. Indexing an OpenCost-compatible allocation endpoint makes container cost data programmatically accessible to FinOps dashboards, chargeback tools, and engineering teams.
View
OpenCost Specification
An OpenCostSpecification property references documentation describing how an API or platform's cost reporting conforms to the OpenCost Specification — a CNCF Incubating project that defines a vendor-neutral standard for measuring and allocating Kubernetes and cloud infrastructure costs. OpenCost covers cluster asset costs, workload cost allocation by namespace, deployment, pod, and label, and idle resource cost distribution. Linking an OpenCost conformance document makes Kubernetes cost data interoperable with FinOps tooling.
View
Postman Collections
A Postman Collection is a machine-readable collection of APIs for use in client, testing, and automation. Postman Collections provides a portable, machine-readable way of defining an API and making available for consumers via a Postman workspace or embedded via documentation and other websites. Collections bundle documentation, can be mocked, and work with the wider Postman platform ecosystem.
View
Postman Workspaces
A Postman Workspace is a cloud space where you can store collections, OpenAPI, tests, and other elements. Think of a Postman Workspace as a GitHub repository, but specifically for APIs, providing a place you can organize collections, OpenAPIs, monitors, tests, and other ways to automate API operations and integrations. Workspaces can be public, private, or partner access only, helping you organize your APIs into individual spaces that are isolated for different audiences.
View
SCI Report
An SCIReport property references a published carbon intensity report for an API or service calculated using the Software Carbon Intensity (SCI) specification — an ISO-ratified standard from the Green Software Foundation. An SCI report documents the measured or estimated carbon intensity for a specific version or deployment of the API, including the methodology, data sources, energy and embodied carbon inputs, the chosen functional unit, and the resulting score. Regular SCI reports enable tracking of carbon efficiency improvements over time.
View
Software Carbon Intensity
A SoftwareCarbonIntensity property references a published Software Carbon Intensity (SCI) score or methodology document for an API or service. SCI is an ISO-ratified standard from the Green Software Foundation quantifying carbon intensity using the formula SCI = ((E * I) + M) per R — where E is energy consumed, I is the marginal carbon intensity of electricity, M is embodied carbon, and R is a functional unit such as per API call or per user. Publishing an SCI score makes carbon efficiency measurable and comparable across API providers.
View
Webhooks
Webhooks are a way to communicate between applications by sending data to another application when an event occurs. Webhooks are HTTP-based callback functions that are automated and triggered by an event in a source system, then sent to a destination system, providing event-driven capabilities utilizing simple HTTP "reverse APIs".
View