Kabbalah API
A gematria number you can show the spelling for.
GematriaKabbalah Numerology72 Names of GodTree of LifeHebrew Birthday …and so much more
Start building in seconds.
Want to try without writing code? Try this domain live in API playground →
npm install @roxyapi/sdkimport { createRoxy } from '@roxyapi/sdk'
const roxy = createRoxy(process.env.ROXY_API_KEY!)
const { data } = await roxy.kabbalah.get(/* ... */)pip install roxy-sdkfrom roxy_sdk import create_roxy
roxy = create_roxy("your-api-key")
result = roxy.kabbalah.get(...) # async: await roxy.kabbalah.get_async(...)composer require roxyapi/sdkuse function RoxyAPI\Sdk\createRoxy;
$roxy = createRoxy(getenv('ROXY_API_KEY'));
$result = $roxy->kabbalah->get(/* ... */);dotnet add package RoxyApi.Sdkusing RoxyApi;
var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);
// await roxy.Kabbalah.<resource>.GetAsync() or .PostAsync(new() { ... })go get github.com/RoxyAPI/sdk-goimport roxyapi "github.com/RoxyAPI/sdk-go"
roxy, _ := roxyapi.NewRoxy(os.Getenv("ROXY_API_KEY"))
// resp, err := roxy.Kabbalah.<Method>(context.Background(), nil)curl -H "X-API-Key: YOUR_KEY" \
https://roxyapi.com/api/v2/kabbalah/claude mcp add --transport http \
roxy-kabbalah https://roxyapi.com/mcp/kabbalah \
--header "X-API-Key: YOUR_KEY"AI agents auto-discover all endpoints as callable tools. Zero configuration. Responses can come back token-optimized and lossless, cutting the tokens your agent spends per call by roughly 40 to 52 percent.
Want to ship faster? Clone a free template and go from zero to production in 30 minutes.
Building with Cursor, Claude Code, or Bolt? Use our AI prompts to generate a complete app in minutes.
Building on WordPress? Install the RoxyAPI plugin and drop a shortcode, no code required.
{
"input": {
"text": "Ruth"
},
"hebrewForms": [
{
"hebrew": "רות",
"romanization": "RVTh",
"rule": "Longest match first: every two letter group the table prints is read as one Hebrew letter before the single letters are tried.",
"values": [
{
"id": "mispar-hechrachi",
"value": 606,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-gadol",
"value": 606,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "otiyot-be-milui",
"value": 928,
"alternateValues": [
929,
938
],
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-katan",
"value": 12,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-kidmi",
"value": 2311,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-prati",
"value": 200036,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-ha-merubah-ha-klali",
"value": 367236,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-meshulash",
"value": 72000216,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-mispari",
"value": null,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-musafi",
"value": 609,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "kolel",
"value": 607,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
}
],
"letters": [
{
"glyph": "ר",
"letterId": "resh",
"name": "Resh",
"isFinal": false,
"value": 200
},
{
"glyph": "ו",
"letterId": "vav",
"name": "Vau",
"isFinal": false,
"value": 6
},
{
"glyph": "ת",
"letterId": "tav",
"name": "Tau",
"isFinal": false,
"value": 400
}
]
},
{
"hebrew": "רוטה",
"romanization": "RVTH",
"rule": "An alternative parse: at least one two letter group is read as two separate Hebrew letters instead of one.",
"values": [
{
"id": "mispar-hechrachi",
"value": 220,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-gadol",
"value": 220,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "otiyot-be-milui",
"value": 947,
"alternateValues": [
948,
951,
952,
956,
957,
961,
966
],
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-katan",
"value": 22,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-kidmi",
"value": 876,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-prati",
"value": 40142,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-ha-merubah-ha-klali",
"value": 48400,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-meshulash",
"value": 8001070,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-mispari",
"value": null,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-musafi",
"value": 224,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "kolel",
"value": 221,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
}
],
"letters": [
{
"glyph": "ר",
"letterId": "resh",
"name": "Resh",
"isFinal": false,
"value": 200
},
{
"glyph": "ו",
"letterId": "vav",
"name": "Vau",
"isFinal": false,
"value": 6
},
{
"glyph": "ט",
"letterId": "tet",
"name": "Teth",
"isFinal": false,
"value": 9
},
{
"glyph": "ה",
"letterId": "he",
"name": "He",
"isFinal": false,
"value": 5
}
]
}
],
"chosen": {
"hebrew": "רות",
"rule": "Longest match first: every two letter group the table prints is read as one Hebrew letter before the single letters are tried."
},
"values": [
{
"id": "mispar-hechrachi",
"value": 606,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-gadol",
"value": 606,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "otiyot-be-milui",
"value": 928,
"alternateValues": [
929,
938
],
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-katan",
"value": 12,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-kidmi",
"value": 2311,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-prati",
"value": 200036,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-ha-merubah-ha-klali",
"value": 367236,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-meshulash",
"value": 72000216,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-mispari",
"value": null,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "mispar-musafi",
"value": 609,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "kolel",
"value": 607,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
}
],
"transformations": [
{
"id": "atbash",
"output": "גפא",
"outputRomanization": "GPA",
"value": 84,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
},
{
"id": "albam",
"output": "טפך",
"outputRomanization": "TPK",
"value": 109,
"tradition": "rabbinic",
"source": "https://en.wikipedia.org/wiki/Gematria"
}
],
"matches": [],
"conventions": {
"transliteration": "letter-map-mathers",
"misparGadol": "finals-500-900",
"atbashOutput": "both"
}
}Structured JSON with documented fields. Not hallucinated text. See all endpoints
Works with your stack
Kabbalah API for gematria, the 72 names, the Tree of Life and the Hebrew birthday, from one key. Score a Hebrew word or a Latin name across ten rabbinic ciphers with the per letter breakdown, every candidate Hebrew spelling shown and the rule that chose one, plus a cited equal value lexicon. The 72 names are derived from the verses rather than copied from a table, the birth name is dated by the exact position of the Sun or by the civil wheel as you choose, and the sephirot, the 22 paths and the 22 letters come back under typed school variants cross linked to the tarot deck. One key covers every RoxyAPI domain, with Remote MCP and typed SDKs.
Every Kabbalah calculation is covered by 11,693 automated tests per deploy, 2,801 of them gold-standard tests locked to named external references such as NASA JPL Horizons, with a public MIT benchmark repo anyone can clone and re-run. See how we test.
Multi-language API responses
Key Features
Everything you need from our Kabbalah API, built for production:
Typed transliteration that shows its work: a Latin name has no single Hebrew spelling, so every candidate spelling comes back with its own values and the rule that produced it, and the chosen one is named. A letter the published map does not cover is rejected by name rather than silently dropped
Eleven rabbinic ciphers plus two substitution transformations, and three Latin alphabet ciphers labelled by lineage from Agrippa 1533 to Mathers 1887, so a Renaissance Christian cipher is never presented as Jewish practice
A curated equal value lexicon where every entry carries at least two independent citations, and a per letter breakdown on every number so a reader can see why it is what it is
The 72 names derived from three verses of Exodus read in the boustrophedon order rather than read off a table, with any row where a named published list differs flagged on that row
The birth name dated two ways and the response says which: by the exact five degree arc the Sun stood in, or by the fixed civil wheel with the year start and the leap day policy as request parameters
The Hebrew date and the Hebrew birthday computed from the published calendar algorithm, with the sunset boundary typed as a request field because it depends on where you were
The ten sephirot, the 22 paths and the 22 letters under four attribution readings, each path cross linked to the tarot trump on it in the Tarot API on the same key
A daily that is actually dated: the Omer count, its sephirot pairing and the printed Hebrew label, with the next opening date returned outside the window instead of an invented reading
All 12 Endpoints
Every one is live in the public OpenAPI spec and callable as an MCP tool. Click any endpoint to view detailed documentation, parameters, and response examples.
What You Can Build with Kabbalah API
Real-world applications and use cases for integrating Kabbalah API into your projects:
Multi domain spiritual apps: a Kabbalah tab beside numerology and tarot, sharing one key and one billing account
Name meaning and numerology products: the gematria of a name with every spelling shown and the equal value words cited
Tarot apps: the 22 paths with the letter and the trump on each, from the same deck the Tarot API serves
Jewish culture and education apps: the Hebrew birthday, the Omer day and the Sefer Yetzirah letter table, computed rather than looked up
AI agents over Remote MCP: a tool that asks for the Hebrew or the transliteration convention and returns the spellings it scored
Reference and editorial platforms: sephirot, letter and cipher lookups with the tradition and the century stated on every row
What developers are saying
Dhani M.
Indie App Developer
Shipped an astrology app over a long weekend. Birth charts, nakshatras, KP cusps, significators. I verified the Lahiri ayanamsha values independently and they line up with my reference. One API key for all of it.
Tom H.
Senior Developer
The OpenAPI spec is the most complete I have seen in this space. Generated a type-safe TypeScript client from it in seconds. Every field has descriptions and examples. Production-grade documentation.
Chris W.
Backend Engineer
Response times consistently under 50ms for numerology and tarot endpoints. The API returns structured JSON with every field documented. Integrated it into our platform in an afternoon.
Do not take our word for it. Ask the agents.
The receipts are public: the testing methodology, the open MIT benchmark, the transparency report, and the live API playground. Let ChatGPT, Perplexity, or Claude search the web and tell you what they find about RoxyAPI accuracy, MCP, SDKs, and pricing.
Opens a live web search in a new tab.
Getting started with Kabbalah API.
From zero to production in 3 steps. No signup required for testing.
3 Steps to Ship
| 1Install the SDK | npm i @roxyapi/sdk |
| 2Get your API key | View Plans |
| 3Make your first call | View Docs |
Agent-Ready Infrastructure
MCPRemote MCP, llms.txt, and AGENTS.md. The full agent-readiness stack for 18+ domains under one key.
- Remote MCP server — every endpoint auto-discovered as a tool by Claude, ChatGPT, Cursor over Streamable HTTP. No Docker.
- Token-optimized responses — opt-in compact mode returns the same data with each field name sent once, cutting the tokens your agent reads per call by roughly 40 to 52 percent. Lossless, and one call still counts as one request.
- llms.txt — AI-native discovery surface for ChatGPT, Perplexity, and Gemini citation
- AGENTS.md — 2026 execution playbook for Cursor, Codex, Windsurf, Aider, Claude Code, Gemini CLI. Bundled in the SDK.
From your AI agent to a verified Kabbalah answer.
Your agent grounds every answer in verified calculations and replies in your own voice, so it never hallucinates a chart, date, or reading. No local setup, no AGPL, no hosted-AI markup.
Audit it yourself: every Kabbalah endpoint runs live in the API playground
Kabbalah API FAQ
How do I get the gematria of a name via API?
Post the name and the API returns every Hebrew spelling the transliteration map produces, each with its values under the rabbinic ciphers and a per letter breakdown, plus the spelling it chose and the rule that chose it. Send the Hebrew yourself instead and it scores exactly that spelling. Vowel points and cantillation marks are removed before scoring, so a pointed and an unpointed spelling of one word give the same number.
Why do two gematria calculators disagree on my name?
Almost always because they wrote it in Hebrew differently and said nothing about it. There is no standard for turning a Latin name into Hebrew: the published Hebrew standards all go the other way. This API takes the transliteration scheme as a typed parameter, returns every candidate spelling rather than one, and echoes the convention on the response, so two answers can be compared instead of argued about.
What is my birth angel and how is it worked out?
The Renaissance tradition gives a birth three names rather than one: two read from the day of birth by two different cycles, and one from the twenty minute interval of the hour. The name of the day can be dated by the exact arc the Sun stood in or by a fixed civil calendar of five day periods, and the two drift apart by up to about three days by early August. Both are offered, the request chooses, and the response says which one produced the answer.
Which arrangement of the Tree of Life does the API use?
The 1652 arrangement, in which Malkuth carries three paths, which is the one the Hermetic orders used and the only one with a published table that letters every path. A one path Malkuth arrangement is in circulation, but the diagram it is traced to had seventeen paths and no letters at all, so there is no sourced table to serve. The parameter is typed and echoed so this cannot change under a caller without notice.
Is this Jewish Kabbalah or Hermetic Qabalah?
Both, and every row says which. The letter values, the ciphers, the substitution methods and the Omer count are rabbinic. The tarot trumps on the paths, the sephirot spheres and the transliteration map are Renaissance and Victorian Hermetic. Each cipher and each table carries a provenance class and the century of its tradition, so a product can present one, the other, or both without misattributing either.
Does this compute the Hebrew calendar?
It computes a Hebrew birthday, not a calendar. The Hebrew date of a birth, the anniversary that follows it and the sunset boundary are fields inside the birth profile, worked out from the published calendar algorithm with no runtime dependency on anything. There are no holidays, no candle times and no Torah readings here, because a free and well maintained converter already covers that ground.
Start using Kabbalah API today.
A gematria number you can show the spelling for.
All 18 domains included with every plan. Every endpoint, MCP server, SDK, and starters.
Plans from $39/mo, starting at $1.80 per domain on annual billing. No credit card required for testing.
View Pricing & Get API Key