Mayan Calendar Skill

What this skill does

Give your agent Mayan calendar conversion. Call it as an MCP tool to turn any Gregorian date into Long Count, Tzolkin and Haab dates. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Mayan Calendar Skill — exactly what your agent gets back when it makes the call.

vervekit · mayancalendartool call

{
  "date": "2024-12-21"
}

result

gregorian: 2024-12-21
longCount: { … }
tzolkin: { … }
haab: { … }
calendarRound: 6 Akbal 6 Kankin
daysSinceEpoch: 1876383

Run it with your own input. Live calls happen in your dashboard, on your key.

Sign in to try

Ways to use it

Trusted facts in one call

Enable Mayan Calendar and your app can add mayan calendar to your app from a live source instead of shipping a lookup table you have to keep current.

A tool agents call for ground truth

Over MCP, your model calls mayancalendar to fetch a reference value at the moment it needs it, rather than recalling it imperfectly.

REST from any stack

Call Mayan Calendar directly to add mayan calendar to your app inline, one key across every skill.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

mayancalendar

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/mayancalendar

Ask your agent

“Enable Mayan Calendar and ask your agent to add mayan calendar to your app.”
“Use the Mayan Calendar skill for me.”

Mayan Calendar Skill, answered

How to connect it over MCP or REST.

How do I add Mayan Calendar to my app or agent?

Enable the Mayan Calendar Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the mayancalendar tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to add mayan calendar to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Mayan Calendar appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Mayan Calendar call cost?

Each call costs 1 credit. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Mayan Calendar is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Mayan Calendar is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

More Reference Data skills

Browse all skills

Trusted facts in one call

A tool agents call for ground truth

REST from any stack

Mayan Calendar Skill, answered

Give your software a way to act on the world.

Scaling in production?