v1 · stable · 49 endpoints

Query the time.
Know the moment.

People have a temporal location. TimeQL maps it to coordinates, cross-validates across calculation systems, and returns the easiest route — as typed JSON.

Read the docs
49 Endpoints
8 Surface groups
1,000 Free requests / mo
~189ms Median latency
timeql · query → result
$ timeql query "When should we launch the rebrand?" resolving → qimen/matrix, horoscope/transits, bazi/fortune scanning → 30 day window · 3 systems best_slots[ #1 2026-04-15 AM · convergence 3 / 3 · score 94 #2 2026-04-22 PM · convergence 2 / 3 · score 78 #3 2026-05-01 AM · convergence 2 / 3 · score 71 ] 3 systems · 3 requests · 189 ms
01 · Overview

A query language
for symbolic time.

You describe what you need. TimeQL compiles it into one or more calculation systems, returns typed JSON with symbolic semantics, and leaves narrative or action to your application.

Input datetime + location, birth_date + optional name, or free-text dream material L0
Resolve compile your question into one or more calculation systems L1 — L2
Return typed JSON objects with symbolic semantics and support signals L3 — L5
Interpret narrative or action is your application's job — or use UN as the canonical L6 layer L6
02 · API surface

Start with the question,
not the tradition.

50 public routes across 8 surface groups. Profiles, timing, relations, directions, naming, latent symbolic, and observation feedback — all share one canonical shape. All endpoints →

S System
Discovery & schema
Active TimeQL contract, capability catalog, and schema surfaces.
GET/v1/updates
GET/v1/capabilities
GET/v1/endpoints
GET/v1/taxonomy
GET/v1/openapi-custom
GET/v1/health
P Profiles & charts
Birth, system, framework
Resolve a birth event or framework into a stable symbolic profile.
POST/v1/horoscope/natal
POST/v1/bazi
POST/v1/tekitenzui
POST/v1/sanmeigaku
POST/v1/jyotish
POST/v1/ziweidoushu
POST/v1/sukuyo
POST/v1/mayan
POST/v1/numerology
POST/v1/kanshi
POST/v2/body
C Compatibility
Two or more profiles
Compare profiles as a structured relation model.
POST/v1/horoscope/synastry
POST/v1/horoscope/triple_synastry
POST/v1/horoscope/composite
POST/v1/bazi/compatibility
POST/v1/sanmeigaku/compatibility
POST/v1/kyusei/compatibility
POST/v1/sukuyo/compatibility
POST/v1/sukuyo/compatibility/search
POST/v1/mayan/compatibility
POST/v1/numerology/compatibility
POST/v2/relation
T Timing & moment
Activation windows
Resolve a timestamp into temporal state and activation windows.
POST/v1/horoscope/transits
POST/v1/horoscope/transit_events
POST/v1/horoscope/event_chart
POST/v1/horoscope/progressions
POST/v1/horoscope/return_chart
POST/v1/horoscope/election
POST/v1/jyotish/gochara
POST/v1/bazi/fortune
POST/v1/sukuyo/fortune
POST/v1/liuren
POST/v1/jinkoujue
POST/v1/reading/time-space-room
POST/v2/time
D Directions & environment
Spatial configuration
Rank directions, matrix states, and environment surfaces.
POST/v1/kyusei
POST/v1/kyusei/directions
POST/v1/kyusei/guidance
POST/v1/qimen
POST/v1/qimen/matrix
POST/v1/fengshui
POST/v1/tekitenzui_qimen
POST/v1/tekitenzui_fengshui
N Naming
Score & suggest
Evaluate candidate names and return scoring or ranked suggestions.
POST/v1/seimei
POST/v1/seimei/suggest
L Latent symbolic
Free-text resolution
Resolve dream text into compiled latent states and concept families.
POST/v1/dream
O Observation
Post-compute feedback
Attach context, inner signals, and outcomes to a prior query_id.
POST/v1/feedback/context
POST/v1/signals/inner
POST/v1/feedback/outcome
03 · Architecture

Structure below the line.
Interpretation above.

TimeQL computes L0 – L5 and returns raw compute plus symbolic semantics. Your AI or application interprets above the line.

L0 Input datetime + location, or birth_date + name datetime, location, name
L1 Conversion calendar normalization, stems & branches, positions stems, branches, positions
L2 Cycles dasha, daiun, transits, progressions dasha, daiun, transits
L3 Symbols elements, archetypes, keywords, polarity elements, archetypes
L4 Relations aspects, compatibility, convergence aspects, convergence
L5 Progression timeline, ranking, scoring timeline, ranked windows
TimeQL boundary
L6 Interpretation your AI, your app — or UN as the canonical reference narrative, action
04 · Onboarding

Three steps to your
first response.

Sign up, pick a plan, get a key. No credit card required for the sandbox.

step 01
Sign up
One click with Google or GitHub. Your TimeQL workspace is created instantly.
~ 5 sec
step 02
Pick a plan
Free Sandbox includes 1,000 requests per month. Upgrade later when you ship.
Free Sandbox · JPY 0 / mo 1,000 cr
step 03
Get your API key
Send REST + JSON. Authenticate with a single bearer token. SDKs follow.
sk-tq-••••••••••
05 · Pricing

One account,
two lanes.

Personal plans meter actual usage against a monthly allowance. Developer plans meter monthly API requests, rate-limited by RPM. The two subscriptions are independent — you can hold both. All prices in JPY (tax included).

Personal

UN Reading · UN Talking · UN Coaching on the dashboard — metered by actual usage, resets monthly

Free¥0 Personal¥1,980/ mo Pro¥3,980/ mo Expert¥9,800/ mo Executive¥19,800/ mo Coach¥98,000/ mo
Monthly guide* ≈15 readings≈250 light chats ≈100 readings≈1,700 light chats ≈200 readings≈3,400 light chats ≈500 readings≈8,500 light chats ≈1,000 readings≈17,000 light chats ≈5,000 readingschat effectively unlimited
UN Reading ✓✓✓✓✓✓
UN Talking 2 characters20 characters20 characters20 characters20 characters20 characters
UN Coaching ——✓✓✓✓
Reading personas StandardAllAllAllAllAll
Custom personas ———2020100
Organizations ————1 org · 2 invites10 orgs · 3 invites

* Approximate full readings per month. Capacity is metered by actual usage, not call counts — lighter conversations go much further. Allowance resets monthly.

Upgrade any time from the dashboard — plan changes apply instantly.

Developer

API access — metered by monthly requests, rate-limited by RPM

Free Sandbox
¥0/ mo
Testing & personal use
  • 1,000 requests / mo
  • 40 requests / day
  • 5 RPM
  • All endpoints
  • Community support
Builder
¥7,980/ mo
Small apps & indie dev
  • 15,000 requests / mo
  • 600 requests / day
  • 25 RPM
  • Email support
Growth Production
¥24,800/ mo
Scaling products
  • 90,000 requests / mo
  • 3,600 requests / day
  • 75 RPM
  • Priority support
Scale
¥79,800/ mo
Production workloads
  • 400,000 requests / mo
  • 16,000 requests / day
  • 200 RPM
  • Dedicated support

Enterprise

SLA 99.95% · Custom RPM · Custom features · Dedicated support · White-label

Contact sales →

Request calculator

Every call counts as one request, regardless of endpoint depth. Estimate monthly volume to find the right plan.

Requests / mo
0
0requests / month
Free Sandbox
06 · Method

Method, trust,
and control.

TimeQL is the compute layer. What it returns is auditable, typed, and explicit about its limits.

01
Not a prose generator
TimeQL returns typed JSON, never narrative. Interpretation stays in your application.
02
Not one tradition
Multiple calculation systems cross-validate. No single forced answer.
03
Not a black box
Every score has explainable support signals. Convergence and divergence are first-class.
04
Not a replacement
Your product logic stays yours. TimeQL provides typed primitives — you decide what to do with them.
OpenAPI 3.1 Changelog Methodology
Free Sandbox · 1,000 requests / mo

Get started

Sign in to receive your API key.

公開審査用のサンプルデータでダッシュボード全体を確認できます。