Anagram Detector API

About the Anagram Detector API

An anagram checker API for word games, puzzles and text comparison. Anagram Detector takes two words or phrases and tells you whether one is a rearrangement of the other, after normalizing both texts the way you choose: ignoring letter case, ignoring spaces, or both.

Every request returns the true or false verdict, the two cleaned strings that were actually compared, and their character counts, so you can show a player exactly why "Dormitory" and "dirty room" matched. Game builders use it to validate guesses in anagram rounds, teachers use it for vocabulary exercises, and developers use it to compare short strings without writing their own normalization rules.

The Free plan returns the verdict, cleaned text and lengths. Paid plans add the alphabetically sorted letters of each input and a similarity percentage, which help when two inputs are close but not exact anagrams, for example to tell a player they are one letter away.

How it works

Anagram Detector compares text1 and text2 by sorting their characters. Each input is first cleaned: with ignorecase (default true) both strings are lowercased, and with ignorespaces (default true) every run of whitespace is removed. The cleaned strings are split into characters, sorted, and joined; is_anagram is true only when the two sorted strings are identical. Punctuation and digits are not stripped, so "listen!" and "silent" are not anagrams unless you remove the exclamation mark first. Two identical inputs also return is_anagram: true.

cleaned_text1 and cleaned_text2 show the exact strings that were compared, and length_text1 and length_text2 are the lengths of those cleaned strings, not of the raw input. Turning ignorecase off makes "A" and "a" different characters; turning ignorespaces off makes spaces count as characters, so phrases with different spacing will not match.

sorted_text1 and sorted_text2 are the sorted character strings used for the comparison. similarity_percentage counts the characters the two cleaned texts share (for each character, the smaller of its two occurrence counts), divides by the length of the longer cleaned text and multiplies by 100, rounded to two decimals. A true anagram scores 100; "abc" against "abcd" scores 75. These three fields are null on the Free plan.

What people use it for

Word Games

Validate anagrams in word puzzles, Scrabble, and anagram-based games

Cryptography

Analyze anagram-based ciphers and cryptographic puzzles

Linguistics

Study anagram relationships in language research and text analysis

Educational Apps

Create interactive tools for teaching anagrams and word patterns

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/anagramdetector

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Optional

1
2

curl "https://api.apiverve.com/v1/anagramdetector?text1=listen&text2=silent&ignorecase=true&ignorespaces=true" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/anagramdetector

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

{
  "status": "ok",
  "error": null,
  "data": {
    "text1": "listen",
    "text2": "silent",
    "is_anagram": true,
    "cleaned_text1": "listen",
    "cleaned_text2": "silent",
    "sorted_text1": "eilnst",
    "sorted_text2": "eilnst",
    "length_text1": 6,
    "length_text2": 6,
    "similarity_percentage": 100
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 1 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Anagram Detector form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Anagram Detector API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1