Skip to content

Ecosystem

The Foundation provides common engineering. Independent organisations build compatible implementations on top of it.

How AEN fits togetherAI agentsAny provider; each chooses its directoriesIndependently operated directoriesGeneral directoryAny industrySpecialised directoryOne industryRegional directoryOne country or regionBusinesses and vendorsListed in the directories they choosebuilt onAEN FoundationOpen specifications for data, capabilities,discovery, agent interaction, trust.Owns none of the directories above.
Illustrative. A directory can be general, specialised by industry or limited to a country. Any organisation can operate one, and agents pick which to use.

Who takes part

AEN Foundation Planned non-profit
Develops and maintains the specifications. Does not own the directories built with them.
Directory operators Independent companies
Run their own compatible directory, with their own brand, domain, policies, listings and business model.
Technology vendors Platforms and providers
Register the services and integrations they already offer, such as payments, booking or inventory.
Businesses Of any size
Publish structured information and capabilities through a compatible directory. Their website stays as it is.
AI agents Any provider
Choose which compatible directories to use, based on the request, coverage, specialisation and trust.
Developers and researchers Implementers
Review and contribute to specifications, and build compatible implementations.

Independent directories

AEN does not require a central directory. A company can use AEN engineering to run its own, with its own brand, domain, infrastructure, registration policies, listings and commercial model, and remain responsible for operating it. A directory can cover any industry or specialise in one, or serve a single country or region.

Directories start out operating individually. Interoperability between them is a possible later capability, optional for every operator.

How an agent chooses

Agents decide which compatible directories to use. They may weigh:

  • The user’s request
  • Geographical coverage
  • Industry specialisation
  • Available business information
  • Supported capabilities
  • Reliability and trustworthiness
  • The agent’s own integration preferences

Small businesses

A local food shop already has a website, menu, opening hours and perhaps an ordering and payment system. It should not have to build a new application for every AI platform. By publishing structured information through a compatible directory, an agent can understand:

  • What the business offers and where it operates
  • Which products or services are available, and at what price
  • When they are available
  • Which actions can be performed
  • What requirements or restrictions apply

The existing website stays useful for human visitors.

Vendors and platforms

Payment providers, booking platforms, inventory systems and e-commerce platforms already expose APIs. They can register supported services and integrations in a compatible directory, as structured vendor information with capabilities and connection details.

This is not an API marketplace. APIs may be used by implementations; AEN describes how services and capabilities are represented, discovered and used.