🛰️ Sviluppatori

The API, the MCP endpoint and llms.txt — the full text

1. What is there

The public API lives under /api/v1/: the index at /api/v1/ names every route; the interactive documentation is at /api/v1/docs, the OpenAPI description at /api/v1/openapi.json, the changes at /api/v1/changelog. It is keyless and read-only, answers JSON (errors as application/problem+json), and is open to any origin (CORS). Names are the site's own slugs, never database ids; times are ISO 8601 with their offset; units are SI.

• GET /api/v1/clock?at=&lat=&lon= — the astro clock: the chart of any moment anywhere (planets with dignities, angles and houses, the Sun and the Moon over the horizon, the Moon's phase and her next aspect); GET /api/v1/venues/{slug}/clock?at= the same over a ground, GET /api/v1/venues/{slug}/conditions?at= the Sun, the Moon and the stored forecast there.
• GET /api/v1/events (by sport, league, team, date, status) and GET /api/v1/events/{sport}/{slug}, with /chart, /conditions, /personnel and /read under each game.
• GET /api/v1/sports, /leagues, /teams, /teams/{sport}/{slug}, /players, /players/{slug}, /venues, /venues/{slug}.

The MCP endpoint (Model Context Protocol, Streamable HTTP) is at https://sportsaspects.com/mcp. It offers the same data as read-only tools — the clock, the grounds and their conditions, the games, the charts, the teams, the players — through the same functions and the same gates as the API; it needs no key either. /llms.txt describes the site in prose for an agent arriving cold; /robots.txt allows every public page and the API's documentation, and keeps the API's answers themselves out of the crawl, since they are not pages. Games, grounds, teams and players carry structured data (JSON-LD) in their pages.

2. What the API shows, and does not

The API shows what a visitor sees on the site, no more: a game's chart, screens and read before the game only where the game page shows them to a visitor (otherwise the answer is 402 before the game and open after it); the read only while the site shows it; the sports the site shows. It never carries anything of a member. It never carries odds, live scores or a feed's raw data: a final score is stated once a game is final, as the Scores page states it. A player's birth date, time and natal positions are not carried: the API says whether a natal chart exists and is timed, and no more.

3. Terms of use (version 2026-10-25)

The data the API, the MCP endpoint and the pages' structured data give is free to read and to use, in your own work, products and services, commercial ones included. We ask you to name the source — Data: Sports Aspects — sportsaspects.com — where you show it, but do not require it on the keyless tier.

Third-party material keeps its own terms, which pass through: forecasts are Open-Meteo's (CC BY 4.0) and are marked so in every answer that carries one; each photo names its author and licence, and those bind whoever shows it; Wikipedia's text is CC BY-SA 4.0 and is linked, not re-served.

The data is offered as it is, without warranty of any kind. It is astrology, published as a study and for interest: not advice, not a basis for a wager. Addresses that exceed about sixty requests a minute are answered 429 and asked to wait; nothing is banned for it, but an agent that mirrors the site rather than querying it may be limited further. The API's first version keeps its shape: what is added is listed at /api/v1/changelog, and a change that would break a client makes a second version beside it.

4. Keys, writes and bulk

There are no keys, writes or bulk exports on this tier. Higher limits, subscriber content and bulk access will come with keys issued by us; nothing is submitted through the API — birth data, comments and reports go through the site's own forms and the staff's review. For anything else, write to us.