Business Name Numerology: What a Name Number API Returns

Business name numerology turns a company name into one number, then reads that number against the owner. Every letter is swapped for its value in the Chaldean table, the one Indian numerology works with. The values are added, and the total is cut down to one digit. Take Acme Inc. Acme adds up to 13 and Inc to 9, so the name totals 22. Then 2 + 2 gives 4, the number of Rahu.

Say John Doe owns the company. His birthday is Aug 15, 1990. That date gives him two numbers, both 6. One is his mulank, taken from the day. The other is his bhagyank, taken from the full date. Our API checks the 4 against each one. Both links come back friendly, so the API labels Acme Inc. a good fit for him.

That is what POST /v1/business returns. You send the name and the owner's birth date. You get the name's total, its single digit, its planet and the fit. You also get as many as 5 new spellings of the first word. Each keeps its sound and lands on a number that suits the owner. Add a launch date, and it reads that too. A Dec 12, 2026 opening totals 16, which reduces to 7. For John, that date is neutral.

The answer never says a name will make a business succeed. The sections below show the working, then the build decisions for a naming tool.

Business name numerology, step by step

On October 17, 2026, we sent Acme Inc. to POST /v1/business, with John Doe as the owner. This is the working behind the answer.

The Chaldean table runs from 1 to 8, so 9 is never a letter's value. The full table sits beside the Western one in Chaldean vs Pythagorean numerology. A business name is read in Chaldean only, just like a person's name number in our API. The glossary keeps a short definition of business name numerology.

The 22 comes back twice, as total and as compound. A compound number is the sum before it is cut to one digit. The answer also sets master to true, because 22 is one of the master numbers. The Indian count still ends on 4, and the fit is read from the 4.

The owner side needs only a date. For Aug 15, 1990, the day gives 1 + 5 = 6, the mulank. The eight digits of the full date total 33, and 3 + 3 = 6, the bhagyank. Both sums are worked out in how the mulank and bhagyank are found. Our free numerology calculator works them out from any date.

Then comes the fit. In Indian numerology, every digit is tied to a planet, and classical tables say which planets are friends. Rahu is not in those tables, so our API reads it as Saturn and names Rahu in a field called via. Venus, the planet of John's 6, counts Saturn as a friend. So both of John's links are friendly, with no enemy, and the outcome is good.

What POST /v1/business returns

The answer has three blocks: the name, the spellings and the launch date. This is the request, using the sample body from our docs.

Owner John Doe (born Aug 15, 1990), business Acme Inc., opening Dec 12, 2026. Besides the business name, the route needs only the owner's birth date.

curl -X POST "https://apiforastrology.com/api/numerology/v1/business" \
  -H "Authorization: Bearer $ASTROLOGY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Acme Inc.","birth_date":"1990-08-15","launch_date":"2026-12-12"}'

The answer for Acme Inc., trimmed to the main fields

{
  "name": {
    "kind": "business",
    "value": "Acme Inc.",
    "name": "Acme Inc.",
    "total": 22,
    "compound": 22,
    "number": 4,
    "master": true,
    "planet": "Rahu",
    "person": { "birth_date": "1990-08-15", "mulank": 6, "bhagyank": 6 },
    "fit": {
      "links": [
        { "from": "mulank", "relation": "friend", "via": ["Rahu"] },
        { "from": "bhagyank", "relation": "friend", "via": ["Rahu"] }
      ],
      "outcome": "good",
      "outcome_name": "Good fit"
    }
  },
  "suggestions": [
    {
      "name": "Aacme Inc.",
      "changes": [{ "code": "double_a", "from": "a", "to": "aa", "name": "Doubled an a" }],
      "total": 23,
      "number": 5,
      "planet": "Mercury",
      "fit": { "outcome": "good", "outcome_name": "Good fit" }
    }
  ],
  "found": 1,
  "launch": {
    "date": "2026-12-12",
    "number": 7,
    "planet": "Ketu",
    "fit": { "outcome": "neutral", "outcome_name": "Neutral" }
  }
}

The name block holds the count and the fit. The value field is the name exactly as you sent it. The name field is the form the API read, with extra spaces trimmed. Print name on screen, so the user sees what was counted.

The spellings change only the first word, and only in ways that keep its sound, such as doubling an a. For Acme Inc., one spelling came back: Aacme Inc., which totals 23 and reduces to 5 (Mercury). The found field says how many matched. Each spelling lists its changes, so your screen can show what moved. The answer adds a line to show beside them. In the API's words: "A new spelling changes the number of the name, not the person. Choose one only if you are happy to use it every day."

The launch block appears only when you send launch_date. Its digits add up the same way: 1 + 2 + 1 + 2 + 2 + 0 + 2 + 6 = 16, then 7, ruled by Ketu. Our API reads Ketu as Mars, and Venus counts Mars as neutral. So Dec 12 is a neutral fit for John. To pick a date rather than check one, POST /v1/dates reads each date in a chosen month against the owner. The launch date entry shows how.

Does Inc. or LLC count?

Our API counts every letter you send. It has no list of suffixes to drop. So the exact name you send is your app's choice, and it can change the answer. We sent eight forms of Acme, all with John as the owner.

Inc. and LLC each add exactly 9 in the Chaldean table. Adding 9 to a total never changes the digit it reduces to, so 13 and 22 both give 4. Keeping or dropping Inc. or LLC leaves the number where it was. The total, the compound and the master flag can still move. Co., Corp. and the longer words do change the number. The Acme Company lands on 2, which is not a good fit for John.

Some changes made no difference. Capital and small letters count the same, and extra spaces are trimmed. Dots and hyphens have no value, so A.C.M.E. Inc. and Acme-Inc. both total 22. An apostrophe is skipped too, but the letter after it counts. Acme's Inc. gains an s worth 3 and lands on 7, a neutral fit.

One catch with hyphens: the API treats Acme-Inc. as one word. So its spellings can change the suffix too, and it offered Acme-Eenc. Keep a space before the suffix.

Among the guides we checked, one from AstroSight says to leave out Inc and other suffixes. The others did not say either way. Dropping a suffix is one more input choice that splits calculators, like the seven choices covered in why numerology calculators disagree. Since the API leaves it to you, say on screen which form was read.

Names the API refuses

A company name can hold a comma, an & sign or a digit. Our API reads English letters only. Between them it allows spaces, dots, hyphens and apostrophes. Anything else is refused with status 422. The error carries invalid_input as its code and name as its field. We tried seven names that fail.

An empty name fails the same way. A request with no birth date gets a 422 on birth_date, and a date like 2026-13-40 gets one on launch_date.

Our API leaves the fix to you, because any letter it guessed would change the count. So clean the name in your form, before the call.

Drop the marks that carry no value. A comma has no letter value, so removing it changes nothing. Acme Inc. still totals 22.

Ask before you spell out a sign or a digit. Each choice makes a new name with its own count. Acme and Co. totals 33, while Acme Co. totals 23.

Mark the right field. The error names the input that failed: name, birth_date or launch_date. Put the message beside that field.

The owner's birth date decides the fit

The same name can suit one owner and not another. We sent Acme Inc. again with Jane Doe as the owner (Mar 22, 1992). Jane's mulank is 4. Her date digits add up to 28, so her bhagyank is 1.

Her mulank, 4, is the same number as the name, and the rule counts a match on the friendly side. Her bhagyank is ruled by the Sun, and the Sun treats Saturn, the stand-in for Rahu, as an enemy. One friendly link plus one enemy link gives mixed.

The rule has four outcomes and no weights: good, neutral, mixed and difficult. The API labels difficult as "Not a good fit".

The route takes one owner per call. It reads only the birth date, never the owner's name. For a company with two founders, call once per founder and show both results side by side. Do not merge them into one label, because the API has no rule for that.

Comparing candidate names without ranking them

A user with a shortlist needs every name on it checked. Our compare route, POST /v1/numbers, does not take business names, and kind: "business" gets a 422. So each candidate is its own call. We sent five for John, in this order.

Two names are good fits and two are not, and nothing breaks either tie. The answer has no score, no rank and no list of good numbers for a type of business. So a "best name" badge would be your app's idea, not the API's. Keep the order the user typed, and print the API's label beside each name.

When more than one spelling comes back, they always come in the same order: the fewest changes first, then alphabetical. That order is not a ranking either.

Each call to POST /v1/business uses 2 reading credits, so five candidates use 10. For a quick shortlist, send each name to POST /v1/number and set kind to business. It returns the same name block for 1 credit, with no spellings and no launch date. Then call POST /v1/business for the name the user opens.

Plan the whole naming flow. The business naming tools page sets out the calls in order, from the name check to the launch date.

Build decisions for a naming tool

Ask which name to check. A brand name and a legal name can differ, such as Acme and Acme Co. Here they give 4 and 5. Let the user pick or check both, and label the form that was read.

Give each candidate its own screen. Show the name as read, the total and its digit, the planet, the fit label and the two links behind it. Add the spellings with their changes, and the launch date when there is one.

Show the working. The business answer gives the total, not each word's sum. If you want Acme 13 and Inc 9 on screen, our name checker route, POST /v1/name, returns each word in words.

Plan for empty fields. The compound field can be null. Acme Corporation totals 60, and our API folds a total above 52 by adding its digits. The 60 becomes 6, which is below the compound range. The found count can be 0 too. For Acme Studio and Acme Goods, no spelling reached a number that suits John. The answer has no sentence for that, so write one, such as "No spelling change suits this owner."

Keep the claim line. Each answer carries a not_claimed line. Its point: a number hints at a leaning and does not fix an event. Show it on each candidate screen, and never write that a name will bring sales or success.

Serve Hindi from the same call. Send lang=hi, and the labels come back in Hindi. Acme Inc.'s fit reads अच्छा मेल, and Rahu reads राहु. Codes such as good and Rahu are not translated, so your app's checks keep working.

Read the full field list. Our number checks page covers what the business route returns, beside the phone, vehicle and house checks.

The short version

A business name number is a Chaldean letter count, cut to one digit and read against one owner's birth date. Acme Inc. gives 22, then 4: good for John Doe, mixed for Jane Doe. The API counts exactly what you send, so your form decides which name goes in. Give each candidate its own call and its own screen, and keep the user's order. Next to each one, show the line that numbers point to leanings, not fixed events.