Best Numerology API for Developers: 2026 Buyer Guide

Searching for a numerology API returns marketing pages, not answers. The questions that actually decide a purchase are technical: does the engine preserve master numbers or silently reduce 11 to 2, does it detect karmic debt during reduction, does it support the Chaldean system alongside Pythagorean, and what happens when a user types Jose with an accent or a Cyrillic surname. This guide compares the numerology API options a developer can evaluate in 2026 against those axes, plus the delivery layer that determines shipping speed: typed SDKs, hosted Remote MCP for AI agents, and pricing you can forecast. Every RoxyAPI response shown below is unedited production output, and every competitor fact was verified on the provider site in July 2026.

How do the best numerology APIs compare in 2026?

Three providers publish enough public documentation to compare directly: RoxyAPI, Prokerala, and AstrologyAPI. RoxyAPI is the only one of the three that documents master number preservation, karmic debt detection on every core calculation, Unicode transliteration, a one-call full chart, numerology compatibility scoring, and typed SDKs. The table below summarizes what each provider documents publicly, reviewed live in July 2026.

Cells marked not documented or not listed reflect the provider public docs and pricing pages reviewed live in July 2026; the feature did not appear on those pages.

Ready to build on verified numbers? The Numerology API returns complete, interpreted results in one call. See pricing.

Does the API preserve master numbers and detect karmic debt?

Master number preservation is the fastest way to separate a correct numerology engine from a naive one. The numbers 11, 22, and 33 must never be reduced further, including when they appear as month, day, or year components. RoxyAPI flags them with an explicit type field and prints the full reduction chain, so a developer can audit every step instead of trusting a bare integer.

{
  "number": 33,
  "calculation": "Month: 3, Day: 8, Year: 1984 → 1+9+8+4 = 22 → 3+8+22=33",
  "type": "master",
  "hasKarmicDebt": false,
  "meaning": { "title": "The Master Teacher" }
}

Karmic debt works the same way: the engine watches the reduction chain, not just the final digit. The birth date 1990-07-15 reduces through 14 before landing on 5, and the response says so:

{
  "number": 5,
  "calculation": "Month: 7, Day: 15 → 1+5 = 6, Year: 1990 → 1+9+9+0 = 19 → 1+9 = 10 → 1+0 = 1 → 7+6+1=14 → 5",
  "type": "single",
  "hasKarmicDebt": true,
  "karmicDebtNumber": 14,
  "karmicDebtMeaning": { "description": "Accumulated Obligation of Moderation and Stability" }
}

The same request with ?lang=es returns the interpretation in Spanish, title included: El Maestro Instructor for the 33 chart. Eight languages ship on the same endpoints with the same quota.

Can the API calculate accented and non Latin names correctly?

A numerology API that strips unmapped characters silently corrupts name numbers for a large share of real users. The correct behavior is documented transliteration: an accented letter maps to its base letter and keeps its value, and the calculation string proves it. RoxyAPI transliterates before mapping, so Jose with an accent scores the E as 5 instead of dropping it.

Here is the unedited production response for the Expression number of José García:

{
  "number": 7,
  "calculation": "J=1, O=6, S=1, E=5, G=7, A=1, R=9, C=3, I=9, A=1 → 1+6+1+5+7+1+9+3+9+1 = 43 → 7",
  "type": "single",
  "hasKarmicDebt": false
}

Engines that skip this step return a different number for the same person depending on how the name was typed. We dissected that failure mode, plus master number stop rules and reduction order, in why two numerology APIs return different Life Path numbers. When you evaluate any vendor, send an accented name and check whether the breakdown accounts for every letter.

What do Prokerala and AstrologyAPI ship for numerology?

Prokerala sells numerology as per-number modules on a credit wallet. Its public credit catalog, reviewed in July 2026, lists 31 Pythagorean modules and 5 Chaldean modules at 100 or 200 credits per API request: Life Path costs 100 credits, while Karmic Debt, Karmic Lessons, Pinnacles, and Challenges cost 200 credits each. Credits reset every billing cycle, unused credits do not carry forward, and additional credits are sold in blocks of 100,000 with 3 months validity.

AstrologyAPI documents numerology as a ten endpoint section inside its Western astrology API docs: numerological_numbers, lifepath_number, personality_number, expression_number, soul_urge_number, challenge_numbers, sub_conscious_self_number, and personal day, month, and year predictions. Chaldean endpoints, karmic debt detection, and numerology compatibility do not appear in that section as of July 2026.

RoxyAPI ships 20 numerology endpoints, part of 164 plus endpoints across 12 insight domains including Western astrology, Vedic astrology, tarot, human design, and forecast, all under one API key. The POST /numerology/dual endpoint returns both systems side by side: the name David comes back as a Pythagorean master 22 and a Chaldean compound 16 rooting to 7 in a single response.

How does numerology API pricing compare for developers?

Flat request pricing beats credit wallets on forecastability. On RoxyAPI, one request equals one quota unit whether it hits REST or the Remote MCP server, and the Starter plan at $39 per month includes 25,000 requests across all 12 domains, about $3.25 per domain. A full numerology profile is one request to POST /numerology/chart, which returns all six core numbers plus karmic lessons, karmic debt, personal year, pinnacles, challenges, hidden passion, subconscious self, and name letter analysis.

Assembling the equivalent profile from per-number modules on the Prokerala catalog consumes 1,800 credits: six core numbers at 100 credits each, karmic debt, karmic lessons, pinnacles, and challenges at 200 each, plus personal year, personal month, hidden passion, and subconscious self at 100 each. A 100,000 credit block covers 55 such profiles before it expires. On RoxyAPI the same 25,000-request Starter month covers 25,000 full profiles, and heavier tiers scale to 200,000 requests for $149. No per-domain fees, no credit weighting, no arithmetic before every feature launch.

When should you choose each numerology API?

Choose based on what you are building, not on brand familiarity. The honest split after reviewing all three public catalogs:

• Choose Prokerala if your product already runs on the Prokerala astrology stack and you want per-number numerology modules, including Chaldean variants, billed to the same credit wallet you already manage.
• Choose AstrologyAPI if you already integrate their Western or Indian astrology report endpoints and only need core Pythagorean numbers plus personal day, month, and year predictions inside the same account.
• Choose RoxyAPI if you want typed SDKs in six ecosystems, complete charts in one call, documented master number and karmic debt handling, transliteration for global names, both Pythagorean and Chaldean systems, and a hosted Remote MCP server your deployed AI assistants in ChatGPT, Claude, or n8n can call for verified numbers instead of hallucinating them.

The numerology engine behind every RoxyAPI response is covered by gold standard tests documented on the methodology page, so the math you audit in the calculation string is the math that ships.

How do you call the numerology API from code?

Numerology needs no geocoding step: birth date and name are enough, which makes it the fastest RoxyAPI domain to integrate. The three most popular endpoints are Life Path, the full chart, and compatibility. Each request needs your API key and a JSON content type header.

curl -s -X POST "https://roxyapi.com/api/v2/numerology/life-path" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"year": 1984, "month": 3, "day": 8}'

curl -s -X POST "https://roxyapi.com/api/v2/numerology/chart" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"fullName": "John William Smith", "year": 1990, "month": 7, "day": 15}'

curl -s -X POST "https://roxyapi.com/api/v2/numerology/compatibility" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person1": {"lifePath": 5, "expression": 7, "soulUrge": 6}, "person2": {"fullName": "Maria Elena Torres", "year": 1992, "month": 4, "day": 21}}'

The compatibility endpoint accepts pre-calculated numbers, raw name and birth date, or a mix across the two people, and returns an overallScore from 0 to 100 with per-aspect breakdowns. Every request and response schema is browsable in the POST /numerology/life-path reference, a live playground that returns real production responses before you pay.

FAQ

What is the best numerology API for developers?

For developers who need auditable math and fast integration, RoxyAPI is the strongest fit: 20 numerology endpoints with step-by-step calculation strings, master number and karmic debt flags on every core calculation, Pythagorean and Chaldean systems, a full chart in one call, and typed SDKs for TypeScript, Python, PHP, C#, Go, and WordPress under one flat subscription.

Do numerology APIs preserve master numbers 11, 22, and 33?

Not all of them document it, which is why you should test before buying. RoxyAPI preserves master numbers at every stage of reduction, marks them with a type: master field, and prints the full chain, so the birth date 1984-03-08 returns 33 with the preserved 22 year component visible in the response.

Can a numerology API handle accented or non Latin names?

RoxyAPI transliterates names before mapping letters to numbers, so José scores the accented E as 5 instead of dropping it, and the calculation string shows every letter and value. Send an accented test name to any vendor you evaluate and confirm the breakdown accounts for all letters.

Does RoxyAPI support Chaldean numerology?

Yes. POST /numerology/chaldean returns a full Chaldean reading with compound numbers and planetary rulers, GET /numerology/compound-number/{number} looks up compound meanings, and POST /numerology/dual returns Pythagorean and Chaldean results for the same name in one call, with an agreement flag between the two systems.

How much does a numerology API cost?

RoxyAPI starts at $39 per month for 25,000 requests, and one request equals one quota unit with no credit weighting. That subscription includes all 12 domains, every numerology endpoint, the Remote MCP servers, SDKs, and 8 language localization, so a complete numerology profile costs exactly one request.

Conclusion

The best numerology API for developers is the one whose math you can audit: master numbers preserved, karmic debt surfaced, every letter of every name accounted for, and one call returning the whole chart. Compare the responses above with any alternative, then start with the Numerology API and ship this week.