1 · Scope
Identify the agent role
The reviewer states what an agent, agent builder, or interoperable agent system can do with the product or protocol, and why that capability is material.
Editorial policy 1.0 · Effective 3 September 2026
The directory applies one public inclusion test to vendor submissions, community contributions, and maintainer-authored entries. Passing that test establishes taxonomy fit; it does not establish product quality.
Evidence standard
1 · Scope
The reviewer states what an agent, agent builder, or interoperable agent system can do with the product or protocol, and why that capability is material.
2 · Verify
The reviewer checks maintained first-party material and rejects thin integrations, unsupported marketing, and generic technical compatibility.
3 · Classify
Each accepted listing receives the most specific supported classification. Classification is not a rating, award, recommendation, or substitute for due diligence.
Experience and verification
Unless a listing explicitly describes a dated test and its conditions, it should be read as a review of public documentation, not evidence that the directory installed, purchased, benchmarked, or security-tested the tool. Superlatives and comparative claims require a disclosed method and supporting evidence; otherwise they are not editorial conclusions.
Review cadence
Every proposed listing is reviewed when it enters the directory. Existing entries are rechecked when a reader, vendor, contributor, or maintainer reports a material change or correction. The directory does not currently promise a fixed recurring re-review interval, so fast-changing facts such as price, availability, limits, and licence terms should be confirmed on the linked first-party source before a decision is made.
Conflicts, sponsorship, and affiliate links
Ordering
Homepage listings are shuffled. Category and tool ordering can use an explicit maintenance value and otherwise falls back to readable label or name ordering. Placement does not represent quality, popularity, payment, market share, or editorial preference. Any future ranked recommendation will require a separate published methodology and will be labelled as a ranking.
Public record
Directory content is stored in a public GitHub repository. Proposed additions and material edits can be examined in pull requests, including the contributor identity and discussion available there. Public history is useful provenance, but submitter identity is not the same as editorial authorship or independent verification.
Corrections, appeals, and removals
A reader or vendor may challenge a fact, classification, rejection, or removal with a specific first-party source. The maintainer may correct the wording, add a caveat, reclassify, temporarily unpublish, or remove an entry when evidence no longer supports it. A vendor request alone does not require publication or deletion of accurate public-interest information. The full process is documented in the corrections policy.
Content and data rights
The repositories and live JSON/CSV exports are public for inspection, citation, and contribution, but their availability does not grant a separate open content or compiled-data licence for bulk republication. Link to the canonical page and attribute short quotations. Product names, logos, documentation, and other third-party materials remain subject to their owners' terms. Any future immutable research release will state explicit reuse terms next to that release.
Want to inspect or improve the evidence behind a listing?
Read the contribution guide