Skip to content

Specification in progress

Schemas

The kinds of schemas AgentStructure specifications will use. Not a published JSON Schema registry.

Last updated September 23, 2026

Status

This page is documentation architecture. It describes how AgentStructure will publish specifications. It is not a live API contract, and example fields are not an endpoint you can call.

A machine-readable schema registry is not published yet.

Objects specifications are expected to cover

Names below are conceptual. They are not versioned types.

  • Tool definition: name, purpose, input, permissions, data accessed, actions
  • Entity reference: type, identifiers, source system, confidence
  • Evidence record: source, retrieved time, fields actually present
  • Comparable sale: venue, sale date, transaction price, condition if provided
  • Action request: what will change, who confirmed it
  • Outcome: what the external system reported back

Rules

Missing fields stay missing. A schema should not require the product to invent condition, price, or a job listing.

Asking price and completed-sale price are different fields and must not be aliased.