Word Lexicon Analyzer API GET

Documentation Start for free →

Lexicon is a simple tool for analyzing words. It returns various properties of the word.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/lexicon

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Word Lexicon Analyzer response payload
  }
}

About the Word Lexicon Analyzer API

Lexicon works by analyzing the word provided and returning various properties of the word. It uses various sources to determine the properties and returns the data.

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
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Word Lexicon Analyzer

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets

Questions.

Common questions about the Word Lexicon Analyzer API.

Read the docs →

What does the Word Lexicon Analyzer API do?

Lexicon is a simple tool for analyzing words. It returns various properties of the word.

How do I authenticate Word Lexicon Analyzer API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Word Lexicon Analyzer API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Word Lexicon Analyzer API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Word Lexicon Analyzer API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Word Lexicon Analyzer API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

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

Parameter	Type	Example	Description
`word`Required	string	`listen`	The word to analyze

Example request

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.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

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.

Sample response

{
  "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.

Field	Type	Example	Description
`word`	string	`"listen"`	The analyzed word
`isAlphagram`	boolean	`false`	Whether the word's letters are already in alphabetical order
`sortedForm`	string	`"eilnst"`	The word's letters sorted alphabetically, used to match anagrams
`isPalindrome`	boolean	`false`	Whether the word is a palindrome
`hasAnagram`	boolean	`false`	Whether the word has anagrams
`isIsogram`	boolean	`true`	Whether the word repeats no letter
`isPangramCandidate`	boolean	`false`	Whether the word contributes rare letters useful in a pangram
`isScrabbleValid`	boolean	`true`	Whether the word is playable in Scrabble
`canBePalindromeAnagram`	boolean	`false`	Whether the letters can be rearranged into a palindrome

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.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

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

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

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.

Plan	Per month	Credits	Word Lexicon Analyzer calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

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.

Compare all pricing tiers →

Call it from cURL — GET /v1/lexicon

No SDK to install — this is a plain HTTPS call to /v1/lexicon with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/lexicon" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/lexicon-apiSource, issues and the examples this page is built from.ReferenceWord Lexicon Analyzer API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/lexiconnpm APIVerve.API.WordLexiconAnalyzerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/lexicon

Install the Node.js SDK, then call the Word Lexicon Analyzer API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/lexicon

Node.js

const res = await fetch("https://api.apiverve.com/v1/lexicon", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/lexiconThe published Node.js client, versioned and signed.GitHubapiverve/lexicon-apiSource, issues and the examples this page is built from.ReferenceWord Lexicon Analyzer API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.WordLexiconAnalyzerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/lexicon

No SDK to install — this is a plain HTTPS call to /v1/lexicon with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/lexicon",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/lexiconnpm APIVerve.API.WordLexiconAnalyzerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/lexicon

Install the C# / .NET SDK, then call the Word Lexicon Analyzer API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.WordLexiconAnalyzer

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/lexicon");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.WordLexiconAnalyzerThe published C# / .NET client, versioned and signed.GitHubapiverve/lexicon-apiSource, issues and the examples this page is built from.ReferenceWord Lexicon Analyzer API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/lexiconnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/lexicon

No SDK to install — this is a plain HTTPS call to /v1/lexicon with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/lexicon", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/lexiconnpm APIVerve.API.WordLexiconAnalyzerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/lexicon

No SDK to install — this is a plain HTTPS call to /v1/lexicon with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/lexicon");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/lexiconnpm APIVerve.API.WordLexiconAnalyzerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/lexicon

No SDK to install — this is a plain HTTPS call to /v1/lexicon with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/lexicon")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/lexiconnpm APIVerve.API.WordLexiconAnalyzerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Text Processing

View all 45 →

All articles →

Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read

Summarize Text with AI: A Practical GuideUse AI to summarize articles, documents, and user content. Tutorial with code for content platforms, research tools, and dashboards.Read

7 Content Moderation Mistakes That Sink AppsYour app allows user content. Here are the moderation mistakes that get apps pulled from stores.Read

Word Lexicon Analyzer API GET

Try it — live request, no key required

About the Word Lexicon Analyzer API

Ways to call it

Other ways to use Word Lexicon Analyzer

Questions.

Request parameters — GET /v1/lexicon

Required

Authentication

Response — GET /v1/lexicon

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/lexicon

Resources

Also published for

Call it from Node.js — GET /v1/lexicon

Resources

Also published for

Call it from Python — GET /v1/lexicon

Resources

Also published for

Call it from C# / .NET — GET /v1/lexicon

Resources

Also published for

Call it from Go — GET /v1/lexicon

Resources

Also published for

Call it from PHP — GET /v1/lexicon

Resources

Also published for

Call it from Ruby — GET /v1/lexicon

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Word Lexicon Analyzer API

Text Processing

Related articles

Ready to build with Word Lexicon Analyzer? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog