Skip to content
AEN Foundation

Specificationsanddocumentation

The permanent home for AEN’s technical documents. No specification is published yet, and nothing is listed as available until it exists.

Open prototype

While the specifications are written, the Foundation is working in public on a reference prototype. It is a place to test ideas against running code, not an AEN standard, and anything in it may change.

  • JSON Schemas and examples for a business descriptor, payment hand-off, payment result and order status.
  • A sample directory, a sample business and an agent client, with a local chat UI.
  • A threat model, a payment proposal and a spec outline, with their open questions listed as issues.
  • Licensed under Apache-2.0; contributions use a DCO sign-off.

Not done: nothing here is certified or compliant with anything, there are no real payments, and wallet and token issuance for real users is an open question.

View the prototype

Specification index

Planned AEN specifications and their status
SpecificationVersionStatus
Data modelNone yet Prototype (not a standard)
Capability modelNone yet Prototype (not a standard)
Directory and discoveryNone yet Prototype (not a standard)
Agent interactionNone yet Prototype (not a standard)
Vendor integrationNone yet Under investigation
Security and trustNone yet Prototype (not a standard)
Directory interoperabilityNone yet Under investigation

What will live here

  • Technical specifications

    Normative documents, versioned and modular.

    Coming later

  • Protocol documentation

    How agents and services talk to each other.

    Coming later

  • Data schemas

    Machine-readable definitions of the common data model.

    Coming later

  • Implementation guides

    Building a compatible directory, vendor integration or agent client.

    Coming later

  • Version history

    What changed between specification versions, and why.

    Coming later

  • Compatibility requirements

    What an implementation must do to call itself compatible.

    Coming later

Versioning intent

Specifications are intended to be modular and versioned so the engineering can evolve without forcing every participant to adopt every future capability at once. The versioning scheme will be defined with the first specification.

Compatibility

There are no compatibility requirements, certifications or compliant implementations yet. Running the prototype does not make anything compatible. This page will say so plainly until that changes.

Prototype repository