Word Lexicon Analyzer API

About the Word Lexicon Analyzer API

Pass any target string to the endpoint to evaluate its letter arrangement, repetition, and dictionary status. The response computes alphabetical letter order, verifies if an anagram can form a palindrome, and flags words with no repeating letters. It also checks whether the word is playable in Scrabble and assesses rare letters for pangrams.

What people use it for

Word Game Validation

Puzzle game backends verify player submissions against Scrabble eligibility and immediately flag valid palindromes for bonus scoring.

Anagram Puzzle Generation

Crossword and puzzle constructors use sorted letter forms to group matching anagrams and test word rearrangements for hidden riddles.

Vocabulary Drill Generation

Language learning platforms detect isograms and alphagrams to build spelling exercises focused on words with non-repeating letters.

Pangram Challenge Construction

To build daily pangram challenges, editorial teams filter candidate lists to find terms that supply rare and uncommon letters.

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/lexicon

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

1
2

curl "https://api.apiverve.com/v1/lexicon?word=listen" \
  -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/lexicon

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

{
  "status": "ok",
  "error": null,
  "data": {
    "word": "listen",
    "isAlphagram": false,
    "sortedForm": "eilnst",
    "isPalindrome": false,
    "hasAnagram": false,
    "isIsogram": true,
    "isPangramCandidate": false,
    "isScrabbleValid": true,
    "canBePalindromeAnagram": false
  }
}

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 — 2 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 Word Lexicon Analyzer 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 — Word Lexicon Analyzer 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