@aeo-kit/schema

JSON Schema definitions for the AEO manifest format — the machine-readable file that declares which tools an AI agent can use, under what intents, with what trust boundaries, and how to test them.

Schemas

| File | Purpose | |---|---| | src/index.schema.json | Root manifest — ties everything together | | src/tools.schema.json | Tool / endpoint declarations | | src/intents.schema.json | Agent intent & workflow guardrails | | src/trust.schema.json | Trust levels, auth, and consumer ACLs | | src/provenance.schema.json | Origin, audit trail, and integrity hashes | | src/tests.schema.json | Inline test cases with assertions |

All schemas use JSON Schema draft 2020-12 and reference each other via relative $ref URIs.

Fixtures

The fixtures/ directory contains example manifests used for validation tests:

• fixtures/valid/ — documents that must pass validation.
  • minimal.json — smallest possible valid manifest.
  • full.json — manifest exercising every optional field.
• fixtures/invalid/ — documents that must fail validation.
  • missing-required-fields.json — omits all required root properties.
  • bad-tool-id.json — tool id violates the naming pattern.
  • empty-tools.json — tools array is empty (minItems: 1).
  • bad-version.json — version and aeo fail pattern checks.
  • extra-properties.json — unknown property blocked by additionalProperties: false.

Quick reference

A minimal AEO manifest looks like this:

{
  "aeo": "0.5",
  "name": "my-service",
  "version": "1.0.0",
  "tools": [
    {
      "id": "get-item",
      "description": "Fetch an item by ID."
    }
  ]
}

Spec version

These schemas target AEO spec 0.1 (unstable). Fields and structure will evolve as the spec matures.