Your assistant.
Our calculations.

01 / OVERVIEW

A chart engine for your assistant

The connector gives assistants such as Muse two focused tools: find a birthplace, then calculate a natal chart. It returns calculated placements and their context, ready for your assistant to explain and answer follow-up questions.

02 / CONNECTION

Connect your assistant

Use a hosted MCP connection with an API key supplied through your assistant’s credential settings. Keep the key out of chat messages, client-side code and URLs.

https://authorityastrology.com/api/v1/mcp

Authorization: Bearer <dedicated connector key>

The connector uses stateless Streamable HTTP with JSON responses. A standard MCP client handles initialization and tool discovery. POST requests use Accept: application/json, text/event-stream. Persistent SSE streams, legacy SSE transport and OAuth are not supported.

Prefer a direct API?

The same lookup and calculation are available over HTTP. The OpenAPI specification describes both endpoints and their request and response schemas.

03 / THE CONVERSATION

Start with the birth details

Ask for a Gregorian birth date, the local time of birth, and the birth city and country. If the time is approximate or unknown, preserve that information.

“What is your birth date, local birth time, and birth city/country? If you don’t know the time, that’s fine.”

Search the birthplace and show the matching city, region and country for confirmation. Use the selected result’s signed token for the calculation. Users don’t need to provide coordinates or a timezone, and the assistant must not guess them.

There is no need to collect a name, email or street address. Explain that birth details go to Authority Astrology for calculation and the place query goes to its geocoding provider.

04 / TOOL REFERENCE

Two tools. One complete flow.

Search by city or town, country, and optionally state or region. Send only the place name, not the person’s birth date or time.

{
  "query": "Greenwich, London, United Kingdom"
}

Returns up to eight matches with a display label, country, IANA timezone, coordinates and birthplaceToken. If there is no suitable match, ask for more detail. Tokens expire after one hour; search again if necessary.

Pass the confirmed location token together with the birth date and time. This example uses synthetic birth details.

{
  "birthplaceToken": "<token from the confirmed birthplace>",
  "localDate": {
    "year": 2000,
    "month": 1,
    "day": 1
  },
  "localTime": {
    "hour": 12,
    "minute": 0
  },
  "birthTimeKnowledge": "EXACT",
  "houseSystem": "P"
}

When the birth time is unknown

Use UNKNOWN and omit localTime entirely. Never substitute noon or midnight for an unknown birth time.

{
  "birthplaceToken": "<token from the confirmed birthplace>",
  "localDate": {
    "year": 2000,
    "month": 1,
    "day": 1
  },
  "birthTimeKnowledge": "UNKNOWN"
}

05 / RESPONSE DATA

Interpret the data with its context

Known-time charts include planetary positions, signs, retrograde status, houses and cusps, chart angles, aspects and orbs, applying/separating motion, moon phase, resolved UTC time and engine provenance. Calculations use the tropical zodiac and a geocentric perspective.

Longitudes, latitudes and orbs are in degrees; angular speeds are degrees/day. Distances are AU and distance speeds are AU/day. Unknown-time ranges use hourly sampling and can miss brief changes between samples.

Attribute the calculations to Authority Astrology and distinguish interpretation from calculated facts. The API does not return an AI-written reading. Transits and synastry are outside this first version.

06 / RELIABLE REQUESTS

Handle limits and missing details

The connector allows an aggregate of 600 authenticated requests per minute per backend process, including MCP discovery. This dedicated budget is separate from the website’s per-IP limit, so shared assistant servers do not consume a website visitor’s allowance. Respect HTTP 429 and Retry-After. Request bodies are limited to 16 KiB; JSON-RPC batches are not supported.

MCP tool failures include isError: true and a structured error code. Direct API errors use HTTP status codes and an error object.

07 / DATA HANDLING

Calculate without creating a profile

The connector does not save a customer profile or report. Birth details are used for the calculation, and only the place-search query is sent to LocationIQ. City lookups are cached in memory for ten minutes; birth details and chart responses are not deliberately logged or stored by the connector.

Birthplace tokens are signed, not encrypted, and contain the selected location. They contain no birth date or time. Responses use Cache-Control: no-store. Your assistant’s conversation retention is governed separately.

The integration key is a server-side credential. Keep it in your assistant platform’s credential settings and do not distribute it to individual users. It grants calculation access only, without access to saved customer profiles or reports.