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."}]}'
The other reviews
- critique_experience
Find the problems in a design before a user or an engineer does, ranked by how badly each one hurts.
- generate_state_matrix
List every state a feature can be in, including the ones nobody drew.
- map_journey
Map the stages around a goal and name the entries, exits and interruptions the flow forgot.
- audit_copy
Review buttons, errors, empty states, confirmations and notifications, and rewrite the ones that fail.
- find_assumptions
Pull the unchecked beliefs out of a brief and turn each into a question you could answer this week.