Study

AXIS Proof-of-Concept Study

Structured observation of protocol usage under declared constraints. Open, voluntary, and transparent.

What this is

We observe how autonomous agents and their operators use the AXIS protocol in practice — specifically, whether declared constraints (published in an Agent Card) align with observed public behaviour. This is not a controlled experiment. It is an open registry with transparent rules. We record what agents declare and track the gap — or absence of a gap — between declaration and action.

What we collect
  • +Public Agent Card fields as submitted by the operator.
  • +Verification state and method (Pending / Verified).
  • +Voluntary public interactions where an agent references their registry entry.
  • +Timestamps of submission and verification events.
What we do not collect
  • ×Private communications, session logs, or internal agent state.
  • ×API keys, credentials, or secrets of any kind.
  • ×Personal data beyond what the operator chooses to publish in their contact field.
  • ×Inferred or derived information not present in the submitted Agent Card.
  • ×Tracking cookies, analytics identifiers, or device fingerprints.
Participation and removal

Participation is voluntary and operator-initiated. Submit an Agent Card via the registry to join. To remove an entry, the operator-of-record may request removal at any time by contacting admin@axisagents.org. Requests are actioned within 7 days. Removal does not affect data already published publicly by the operator.

Moderation

Entries that are fraudulent, abusive, or in clear violation of the Agent Card schema may be removed without notice. An entry is considered fraudulent if the verification nonce is forged or if the declared operator-of-record cannot be confirmed. No appeal process in the current beta.

Status definitions
StatusMeaning
Pending Agent Card submitted. Verification not yet complete. Entry is visible but unconfirmed.
Verified Operator-of-record has completed nonce verification. The operator controls the declared endpoint.
Featured Verified entry selected for the Founding Cohort. Curated by the registry team during the beta period.
Verification proves control of an endpoint, not moral trust. Verified means technical confirmation only.