Skip to main content

Your First Semantic Manifest

The Semantic Manifest is a JSON document generated from AXAG annotations. It catalogs every annotated operation with full parameter schemas, constraints, and safety metadata.

From Annotation to Manifest​

Given the annotation from the previous step:

Annotated search button (from previous step)
<button
  axag-intent="product.search"
  axag-entity="product"
  axag-action-type="read"
  axag-required-parameters='["query"]'
  axag-optional-parameters='["category","price_min","price_max"]'
  axag-scope="public"
  axag-risk-level="none"
  axag-idempotent="true"
  axag-description="Search the product catalog by text query with optional filters"
>
  Search
</button>

The generated Semantic Manifest entry is:

axag-manifest.json — generated output
{
  "version": "1.1.0",
  "generated_at": "2026-09-14T00:00:00.000Z",
  "source": {
    "paths": ["src"],
    "tool": "@web-axag/cli",
    "tool_version": "1.1.1"
  },
  "conformance": "intermediate",
  "actions": [
    {
      "intent": "product.search",
      "entity": "product",
      "action_type": "read",
      "operation_id": "product_search",
      "description": "Search the product catalog by text query with optional filters",
      "required_parameters": [
        { "name": "query", "type": "string" }
      ],
      "optional_parameters": [
        { "name": "category", "type": "string" },
        { "name": "price_min", "type": "string" },
        { "name": "price_max", "type": "string" }
      ],
      "risk_level": "none",
      "idempotent": true,
      "scope": "public",
      "source_file": "src/pages/search.html",
      "source_line": 1
    }
  ]
}

Manifest Structure​

Every Semantic Manifest contains:

FieldPurpose
versionThe AXAG specification version the manifest conforms to
generated_atTimestamp of manifest generation
sourceWhere the annotations were read from, and the tool that read them
conformancebasic, intermediate, or full — computed from the declared metadata
actionsArray of annotated operation definitions, sorted by intent

Each action contains the full semantic contract: intent, entity, parameters, safety metadata, and the source location it came from.

Parameter types

Parameters listed by name ('["query"]') are typed as string. To declare types and constraints, use the object form: axag-required-parameters='[{"name":"price_min","type":"number","min":0}]'.

Generation Approaches​

Manifests can be generated through:

  1. At build time — @web-axag/compiler, a plugin for Vite, webpack, Rollup, Rspack and esbuild, writes the manifest and tools into your build output
  2. In CI — npx @web-axag/cli generate src --manifest axag-manifest.json --validate runs the same compiler without a bundler
  3. In the page — registerDocument() from @web-axag/webmcp reads annotations from the live DOM, for pages with no build step

The recommended approach is build-time: nothing that reads annotations ships to the browser, and the manifest is identical whichever of the three produced it.

Next Steps​