Verdict

All 6 tools

Find one concept that goes by several names across your UI, docs and API.

check_terminology

Before: what you give it

The example input, as sent.

onboarding UI: Create your first workspace. Add a client to get started. Your team members can see every project.
docs: A project contains clients. Invite a teammate to your account. Each workspace has its own billing seat.
API reference: POST /v1/teams creates a team. The account_id identifies the organization that owns the team.

After: what comes back

A real run of this tool has not been captured for this page yet, so there is no sample to show. Run the request below to see the answer for yourself.

What you get

Concept clusters showing which source uses which term, with the drifting ones flagged.

What gets better

A user meets the same word for the same thing on every surface, and so does the API consumer.

When to use it

When the product, its docs and its API have been written by different people.

What it cannot do

Combined source text is capped at 30,000 characters. It matches meaning, so it can miss a rename that changes nothing in the wording.

Run it

Two free calls a day with no key. Send your own Anthropic key in an x-anthropic-key header to lift the limit.

curl -X POST https://verdict.allthepossibles.com/api/check_terminology -H 'content-type: application/json' -d '{"sources":[{"label":"onboarding UI","text":"Create your first workspace. Add a client to get started. Your team members can see every project."},{"label":"docs","text":"A project contains clients. Invite a teammate to your account. Each workspace has its own billing seat."},{"label":"API reference","text":"POST /v1/teams creates a team. The account_id identifies the organization that owns the team."}]}'

Full input schema in the docs

The other reviews