HTTP API

GEOMETRY’s primary surface for AI apps is MCP (https://mcp.geometry.app/mcp). Use that first. HTTP / REST is the secondary door for apps, scripts, and pipelines that are not MCP-native. Same three tools, same JSON contracts — different transport.

​

Status

When the branded API door is ready, this page will add curl examples, auth (?key=), and rate-limit notes — still pointing at the same tools:

• get_card_for_birthdate
• get_compatibility
• get_day_card

​

What stays the same

• Inputs (e.g. bare YYYY-MM-DD) and complete JSON outputs
• Coverage window and calendar rules — When it covers
• Keys and rotation — Where your key goes
• Payload field meaning — What you get · Field glossary

​

What to use now

1. Prefer MCP if your host supports connectors (Claude, ChatGPT, Cursor, VS Code, …).
2. If you need raw HTTP today, wait for the canonical https://api.geometry.app/… examples on this page — or use MCP until then.
3. Questions about zodiac or calendar disagreement belong in Astro wheels / FAQ — not “API vs MCP.”

​

Next

• Quickstart — connect MCP
• What you get — tools and shapes
• Support — self-serve triage