AstroWay/api v2.105.4 · ja
すべてのシステムが正常です
// astrology api · POST /v1/acg/by-category

Astrocartography interpretation API

Line geometry alone does not tell a user where to move. This endpoint takes an area of life, picks the astrocartography lines that actually govern it, ranks them by how strongly and how closely they apply, and returns the interpretation text for each. One call replaces the planet-to-theme mapping every relocation product otherwise has to invent in-house.

Endpoint
POST /v1/acg/by-category
Cost
50 credits
Latency
~210 ms
Tier
Tier 3
// 01 / What it computes

Astrocartography interpretation API

The endpoint computes the full astrocartography set for the birth moment, then filters it through a taxonomy of nineteen life areas built from the founding literature of the technique: Jim Lewis for planet-on-angle meaning, Erin Sullivan for what each of the four angles governs, and Martin Davis for the treatment of difficult lines. Each area names the lines that belong to it with a weight from one to three, so a Sun on the Midheaven outranks a Mercury on the same angle for career. Every mapping also carries a polarity, and challenging lines are returned alongside supportive ones rather than filtered away, because a relocation tool that shows only favourable lines misrepresents the technique. When you pass a point, lines outside the radius drop out and the returned strength multiplies the astrological weight by geographic proximity, which is what lets you rank candidate cities rather than merely list lines. Interpretation text is served from a curated knowledge base covering all forty planet-and-angle combinations in eleven languages, with a documented fallback when a translation is missing.

// 02 / Live request

POST/v1/acg/by-category

curl -X POST https://api.astroway.info/v1/acg/by-category \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{
  "date": "1990-05-15",
  "time": "14:30:00",
  "timezoneOffset": 3,
  "latitude": 50.45,
  "longitude": 30.52,
  "category": "career",
  "point": { "lat": 51.5074, "lng": -0.1278 },
  "radiusDeg": 8,
  "language": "en"
}'
Response (excerpt)
{
  "ok": true,
  "data": {
    "category": { "id": "career", "name": "Career" },
    "language": "en",
    "count": 3,
    "lines": [
      {
        "planet": "Jupiter",
        "type": "MC",
        "weight": 3,
        "polarity": "supportive",
        "strength": 2.31,
        "distanceDeg": 1.84,
        "interpretation": {
          "title": "Jupiter - MC",
          "text": "Expansion of professional opportunity…",
          "lang": "en"
        }
      }
    ]
  }
}
// 03 / Parameters

Parameters

nametypeRequired
date string (YYYY-MM-DD) yes Birth date.
time string (HH:MM:SS) yes Local clock time at birth.
timezoneOffset number (hours) yes UTC offset in effect at the birth moment.
latitude number yes Birth-place latitude, decimal degrees.
longitude number yes Birth-place longitude, decimal degrees.
category string yes One of 19 life areas: career, love, money, health, home, learning, power, travel and more. Fetch the full list from GET /v1/acg/categories.
point { lat, lng } no Optional geographic focus. With it, only lines running within radiusDeg of that point are returned and strength folds in proximity.
radiusDeg number no Search radius in degrees around point. Default 4, range 0.5 to 20.
polarity string no supportive, challenging, or all (default). Challenging lines are returned by default rather than hidden.
includeText boolean no Attach the interpretation text for each line. Default true.
includeCoordinates boolean no Attach the full line geometry. Default true; set false for a compact ranking response.
language string no Interpretation language. Falls back to English then Ukrainian when a translation is missing, and the served language is reported per line.
// 04 / When to use it

When to use it

Use this when your product answers a question phrased in ordinary language: where should I go for work, which of these three cities is best for a relationship, what does this line over my city actually mean. Three shapes cover most builds. Ranking, by sending a category and a point per candidate city and sorting on strength. Explaining, by calling /v1/acg/line-report for a single planet and angle to get the full text plus every other life area that line touches. Discovering, by fetching GET /v1/acg/categories once at zero credits and building your UI from the returned taxonomy so a new category appears without a client release. Because the text is curated rather than generated, responses are deterministic, cite no model, and cost nothing extra in inference: the same request returns the same words tomorrow.

// 05 / Notes

Notes

The taxonomy covers the ten traditional bodies. Chiron, Lilith and the lunar nodes appear in /v1/acg geometry but are deliberately outside the mapping, since the technique as Jim Lewis defined it does not assign them angular life-area rulership. Weights and polarities are editorial judgement expressed as data, versioned in the repository and auditable rather than hidden inside a prompt. Interpretation text is a knowledge-base lookup, not a language-model call, so it is stable, offline-reproducible and free of the disclaimers that generated interpretation requires.

Try the Astrocartography Interpretations API

Grab a key and make your first call in under a minute.

99.9% SLA · 有料プラン · 30日間 ステータス →