Agentic means software can discover and interpret the capabilities a provider publishes.
IRI Facility API 2.0 · Development specification · Draft
The Facility API is one technical contribution to the wider IRI effort. Its 2.0 development line gives infrastructure a shared way to describe resources, their relationships, and applicable operations. Engagement, trust, policy, and governance remain essential to putting these interfaces to work.
Flexible resource descriptions
A common resource model can represent computing, storage, data, and other scientific services without forcing every provider's details into one universal object. resource_type identifies a resource's semantic type; attributes holds type-specific details. Shared Resource Definition Profiles and a governed vocabulary give those details meaning across implementations.
Explore the resource model and published profiles.
Discoverable capabilities
Resources advertise relationships and applicable operations through _links. Registered relations let clients follow what a provider actually publishes rather than guess URL conventions. A service-desc link identifies the deployed service description, normally an OpenAPI document describing that running service's methods, inputs, responses, errors, and security requirements.
An operation link describes applicability. Executing the operation still depends on current authorization, resource state, and available capacity.
Read Hypermedia and Discovery and Understanding service-desc.
Useful to workflows and authorized AI agents
Explicit semantics and machine-readable operation contracts give conventional workflow tools and authorized AI agents the same discovery process. Software can inspect a resource, interpret published profiles and relations, and validate an intended request against a deployed contract before calling it.
A discovery journey
A client discovers a compute resource, follows its links to related storage, and finds an advertised operation. It consults the deployed OpenAPI description to understand the request and its security requirements, then makes an authorized request. The provider continues to decide whether that request can proceed.
See the agentic discovery explanation for the technical model.
Version-specific contracts, independent adoption
The authoritative repository maintains the accepted 1.0 specification and the 2.0 development specification independently. Each provider chooses its adoption schedule and publishes the contract for its own service. An implementation listing does not establish a shared version or feature set.
This overview introduces the model. Use the version-specific documentation, architecture explanation, and active specification source for implementation work.