Mayan Calendar

What it grounds

Ground agents in accurate Gregorian-to-Mayan conversions — Long Count, Tzolkin and Haab — so historical date answers rest on real calendar math.

Ways to ground with it

One call to the ground truth

Let an agent call Mayan Calendar for a trusted reference value instead of recalling it imperfectly — the answer comes from live data, with the source attached.

Replace the model's stale memory

Reference facts drift; enable mayancalendar so the agent looks them up at answer time and cites where they came from.

Auditable facts

Every reference the agent uses carries Mayan Calendar as its origin, so a person can verify it.

Connect over MCP

Point your agent framework at the VerveContext endpoint. Every enabled source — this one included — becomes a tool the model can call. No per-source plumbing.

context.json

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp",
      "headers": { "x-api-key": "vc_live_••••" }
    }
  }
}

# “mayancalendar” is now a tool your agent can call

Facts your agent can cite

Each call returns structured fields your agent can read — and trace back to this source.

gregorian
longCount
tzolkin
haab
calendarRound
daysSinceEpoch

Mayan Calendar, answered

How to ground an agent in it over MCP.

How do I give my agent Mayan Calendar?

Enable it on VerveContext and point your agent framework at the VerveContext MCP endpoint. Mayan Calendar then appears to the model as a tool named mayancalendar, which it calls when a task needs it — no per-source plumbing.

Which agents and frameworks can use it?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol. Mayan Calendar is exposed as a standard tool, so nothing source-specific is required.

Can the agent cite Mayan Calendar?

Yes. Mayan Calendar is verifiable factual grounding — every value the agent pulls can carry Mayan Calendar as its source, so a person (or another system) can trace where the fact came from.

How many credits does a Mayan Calendar call cost?

Each call costs 1 credit. Scoped keys let you grant an agent only the sources it should reach, and usage logs show exactly what was pulled to ground each answer.

How current is the data?

Mayan Calendar is served live from APIVerve's production data engine and pulled at the moment the agent calls it, so answers reflect the world now rather than the model's training cutoff.

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

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

One call to the ground truth

Replace the model's stale memory

Auditable facts

Mayan Calendar, answered

Ground your agents in Mayan Calendar. Connect over MCP, enable the source, and every answer carries its receipts.

Scaling up?