A JSON REST API that returns 47 Pythagorean numerology fields from a name and a date of birth — life path, destiny, karmic debts, pinnacles, planes of expression. One fixed, documented set of conventions that will not drift under you.
Try any name
Accented and Russian names work too.
Live calls to POST /v1/demo — the real endpoint, behind Cloudflare Turnstile. Nothing is stored.
Works with
Integrate
One POST, one header, about five lines in any language. The response on the right is the actual JSON the API just returned for the chart above. Step-by-step guides: Python, JavaScript & Node.js, or generate a client from OpenAPI.
curl -X POST https://simplenumerologyapi.com/v1/charts/pythagorean \
-H 'X-API-Key: nk_…' \
-H 'content-type: application/json' \
-d '{"first_name":"María","middle_name":"Stefania",
"last_name":"García López","birthdate":"1990-03-12"}'
Why this one
Whether Y is a vowel, whether master numbers survive reduction, whether you reduce each name or the whole name at once — different answers give different charts, and most APIs never tell you which they picked.
Vowels are A/E/I/O/U with Y always a consonant. Name numbers sum the whole name at once. Master numbers survive reduction. These are part of the contract, not implementation details — changing one would silently alter every chart you ever computed.
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
|---|---|---|---|---|---|---|---|---|
| A | B | C | D | E | F | G | H | I |
| J | K | L | M | N | O | P | Q | R |
| S | T | U | V | W | X | Y | Z |
No database of names, no logs of birthdates. Charts are pure computation from the request and discarded with it. Names travel in the body, never the URL — so they never reach an access log, a proxy log, or browser history.
Forever. No model, no randomness, no drift between versions.
Quota headers on every response. A 402 when you run out, not a silent truncation. Cancelling a paid plan drops you to the free quota rather than revoking your key — an expired card never hard-breaks your integration.
Pricing
Up to 20 keys, one per environment. Quota resets monthly, with an email at 80%. Upgrade, downgrade or cancel yourself — no retention call.
Enough to build against and decide.
For a production app with real traffic.
For high volume and batch work.
More than 100,000 charts a month?
Switch on overage and paid plans keep serving past the quota, billed per 1,000. Or tell us about your volume.
Sign up with GitHub, Google, or your email and a password. Paid plans continue straight to checkout.
Questions
Yes. The free plan includes 100 requests a month on every endpoint — Pythagorean charts, cycles and compatibility — plus the OpenAPI spec. No credit card, and it does not expire.
You can — it is arithmetic. The work is not the arithmetic, it is deciding the conventions and never changing them: whether Y counts as a vowel, whether a master number survives reduction, whether a compound surname contributes one initial or two. Get one wrong and every chart shifts. This endpoint has made those choices, documented them, and treats them as frozen.
Nothing. There is no database of names and no logging of request bodies. A chart is computed from the request and discarded with it. Names travel in the body rather than the URL, so they never land in an access log or browser history. Your own account data — email, keys, billing references — can be exported or deleted from the account page whenever you like. See the privacy policy.
Yes, and this is the most common integration bug. Reduction deliberately stops at the master numbers 11, 22 and 33, so a field typed integer can return two digits. Two more shapes to expect: hidden_passion_number is an array, because ties are canonical rather than an error; and full_name_number_counts lists every digit from 1 to 9 with its count, zeros included.
We email you at 80% and again at 100%. At the limit you get a 402 with quota headers — unless you have switched on overage on a paid plan, in which case requests keep flowing and the extra is billed per 1,000. Cancelling drops you to the free quota rather than revoking your keys, so an expired card never hard-breaks your integration.
No. It is one POST with a JSON body and a header — the tabs above are the whole integration in four languages, and there are step-by-step guides for Python and JavaScript. If you want a typed client, generate one from the OpenAPI document.
No onboarding call to book, no minimum.
Sign up with GitHub, Google or an email address. The free plan needs no card.
Post a name and a birthdate with your key in the X-API-Key header.
Life path to planes of expression, as JSON. The same input always gives the same chart, so you can cache it.