Time-Lord Techniques

Hellenistic Timing API: 12 Endpoints, One Namespace

Every classical time-lord technique under /api/v3/timing/*: profections, firdaria, decennials, zodiacal releasing, sun-conjunctions, and exact aspect passages between two transiting bodies.

Plus a Timeline aggregator that returns every active period in one call. Sect-aware, MCP-ready, sub-300ms.

View All 12 Endpoints

Timing Endpoints

<300ms

P95 Response

Classical Techniques

MCP

Agent-Compatible

Swiss Ephemeris Precision

Sect-Aware Lord Logic

SVG Renderers Included

Transform with

What the /timing Namespace Ships

Hard numbers, not marketing fluff

Timing Endpoints

<300ms

P95 Response Time

Profection Anchors

Classical Techniques

~10

Cached Planet Positions per Request

99.9%

Uptime SLA

What You Get in the /timing Namespace

Twelve endpoints, seven techniques, one schema

Timeline Aggregator

One POST to /timing/timeline returns every active time-lord across profections, firdaria, decennials, and ZR for a given date

Fan-out to four technique services in parallel, merge by date, return a single chronologically sorted list of active periods with their rulers

Six Profection Endpoints

Annual, monthly, daily, continuous, biwheel, and aspects. Every resolution from a life timeline down to today's profected aspects

Six routes under /timing/profections/* sharing one ProfectionService, six anchors (ASC, Fortune, Sun, Moon, MC, Spirit), whole-sign and Medieval 30°/year both supported

Sect-Aware Lord Logic

Firdaria L1/L2 and Decennials starter are computed from chart sect, not hardcoded

Day charts start firdaria with the Sun and order decennials from angular planets above the horizon; night charts start with the Moon and use planets below

Zodiacal Releasing (Valens)

Full ZR from the Lots of Fortune and Spirit, L1 through L4, with Loosing of the Bond transitions detected

/timing/zodiacal-releasing for the full timeline, /timing/zodiacal-releasing/current for the active L1-L4 stack at a specific date

Sun-Conjunctions Calculator

Detect Cazimi, Combust, and Under the Beams with three orb presets

Modern preset: Cazimi within 17 arcminutes, Combust within 8°30′, Under the Beams within 17°. Lilly and Bonatti presets shift the traditional orbs accordingly

Aspect Passages: Transit-to-Transit Timing

Find the exact date two transiting planets aspect each other in the sky, independent of any birth chart. Built for mundane astrology, market-timing tools, and generic ephemeris apps

POST /timing/aspect-passages takes a date window and either explicit pairs or a body list expanded to every unordered pair, returns one row per exact perfection with exact_utc, side, relative_motion, and relative_speed. A retrograde loop returns multiple rows, never one blurred window

MCP Tool Registration

Every timing endpoint is exposed as a Model Context Protocol tool for Claude, GPT, Cursor, and other agents

Tool schemas auto-generated from the FastAPI request models, parameter validation preserved, examples copied from the OpenAPI spec

SVG Renderers

Age-bands wheel and bi-wheel overlays render directly to SVG. No client-side chart library required

/svg/timing/age-bands-wheel returns a wheel with the 12 profection ages mapped onto sign segments; /svg/timing/biwheel renders the profected chart over the natal

Six Profection Anchors

Switch the profected sign source between ASC, Fortune, Sun, Moon, MC, and Spirit

Anchor parameter on every profection endpoint; the same age can be projected from any of the six points without recomputing the underlying chart

Shared Subject Schema

Pass birth data once in the standard subject shape and every endpoint accepts it

City-based input resolves to lat/lng/timezone via GeoService; coordinate-only subjects skip geocoding. Same shape across all 12 endpoints

What is the /api/v3/timing Namespace?

A hub for every Hellenistic and Medieval time-lord technique

The /api/v3/timing/* namespace is a single hub for classical time-lord techniques. It exposes 12 endpoints covering profections (six variants), firdaria, decennials, zodiacal releasing, sun-conjunctions, aspect passages between two transiting bodies, and a Timeline aggregator that returns every active period across techniques in one call. All endpoints share the same subject schema, so once you pass birth data once, every technique is a single POST away. Sect logic runs where it matters (firdaria L1/L2, decennials starter). SVG renderers handle the age-bands wheel and bi-wheel overlays. The whole namespace is registered as Model Context Protocol tools, so a Claude or GPT agent can call profections or zodiacal releasing the same way it calls a database.

What are the 12 endpoints in /api/v3/timing?

Six profection endpoints: /profections/annual (multi-year timeline, six anchors), /profections/monthly (12 sub-periods per year), /profections/daily (12 daily windows per profection month), /profections/continuous (Medieval 30°/year continuous profection), /profections/biwheel (profected chart overlaid on natal), and /profections/aspects (profection-to-natal aspects at a date).

Then /firdaria (Persian L1/L2, sect-aware, 75-year cycle), /decennials (Hellenistic 10-year periods, Chaldean order), /zodiacal-releasing plus /zodiacal-releasing/current (Vettius Valens, Lots of Fortune and Spirit, L1 through L4), /sun-conjunctions (Cazimi within ~17′, Combust ~8°30′, Under the Beams ~17°), /aspect-passages (exact aspect timing between two transiting bodies, no natal chart involved), and /timeline.

The aggregator asks every technique what's active right now and returns the union.

12 endpoints, one shared subject schema, one POST per technique

1 min read

How does the /timing/timeline aggregator work?

Timeline is the flagship endpoint.

Pass a subject and a target date.

It calls profections, firdaria L1+L2, decennials, and zodiacal releasing in parallel, then merges the results into a single chronologically sorted list of active periods.

You get the lord of the year, the active firdaria sub-period, the current decennial ruler, and the ZR L1/L2 periods on Fortune and Spirit, all in one round trip.

This is the endpoint you wire into a dashboard or an agent.

Instead of building a state machine that calls four endpoints and reconciles overlapping periods, you call /timeline and render.

Caches the ~10 natal positions across techniques, so the marginal cost of asking for every period at once is small.

One call, every active time-lord across all 6 techniques

1 min read

Profections in depth: annual, monthly, daily, continuous, biwheel, aspects

Profections is the most-used technique in modern Hellenistic practice, so it gets six endpoints.

Annual returns the multi-year table with age, profection sign, profection house, Lord of the Year, and the LOY's natal placement.

Six anchors are supported: ASC (canonical), Fortune, Sun, Moon, MC, and Spirit.

Monthly subdivides each year into 12 month-long sub-profections.

Daily subdivides each profection month into 12 daily windows.

Continuous returns the Medieval 30°-per-year linear profection, useful when you need to direct a specific degree rather than a whole sign.

Biwheel produces a profected chart overlaid on the natal, ready to render as SVG.

Aspects returns the live aspects formed between the profected positions and the natal chart at a chosen date.

That last one is the operational layer most clients actually want.

See /p/profections for the dedicated page.

Six profection endpoints, six anchors, one schema

1 min read

Hellenistic time-lords: Firdaria, Decennials, Zodiacal Releasing

Firdaria is Persian time-lord with a 75-year cycle.

The L1 ruler depends on sect: diurnal charts start with the Sun, nocturnal with the Moon.

Each major period is divided into seven L2 sub-periods.

Decennials is Hellenistic, 10-year periods in Chaldean order, with the starter chosen by sect logic from the angular planets near the Hour-Marker.

Zodiacal releasing is Vettius Valens, released from the Lot of Fortune for body and livelihood, or from Spirit for career and reputation, with L1 through L4 nested sub-periods and Loosing of the Bond transitions.

Each has its own deep-dive page: /p/firdaria, /p/decennials, /p/zodiacal-releasing.

The hub gives you the endpoint; the dedicated pages explain the theory.

Sect-aware lord logic across firdaria L1/L2 and decennials starter

1 min read

Sun-Conjunctions: Cazimi, Combust, Under the Beams

The /timing/sun-conjunctions endpoint detects when natal or transiting planets sit close to the Sun.

Three orb presets ship: Modern (Cazimi 17 arcminutes, Combust 8°30′, Under the Beams 17°), Lilly (Cazimi 17′, Combust 8°30′, Under the Beams 17°), and Bonatti (slightly different traditional orbs).

Cazimi is a powerful dignity: a planet in the heart of the Sun is treated as exalted.

Combust is debilitating.

The endpoint returns the exact orb, the condition (Cazimi, Combust, Under the Beams, or none), and the time windows.

Useful for electional astrology and for flagging when a transiting Mercury station happens combust.

See /p/cazimi-combust for the dedicated page.

Three classical orb presets: Modern, Lilly, Bonatti

1 min read

Aspect Passages: when do two transiting planets aspect each other?

Every other endpoint in /timing answers a transit-to-natal question: where a moving planet stands against a fixed point in your birth chart.

/timing/aspect-passages answers a different question, with no birth chart involved at all: when do two MOVING planets aspect each other in the sky.

Pass a date window plus either explicit pairs (Jupiter and Saturn) or a body list that expands to every unordered pair, and the endpoint returns the exact UTC instant each aspect perfects.

A retrograde loop, like the three Saturn-square-Uranus perfections of 2021 (February, June, December), comes back as three separate rows instead of one blurred window, each tagged with relative_motion (forward or reversed) and side (waxing or waning, read from the faster body).

Choose an aspect set (ptolemaic, configured_four, baigent_event_four) or list aspects explicitly.

This is the endpoint for mundane astrology, financial and market-timing tools, and any ephemeris app that needs a planet-to-planet event calendar independent of a specific person's chart.

Transit-to-transit timing, no natal chart required

1 min read

MCP tools: call timing endpoints from Claude or GPT agents

Every endpoint in /api/v3/timing is registered as a Model Context Protocol tool.

An AI agent (Claude Desktop, an agent you build on top of GPT, a Cursor extension) can call get_annual_profections or get_timing_timeline the same way it calls a SQL tool.

The schemas, examples, and parameter validation are all exposed through MCP.

This means you can build a 'birth chart copilot' that, given a question like 'what's my lord of the year and is anything close to combust right now', resolves the question by calling profections and sun-conjunctions and then narrates the result.

The SVG renderers (/svg/timing/* age-bands wheel, /svg/timing/biwheel) are also tool-accessible, so an agent can ask for a rendered wheel and embed the PNG.

MCP-registered: every timing endpoint is an agent tool

1 min read

Use Cases

Mobile Astrology Apps

Show users their lord of the year, active firdaria, and current ZR period without writing the algorithms yourself

Professional Practice Tools

Power a consulting dashboard that surfaces every active time-lord at a glance via the Timeline aggregator

AI Astrology Agents

Wire MCP tools into Claude or GPT so an agent can answer questions by calling profections or ZR directly

Electional Software

Combine sun-conjunctions (Cazimi/Combust) with profections-aspects to score election windows

Mundane & Financial Astrology

Find the exact date two transiting planets aspect each other, like a Jupiter-Saturn conjunction, with no birth chart involved

Technical Specifications

Endpoints	12 under /api/v3/timing/*
Response Time	<300ms P95 worldwide
Profection Anchors	ASC, Fortune, Sun, Moon, MC, Spirit
Profection Resolutions	Annual, monthly, daily, continuous, biwheel, aspects
Firdaria Cycle	75 years, sect-aware L1/L2
Decennials Order	Chaldean, sect-aware starter
Zodiacal Releasing	Vettius Valens, Fortune and Spirit, L1-L4
Sun-Conjunction Presets	Modern, Lilly, Bonatti
Aspect Passages	Transit-to-transit exact timing, ptolemaic/configured_four/baigent_event_four aspect sets
SVG Renderers	/svg/timing/age-bands-wheel, /svg/timing/biwheel
MCP Integration	All 12 endpoints registered as MCP tools
Ephemeris	Swiss Ephemeris, 6000 BCE to 6000 CE
Subject Schema	Shared across the whole namespace

Hub Namespace vs Single-Technique Libraries

Feature	Astrology API	Others
Techniques Covered	Profections, Firdaria, Decennials, ZR, Sun-Conjunctions, Timeline	Usually annual profections or solar return only
Timeline Aggregator	One call returns every active period	Build the aggregation layer yourself
Profection Resolutions	Annual, monthly, daily, continuous, biwheel, aspects	Annual only
Sect Logic	Built into firdaria L1/L2 and decennials starter	Diurnal/nocturnal handling is on you
Sun-Conjunctions	Cazimi, Combust, Under the Beams with three orb presets	Not provided
Transit-to-Transit Timing	Dedicated aspect-passages endpoint, exact dates between two moving bodies	Transit-to-natal only, no chart-independent timing
SVG Output	Age-bands wheel and bi-wheel renderers included	Render the wheel yourself in D3
AI Agent Integration	All endpoints registered as MCP tools	No agent tooling
Subject Schema	One schema across 12 endpoints	Different input shape per library

Dedicated Pages for Each Technique

Profections API

Annual, monthly, daily, continuous, biwheel, aspects: the deep dive on the six-endpoint profection family

Firdaria API

Persian time-lord with a 75-year cycle, sect-aware L1 and L2 sub-periods

Zodiacal Releasing API

Vettius Valens ZR from Fortune and Spirit, L1 through L4, Loosing of the Bond

Cazimi & Combust API

Sun-conjunctions with Modern, Lilly, and Bonatti orb presets

Horary API

Question-based timing for traditional horary practice

Solar Return API

Annual solar return charts, paired well with annual profections

Vimshottari Dasha API

Vedic 120-year dasha cycle if you're shipping a Jyotish flavor alongside Hellenistic

References & Standards

Swiss Ephemeris (DE431-based) — astronomical calculations source
NASA JPL Planetary Ephemerides — underlying ephemeris dataset
International Astronomical Union (IAU) — body designation and nomenclature standards
IANA Time Zone Database — timezone & DST resolution

Simple, Transparent Pricing

Start free, scale as you grow. No hidden fees, no surprises.

Always Free

Start Free

Perfect for learning, testing, and small personal projects

50 API calls/month

Basic natal charts

5 house systems

Community support

Pro

$11/month

For small apps and personal projects

All basic endpoints
12 house systems
Email support

Best Value

Pro Plus

$21/month

For growing apps and medium traffic

All enhanced endpoints
18 house systems
AI interpretations
Priority email support

Ultra

$37/month

For professional astrology applications

Credit math ↓

All premium endpoints
23 house systems
Advanced AI interpretations
Priority support

High Volume Plans

For enterprise-scale applications

Business

$99/month

For high-volume applications

Credit math ↓

ALL endpoints
White-label ready
Custom AI fine-tuning
Phone support

UNLIMITED

Enterprise

$399+per month

Unlimited requests with dedicated infrastructure

Dedicated server infrastructure
Sub-300ms guaranteed
24/7 dedicated support
99.99% uptime SLA

All plans include comprehensive documentation and SDKs

Questions? Talk to our team

Hellenistic Timing API: Questions Developers Actually Ask

If it's not here, the OpenAPI spec probably answers it

General

What endpoints are in the /api/v3/timing namespace?

Features

What does the /timing/timeline aggregator do?

Integration

Can I use the timing endpoints as MCP tools with Claude or GPT?

Features

Do you support SVG rendering of timing wheels?

Features

How is monthly profection different from annual?

Use Cases

Which time-lord technique should I expose first in my app?

Technical

What is sect and where does it matter in your timing endpoints?

Features

What is Cazimi and how does the sun-conjunctions endpoint detect it?

Technical

How accurate are the underlying calculations?

Technical

What programming languages can I call this from?

Pricing

How much does the Timing API cost?

Performance

Is the response time really under 300ms?

Features

Do you support both whole-sign and degree-based profection?

Features

Can I get profection-to-natal aspects at a specific date?

Features

Can I find when two transiting planets aspect each other, without a natal chart?

Features

Does Zodiacal Releasing go all the way to L4?

Comparison

What's the difference between this and your /transit-api?

Each Technique Has Its Own Deep-Dive Page

The /timing hub gives you the endpoint. The pages below explain the theory, the orbs, and the edge cases. Start with

Ship Time-Lord Techniques Without Writing Them

The /api/v3/timing namespace gives you all 12 endpoints, sect-aware logic, SVG renderers, and MCP tool registration. Free tier: 50 requests every month, forever.

Try the Timeline Endpoint View OpenAPI Spec

12 Endpoints in One Namespace

<300ms P95 Response

Registered as MCP Tools

Free Tier · No Card Required · Swiss Ephemeris Precision

What is the /api/v3/timing Namespace?

A hub for every Hellenistic and Medieval time-lord technique

Use Cases

Mobile Astrology Apps

Show users their lord of the year, active firdaria, and current ZR period without writing the algorithms yourself

Professional Practice Tools

Power a consulting dashboard that surfaces every active time-lord at a glance via the Timeline aggregator

AI Astrology Agents

Wire MCP tools into Claude or GPT so an agent can answer questions by calling profections or ZR directly

Electional Software

Combine sun-conjunctions (Cazimi/Combust) with profections-aspects to score election windows

Mundane & Financial Astrology

Find the exact date two transiting planets aspect each other, like a Jupiter-Saturn conjunction, with no birth chart involved

Technical Specifications

Endpoints	12 under /api/v3/timing/*
Response Time	<300ms P95 worldwide
Profection Anchors	ASC, Fortune, Sun, Moon, MC, Spirit
Profection Resolutions	Annual, monthly, daily, continuous, biwheel, aspects
Firdaria Cycle	75 years, sect-aware L1/L2
Decennials Order	Chaldean, sect-aware starter
Zodiacal Releasing	Vettius Valens, Fortune and Spirit, L1-L4
Sun-Conjunction Presets	Modern, Lilly, Bonatti
Aspect Passages	Transit-to-transit exact timing, ptolemaic/configured_four/baigent_event_four aspect sets
SVG Renderers	/svg/timing/age-bands-wheel, /svg/timing/biwheel
MCP Integration	All 12 endpoints registered as MCP tools
Ephemeris	Swiss Ephemeris, 6000 BCE to 6000 CE
Subject Schema	Shared across the whole namespace

Hub Namespace vs Single-Technique Libraries

Feature	Astrology API	Others
Techniques Covered	Profections, Firdaria, Decennials, ZR, Sun-Conjunctions, Timeline	Usually annual profections or solar return only
Timeline Aggregator	One call returns every active period	Build the aggregation layer yourself
Profection Resolutions	Annual, monthly, daily, continuous, biwheel, aspects	Annual only
Sect Logic	Built into firdaria L1/L2 and decennials starter	Diurnal/nocturnal handling is on you
Sun-Conjunctions	Cazimi, Combust, Under the Beams with three orb presets	Not provided
Transit-to-Transit Timing	Dedicated aspect-passages endpoint, exact dates between two moving bodies	Transit-to-natal only, no chart-independent timing
SVG Output	Age-bands wheel and bi-wheel renderers included	Render the wheel yourself in D3
AI Agent Integration	All endpoints registered as MCP tools	No agent tooling
Subject Schema	One schema across 12 endpoints	Different input shape per library

Hellenistic Timing API: 12 Endpoints, One Namespace

Time-Lord Techniques Are Scattered Across Five Libraries

One Namespace, 12 Endpoints, One Subject Schema

What the /timing Namespace Ships

What You Get in the /timing Namespace

Timeline Aggregator

Six Profection Endpoints

Sect-Aware Lord Logic

Zodiacal Releasing (Valens)

Sun-Conjunctions Calculator

Aspect Passages: Transit-to-Transit Timing

MCP Tool Registration

SVG Renderers

Six Profection Anchors

Shared Subject Schema

What is the /api/v3/timing Namespace?

What are the 12 endpoints in /api/v3/timing?

How does the /timing/timeline aggregator work?

Profections in depth: annual, monthly, daily, continuous, biwheel, aspects

Hellenistic time-lords: Firdaria, Decennials, Zodiacal Releasing

Sun-Conjunctions: Cazimi, Combust, Under the Beams

Aspect Passages: when do two transiting planets aspect each other?

MCP tools: call timing endpoints from Claude or GPT agents

Use Cases

Mobile Astrology Apps

Professional Practice Tools

AI Astrology Agents

Electional Software

Mundane & Financial Astrology

Technical Specifications

Hub Namespace vs Single-Technique Libraries

Dedicated Pages for Each Technique

Profections API

Firdaria API

Zodiacal Releasing API

Cazimi & Combust API

Horary API

Solar Return API

Vimshottari Dasha API

References & Standards

Simple, Transparent Pricing

Always Free

Pro

Pro Plus

Ultra

Business

Enterprise

Hellenistic Timing API: Questions Developers Actually Ask

What endpoints are in the /api/v3/timing namespace?

What does the /timing/timeline aggregator do?

Can I use the timing endpoints as MCP tools with Claude or GPT?

Do you support SVG rendering of timing wheels?

How is monthly profection different from annual?

Which time-lord technique should I expose first in my app?

What is sect and where does it matter in your timing endpoints?

What is Cazimi and how does the sun-conjunctions endpoint detect it?

How accurate are the underlying calculations?

What programming languages can I call this from?

How much does the Timing API cost?

Is the response time really under 300ms?

Do you support both whole-sign and degree-based profection?

Can I get profection-to-natal aspects at a specific date?

Can I find when two transiting planets aspect each other, without a natal chart?

Does Zodiacal Releasing go all the way to L4?

What's the difference between this and your /transit-api?

Each Technique Has Its Own Deep-Dive Page

Ship Time-Lord Techniques Without Writing Them

Time-Lord Techniques Are Scattered Across Five Libraries

One Namespace, 12 Endpoints, One Subject Schema

What the /timing Namespace Ships

What You Get in the /timing Namespace

Timeline Aggregator

Six Profection Endpoints

Sect-Aware Lord Logic

Zodiacal Releasing (Valens)

Sun-Conjunctions Calculator

Aspect Passages: Transit-to-Transit Timing

MCP Tool Registration

SVG Renderers

Six Profection Anchors