Skip to main content
These tools cover a single-date Cosmic card, a two-date score (Cosmic card A vs Cosmic card B), and a name decode. One or two dates (or a name) in, and you get a lot back — every call is answered from a single deterministic lookup. Here’s the whole menu, plus the small set of repeating shapes every payload is built from, so you learn them once and can read any block. The live tool is always the source of truth for exact fields. For how to read _name / _slug / _no, see Field glossary. Naming on the pair tool: get_compatibility. Wire names to remember: get_date (single date) puts the profile at the top level — cosmic plus sibling tarot_majors (.greer / .tarot_school). get_compatibility (two dates) wraps each side as cosmic_card_a / cosmic_card_b, each holding that same profile shape. Out-of-range scope is cosmic_card_only. Every success payload also stamps tool / tool_version / engine_chain.

​
Tools

Production tools: get_date, get_compatibility, get_name. Weekday planetary ruler lives on get_date.
These are field counts — every key/value pair returned. name, slug, and _no are different encodings of the same entity, so the number of distinct concepts is lower; we quote fields, not unique concepts. Counts also flex with the date (the retrograde list runs ~17–23 active bodies), so treat them as typical, not fixed.

​
Payload conventions

  • String fields are lowercase, except glyph / symbol fields (for example unicard_symbol)
  • Missing values use typed sentinels — 0, "none", "", [] — not null, so a block keeps the same shape whether or not the concept applies. Check for the placeholder, not for null. One documented exception: day_ruler.norse.deity is null on Saturdays (see Field glossary)
  • There is no full_payload flag. Each tool’s only inputs are its date (or name) fields. MCP and HTTP responses always include the complete object
  • Chat UIs may summarize. To see every field in chat, ask the agent for the raw tool result — that instruction is to the model, not a GEOMETRY parameter

​
Sign object

Every zodiac, calendar-month, rune, and cyclical block returns the same core shape: Blocks that return a sign object include lunar, nong_li, coptic, mayan_haab, hebrew_monthly, dreamspell_monthly, celtic_ogham, celtic_coligny, norse_runes, chakra, each wheel under astro_wheels, and true_sidereal. Read sign_slug; the meaning of sign_no differs per system.

​
Card object

The playing-card and tarot decks (cosmic, tarot, medicine, and lenormand) share:

​
Aspect map

Wherever a Western-style sign has relationships — each wheel under astro_wheels, and true_sidereal.relationships — you get six keys: trine, square, sextile, quincunx, opposition, semisextile. Each holds one or two mini sign objects (sign_no, sign_name, sign_slug). Chinese zodiac uses those same labels where they apply, plus one extra: harmonic_pair (the secret-friend / complementary animal pair — not a Western aspect). On get_compatibility, the scored Chinese name is chinese_zodiac_aspect (trine, harmonic_pair, opposition, square, sextile, semisextile, quincunx, or none). The leftover 9027 Western-grid label on the same pair is chinese_wheel_aspect (informational; chinese_wheel_bonus is shown, not summed).

​
Element object

classical_element and periodic_element both carry element_no and element_name (plus element_symbol); the periodic lane adds atomic_no. The two lanes read differently — see Field glossary.