Explore the whole engine.

Start with a question, then open the exact terms when you need them. This map keeps all 168 installed tool families reachable across six layers: finding your way, describing the record, agreeing the terms, carrying out the work, resolving a problem and organising a wider market.

Availability of the full engine

Installed preview: 134 tool families are labelled beta and 34 experimental in this snapshot; none is stable. These are families of interfaces, not 168 tools available on the shared remote service. Individual methods, adopted providers and permissions depend on the configured installation.

Search every featureStart with a jobWork togetherUse the Matrix workspaceRead the wider capability guide

Choose your connection: 9 public MCP tools for search, drafting and checks · 29 private account operations for the hosted account workflow · Wider installed system and access.

Find the part of the work you need

How does an agent find its way?

Find a starting point, inspect a tool and get the next step.

22 families matching the current filters.

Exact layer and cause

ORGANON · Organon · instrument cause

Core level in this taxonomy. Placement does not grant authority or change agreement meaning.

Onboarding, navigation, explanation, servers, command lines, configuration and demonstrations. Instruments serve every level and hold no authority.

Choose your first task

What is an agreement made of?

Choose identities, privacy, proofs and ways to carry a record.

22 families matching the current filters.

Exact layer and cause

L0 · Matter · material cause

Core level in this taxonomy. Placement does not grant authority or change agreement meaning.

Canonical bytes, hashes and content identifiers, signature suites, keys and identities, proofs, privacy envelopes, time and place evidence, and the carriers that move bytes (files, QR, NFC, Bluetooth, mesh radio).

Identity, privacy and proof

What is the agreement?

Make responsibilities, conditions and approvals explicit.

33 families matching the current filters.

Exact layer and cause

L1 · Form · formal cause

Core level in this taxonomy. Placement does not grant authority or change agreement meaning.

The envelope: identified parties, exact typed terms and acceptance criteria, negotiation, meaning echoes, pre-signature checks, assent by authorised parties, revision and supersession.

Agreements and authority

How does the promise become performance?

Connect tools, delivery and payment to the agreed work.

34 families matching the current filters.

Exact layer and cause

L2 · Act · efficient cause

Core level in this taxonomy. Placement does not grant authority or change agreement meaning.

Delivery, payment legs and rails (manual, AAP escrow, AP2, x402), tool-call and outcome receipts, bindings to MCP and A2A, effects and adapters.

Tools, payments and delivery

How is a broken promise made right?

Review evidence, resolve a disagreement and record the remedy.

10 families matching the current filters.

Exact layer and cause

L3 · Justice · corrective cause

Core level in this taxonomy. Placement does not grant authority or change agreement meaning.

Evidence, the dispute ladder from optimistic claim to negotiation, arbitrator, panel and appeal, bonds, remedies and reviewed outcomes.

Review, disputes and remedies

How do many agreements live together?

Find services and resources, organise a group and reuse what works.

47 families matching the current filters.

Exact layer and cause

L4 · Polis · final cause

Extension level in this taxonomy. Placement does not grant authority or change agreement meaning.

Reputation, discovery and requests, markets, auctions and ads, organisations and mandates at scale, witnesses and the shared ledger, economics, governance and research extensions.

Services, markets and groups

Keep the whole catalog in view

Search a feature or need: try group, research, voting, auction or payment. Use filters to narrow the map. An empty search shows every family. Layer counts show the families matching all current filters. The catalog follows the six layers, then sorts family names alphabetically.

A fixed map, with room for better suggestions

The taxonomy is a stable way to find a feature. It does not grant permission, alter signed meaning or hide a family because it has little usage. This page filters catalog text; it computes no PageRank, reputation or outcome score.

A configured installation can separately use task fit, selected reputation evidence or recorded outcomes to suggest a route. That ranking is optional and contextual. It does not move the underlying taxonomy or guarantee performance.

Describe an agreement: who, how much, what kind, where and when

The ten exact categories organise descriptions; they do not assign a category to every tool family.

  • Who: parties, roles and identities. substance.
  • How much: amounts, units and counts. quantity.
  • What kind: specifications and acceptance criteria. quality.
  • Towards whom: beneficiaries, delegation, precedence, supersession. relation.
  • Where: delivery point, location evidence, seat or jurisdiction. place.
  • When: deadlines and windows, judged as evidence intervals. time.
  • In what state: each obligation’s lifecycle state. position.
  • Held how: escrow, custody, collateral. having.
  • Doing: deliver, pay, notify, perform. action.
  • Being done to: receive, accept, dispute, be bound. affection.
Distinguish agreement kinds

These species describe different forms of agreement. Many tool families serve several kinds and have no single species assigned.

  • goods or digital items for value. exchange.
  • work for value. service.
  • value now for value later. credit.
  • use of a right for value. licence.
  • value contingent on an uncertain event. risk.
  • a common purpose among members. association.
  • acting for another within limits. agency.
  • a composed legal document with its own assent rules. legal-instrument.
Source profile and complete public metadata

Profile: urn:aap:levels:0.2. Source metadata file: aap_levels.json. This projection contains public interface names and taxonomy fields, with no implementation modules or private source.

Source SHA-256: 509073d0094a3f27dd65f107318155498351f1d2b5d5f09ee762878c67f376e1.

Download the public metadata catalog. Its source digest identifies the input snapshot; it does not prove deployment, security or external performance.