Mesoamerican Astrology API
A Mayan day sign that tells you which correlation it came from.
Mayan AstrologyTzolkinLong Count CalendarAztec CalendarNahual Compatibility …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.mesoamericanAstrology.get(/* ... */)pip install roxy-sdkfrom roxy_sdk import create_roxy
roxy = create_roxy("your-api-key")
result = roxy.mesoamerican_astrology.get(...) # async: await roxy.mesoamerican_astrology.get_async(...)composer require roxyapi/sdkuse function RoxyAPI\Sdk\createRoxy;
$roxy = createRoxy(getenv('ROXY_API_KEY'));
$result = $roxy->mesoamericanAstrology->get(/* ... */);dotnet add package RoxyApi.Sdkusing RoxyApi;
var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);
// await roxy.MesoamericanAstrology.<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.MesoamericanAstrology.<Method>(context.Background(), nil)curl -H "X-API-Key: YOUR_KEY" \
https://roxyapi.com/api/v2/mesoamerican-astrology/claude mcp add --transport http \
roxy-mesoamerican-astrology https://roxyapi.com/mcp/mesoamerican-astrology \
--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.
{
"date": "2012-12-21",
"tzolkin": {
"daySign": "ajaw",
"daySignName": "Ajaw",
"daySignClassic": "Ahau",
"daySignKiche": "AJPUʼ",
"number": 4,
"trecena": {
"number": 13,
"dayOfTrecena": 4,
"rulingSign": "kaban",
"rulingSignName": "Kabʼan"
},
"reading": {
"keynote": "The nawal Ajaw, called AJPUʼ in the highland daykeeping tradition, is the sun at its height, the completed day and the authority that comes with finishing. The sign itself is read as lord, ruler, sun.",
"numberReading": "The coefficient 4 has no character recorded for it in the sources this API is built on, so no reading is offered for the number alone. The sign carries the day.",
"strengths": [
"Finishes what was started and lets the result be seen",
"Warms a whole room rather than one corner of it"
],
"challenges": [
"Needs the light on it and dims when the light moves",
"Treats a finished thing as final and stops asking about it"
],
"guidance": "Give the credit away once today. A sun that shines only on itself lights nothing."
}
},
"haab": {
"month": "kankin",
"monthName": "Kʼankʼin",
"monthClassic": "Kankin",
"day": 3,
"dayOfYear": 263,
"reading": "The Haab date is 3 Kʼankʼin, inside a period read this way: The yellow sun, ripening light, where the year turns toward its harvest."
},
"longCount": {
"formatted": "13.0.0.0.0",
"baktun": 13,
"katun": 0,
"tun": 0,
"winal": 0,
"kin": 0,
"daysSinceEpoch": 1872000,
"julianDayNumber": 2456283
},
"calendarRound": "4 Ajaw 3 Kʼankʼin",
"lordOfNight": {
"label": "G9",
"reading": "The night belongs to G9 of the nine, a cycle that turns one step every day and closes every nine. The Maya names for the nine were never recorded, so the cycle is published by its glyph labels alone."
},
"yearBearer": {
"daySign": "kaban",
"daySignName": "Kabʼan",
"number": 1,
"reading": "The Haab year is carried by 1 Kabʼan, read at the seating of Pop. This is the Classic set, and it is the one highland daykeepers still run today."
},
"cross": [
{
"position": "center",
"offsetDays": 0,
"daySign": "ajaw",
"daySignName": "Ajaw",
"daySignKiche": "AJPUʼ",
"number": 4,
"reading": "The centre of the cross is the birth nawal itself, 4 Ajaw, and every arm is read against it."
},
{
"position": "conception",
"offsetDays": -8,
"daySign": "eb",
"daySignName": "Ebʼ",
"daySignKiche": "E",
"number": 9,
"reading": "The conception arm, eight days before the birth day, is 9 Ebʼ. It is read as the root the life is drawn from."
},
{
"position": "destiny",
"offsetDays": 8,
"daySign": "lamat",
"daySignName": "Lamat",
"daySignKiche": "QʼANIL",
"number": 12,
"reading": "The destiny arm, eight days after the birth day, is 12 Lamat. It is read as later life and as what is left behind."
},
{
"position": "left",
"offsetDays": 6,
"daySign": "kimi",
"daySignName": "Kimi",
"daySignKiche": "KAME",
"number": 10,
"reading": "The left arm, six days after the birth day, is 10 Kimi. It is read as one of the two sides the life is balanced between."
},
{
"position": "right",
"offsetDays": -6,
"daySign": "ix",
"daySignName": "Ix",
"daySignKiche": "IʼX",
"number": 11,
"reading": "The right arm, six days before the birth day, is 11 Ix. It is read as the other of the two sides."
}
],
"summary": "This day is 4 Ajaw 3 Kʼankʼin, Long Count 13.0.0.0.0. The nawal is Ajaw, the sun at its height, the completed day and the authority that comes with finishing, carried on the coefficient 4.",
"conventions": {
"correlation": "gmt-584283",
"yearBearerSystem": "classic"
}
}Structured JSON with documented fields. Not hallucinated text. See all endpoints
Works with your stack
Calculate Mayan astrology day signs, the Tzolkin sacred round, the Haab year, the full Long Count and the Aztec tonalpohualli from any date: day sign and coefficient, trecena, Calendar Round, Lord of the Night, Year Bearer and the five point Cruz Maya, each with a composed reading. The correlation constant that makes two Mayan calculators disagree is a typed parameter with a named default rather than a hidden pick, and every response echoes the conventions it was computed under, so a saved chart stays reproducible. Both naming traditions ship on every sign, the Yucatec spelling and the Kʼicheʼ name daykeepers actually use, and readings come back in every language the API ships. One key covers every RoxyAPI domain, with Remote MCP and typed SDKs.
Every Mesoamerican Astrology 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 Mesoamerican Astrology API, built for production:
The correlation constant is a typed request parameter with a named default, not a hidden pick: four published constants are offered, the resolved one comes back on every response, and a saved chart can therefore be reproduced or matched against a published inscription reading years later
Both naming traditions on every day sign: the Yucatec spelling in the standard orthography, the sixteenth century form that printed reference tables use, and the Kʼicheʼ name from the living highland daykeeping practice, all carried as data so they read the same in every language
One call returns the whole day rather than a fragment of it: Tzolkin sign and coefficient, Haab date, the five position Long Count with its day count and Julian Day Number, the Calendar Round, the Lord of the Night, the Year Bearer and the five point Cruz Maya
The Year Bearer school and the world direction reading are typed conventions too, because the three bearer sets share no member and the two direction readings sit a quarter turn apart, so a silent default would be a school choice disguised as a fact
The Aztec tonalpohualli is a first class family on the same key, with its own anchored day count, sign catalogue and trecenas, and it states plainly which fields it does not return and why
Any date from 3114 BC to the twenty second century costs exactly what today costs, because a Mesoamerican day is an integer function of the elapsed day rather than an ephemeris lookup, so a date five millennia back costs exactly what today costs
Classical and academic count only: the unbroken day count from the Long Count epoch, verified against two institutional converters at thirteen dates spanning five millennia and under every correlation offered, so an answer here is one a daykeeper would recognise
All 18 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.
Show all endpointsShow fewer endpoints
What You Can Build with Mesoamerican Astrology API
Real-world applications and use cases for integrating Mesoamerican Astrology API into your projects:
Mayan astrology and nawal apps: day sign, coefficient, trecena and the five point cross from one birth date
Spanish language calculators: the nahual, the Cruz Maya and the daily energy, with the correlation daykeepers use
Calendar and education tools: Long Count conversion both ways, Calendar Round, Haab dates and a whole month grid in one call
Daily content platforms: a deterministic day sign of the day for both calendars, cached and safe to schedule weeks ahead
Multi domain spiritual companions: a Mayan card beside a natal chart and a BaZi chart, on one key with the same conventions echo shape
Epigraphy and museum software: place an inscription date on a civil calendar under a named correlation constant
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 Mesoamerican Astrology 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 Mesoamerican Astrology 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 Mesoamerican Astrology endpoint runs live in the API playground
Mesoamerican Astrology API FAQ
How do I find my Mayan sign with an API?
Send a birth date to the Tzolkin endpoint and the day sign comes back with its coefficient, its trecena and a composed nawal reading, in one response. The sign arrives in three namings at once: the standard Yucatec spelling, the sixteenth century form older books print, and the Kʼicheʼ name highland daykeepers use, so you can label it the way your audience expects. Typed SDKs and a Remote MCP server are available on the same key, along with every other RoxyAPI domain.
Why do two Mayan sign calculators give different answers for one date?
Usually one of two reasons, and both are stated on every response here. The first is the correlation constant, the number that ties the day count to a civil date: several are published, they sit a few days apart, and a calculator that does not say which it used cannot be checked. The second is that some popular tools run the modern Dreamspell or thirteen moon count, which freezes its count on 29 February and has therefore drifted away from the classical day count by a different amount at every date. This API runs the classical count only and names the constant it used.
Which correlation constant should I use?
Use the default unless you have a reason not to. It is the commonly accepted constant, the one the major institutional converter runs on, and the one a highland daykeeper count agrees with. The three alternatives are offered because published inscription readings sometimes use them and a researcher needs to reproduce a printed value; each shifts the Long Count by exactly its difference in days from the default, which makes a disagreement easy to diagnose rather than mysterious.
What is the difference between the Mayan and the Aztec calendar here?
They are two 260 day counts with the same structure, thirteen coefficients running against twenty day signs, under different names and different anchors. The Maya family returns the Tzolkin plus the Haab year, the Long Count and the Lord of the Night; the Aztec family returns the tonalpohualli day sign, its coefficient and its trecena. The Aztec side deliberately returns fewer fields, and every response says which ones and why: where the reference sources disagree, nothing ships rather than a guess.
How is the Cruz Maya read?
The cross has five points around the birth nawal: conception eight days before the birth day, destiny eight days after, and two arms six days after and six days before. Each point returns its own day sign and coefficient with a line on what it is read as. This is a living daykeeper convention rather than an archaeological reconstruction, and the response says so on the field itself, because the academic literature describes the day count and the year bearers but not a five point cross.
Does it work for historical dates?
Yes, and without losing accuracy, because a Mesoamerican day is a plain count of elapsed days rather than an astronomical lookup. Dates are read as proleptic Gregorian throughout, including before the 1582 reform, so a tool that switches to the Julian calendar below the reform will differ by ten or eleven days on the same input; the conversion endpoint flags any date before the reform for exactly that reason. Long Count conversion runs in both directions, so an inscription date can be placed on a civil calendar and back.
Start using Mesoamerican Astrology API today.
A Mayan day sign that tells you which correlation it came from.
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