How to choose a numerology API

The 12 checks

1. 1. Chaldean and Pythagorean

   Ask: Does it return both letter systems, and does it say which one it reads? Chaldean is the one Indian numerology uses. Pythagorean is the Western one.

   Look for: Both numbers side by side, each labelled, with a clear flag on the one that is read. A lone number with no system named confuses users who know the other one.

2. 2. Names in other scripts

   Ask: What happens when a user types a name in Hindi letters or another script?

   Look for: A clear error that asks for English letters. An API that changes the script for you picks a spelling for your user. Each spelling gives a different number.

3. 3. Mulank and bhagyank

   Ask: Does it return the mulank (birth day number) and the bhagyank (destiny number)? Many apps call them the driver and conductor numbers.

   Look for: The full sum next to the final digit, so you can check the working. A birth on the 15th should give a mulank of 1 + 5 = 6.

4. 4. The Lo Shu grid and its lines

   Ask: Does it fill the Lo Shu grid from the birth date? The grid is a 3 by 3 square of the numbers 1 to 9. Does it read the lines?

   Look for: The count in each cell, the missing and repeated numbers, and the full or empty lines. Books differ on which digits go in, so the API should say.

5. 5. Master numbers

   Ask: Are 11, 22 and 33 kept, flagged or reduced to one digit?

   Look for: The rule, stated in the answer. One way ends every number on one digit, and another keeps 11, 22 or 33. Either is fine when the API says which.

6. 6. Compatibility

   Ask: Can it compare two people by their birth dates? Does it read the pair both ways?

   Look for: A plain outcome, such as good or mixed, and the reason for it. One person's number can be friendly to the other's, but not the other way around.

7. 7. Mobile, vehicle and house numbers

   Ask: Can it check a phone, car or house number against its owner's numbers?

   Look for: A stated rule for letters. Books disagree on whether the letters on a plate count, so the answer should list what it skipped.

8. 8. Baby names

   Ask: Can it suggest names whose number suits a child, counted with the surname?

   Look for: Each name with its meaning, its number and its fit. A list that picks one name as best takes the choice away from the parents.

9. 9. Languages

   Ask: Are the readings in your users' languages, such as Hindi?

   Look for: Reading text in each language, with codes and keys that stay in English so your code does not change. Have a native speaker read one answer.

10. 10. Credits and pricing

    Ask: What does one call cost? Does a full report cost more than one number? Do failed calls cost anything?

    Look for: A price for each route that you can multiply by your traffic. Price one real month before you build.

11. 11. Test keys and sample people

    Ask: Can your team build without a card? Which people can you test with?

    Look for: Free test keys and named sample people whose answers are in the docs. Then you can compare your result with the published one.

12. 12. Sources for the letter tables

    Ask: Where do the letter values and the grid come from?

    Look for: A named book or source for each table, so a numerologist on your team can check it. No source named means no way to check.

How do you test a numerology API in one afternoon?

Send the same two sample people to each API, and write down every number. Then try a second spelling, a name in Hindi letters, a phone number and a pair. Ask for one answer twice, and once in Hindi. Last, price one real month. The steps below show the real answers from the Numerology API.

1. Pick two sample people and send them to every API. The docs here use John Doe, born Aug 15, 1990, and Jane Doe, born Mar 22, 1992. Free test keys answer for both.
2. Send John to the profile route, POST /v1/profile. The Numerology API gives a mulank of 6. The bhagyank is 6, from a total of 33, flagged as a master number. His name is 7 in Chaldean (a sum of 34) and 8 in Pythagorean (35). Only the Chaldean number is read.
3. Send two spellings to the name route, John Doe and Jon Doe. Jon Doe adds up to 29, then 11, then 2, a master number on the way. John Doe's fit is "Neutral", and Jon Doe's is "Not a good fit". One letter changed the answer.
4. Send the same name in Hindi letters: जॉन डो. A careful API refuses it and says why, instead of guessing a spelling. The Numerology API answers with a 422 error that asks for English letters (A to Z).
5. Check one phone number and one pair. 212 555 0147 adds up to 32, then 5: a "Good fit" for John. John and Jane come back "Mixed", with each link between their numbers read both ways. Their mulanks, 6 and 4, are friendly both ways.
6. Ask for John's profile twice, then once with lang=hi. The two English answers should match word for word. In Hindi, codes such as planet should stay in English, with the Hindi name in planet_name.
7. Price one real month. A profile uses 3 credits, so the Free plan's 150 credits a month cover 50 profiles.

The answers above are real, recorded from the Numerology API and checked on Oct 28, 2026.

How API for Astrology answers each check

What the Numerology API does not do

• Changing a name into English letters. A name in Hindi or another script is refused, because each spelling gives a different number.
• Readings for compound numbers. Sums from 10 to 52 come back in compound, but they are not read.
• A best pick. Names, spellings and numbers each get a fit, in a fixed order, and the answer says ranked: false.
• Predictions of fixed events. Every answer carries the same line: "Numbers describe tendencies, not fixed events. Use them as a guide, not a rule."
• Counting the letters on a plate or a door. Only digits count.
• Image files. The JSON answers give the Lo Shu grid as data for you to draw. The full report is one printable HTML page with its drawings built in.

Questions buyers ask