Methodology

Start with the job

AgentsUse begins with the work an agent needs to do, then checks whether a tool can do it, what setup it needs, and where its limits are. Directory size is not the goal. A profile is published only when it can help a reader set up, choose, reject, or safely operate a tool better than a raw registry or repository page can.

Status flow

Every record moves through explicit states: candidate (discovered, not normalized), draft (normalized, waiting for review), verified (public facts have source evidence), and published (a public page exists). Deprecated and archived states handle stale records. Candidate and draft records never get a public page and never appear in the sitemap.

Verification labels

• Source verified: a public claim traces to an official or primary source checked on the date shown.
• Config checked: a published configuration matches the source structure and contains no real credentials.
• Locally tested: AgentsUse ran the setup and recorded the version, date, and result.
• Vendor claimed: the vendor states the claim and AgentsUse has not independently checked it. Labeled as such.
• Community reported: a third party reports the claim. It never creates a public claim by itself.

Only source verified, config checked, and locally tested claims support strong profile copy. Unknown fields stay empty or are shown as unknown. AgentsUse does not invent pricing, features, ratings, star counts, benchmarks, or compatibility.

Publication gate for a tool profile

A profile can be published and indexed only when all of the following are true:

• The record is published with at least source-verified evidence, a reviewed one-sentence pitch, and a primary category.
• At least five capabilities are verified, or the page explains why fewer public capabilities exist.
• Official site and documentation URLs are verified. Pricing is sourced or shown as unknown. Open-source and license claims are sourced.
• At least one real setup path exists: install, API quick start, package, hosted setup, or MCP config with placeholders only.
• At least two meaningful relationships exist, such as alternatives, verified compatibility, or stack membership.
• Every displayed metric carries a checked date. The page names a limitation or avoid-if case from sourced facts.
• Title and description are unique, structured data matches visible content, and no review item is left open.

Comparisons and integrations stay gated

Comparison and framework integration pages stay unpublished or noindexed until both sides are verified, the shared dimensions are sourced, and the page can give a scenario-based recommendation without invented facts. Compatibility is a sourced fact, never inferred because two tools share a category.

Sponsorship separation

Sponsored placement never changes inclusion, order, quality scores, alternative order, or a comparison conclusion. Any future sponsored unit will be labeled Sponsored and rendered separately from editorial results. See the about page, disclaimer, and terms of use.

Corrections

Send corrections with a source link through the contact page. A verified correction updates the profile and its check date. Browse the tools directory or the guides.