Install Jentic One Beta

Connect the NatalChart.AI API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NatalChart.AI API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnatalchart.ai%2Fnatalchart" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnatalchart.ai%2Fnatalchart" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with NatalChart.AI API.

Compute a full natal chart from a birth date, local time, latitude, and longitude: every body's longitude, sign, house, speed, and retrograde flag plus angles and Placidus cusps

Return individual chart slices such as planets, angles, house cusps, major aspects with orbs, element balance, or fixed-star conjunctions within 1.5 degrees

List every transit-to-natal aspect, sign ingress, and station across a date window of up to 92 days

Compare two charts for synastry with inter-chart aspects, house overlays both ways, and a score per life sphere

GET STARTED

Start building with NatalChart.AI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use NatalChart.AI API for, with concrete tasks.

★ Astrology assistant agent with calculated charts

An AI astrology assistant needs accurate positions rather than invented ones before it writes any interpretation. Through Jentic the agent searches for 'calculate a natal chart', loads the NatalChart.AI full chart operation with its input schema, and sends a birth object with date, time, latitude, and longitude. It receives every body's sign, degree, and house plus aspects with orbs, and grounds its reading in those numbers. The bearer key is attached by your own Jentic One instance at call time.

Call POST /v1/chart/full with birth date 1991-09-06, time 18:30, latitude 50.4501, longitude 30.5234, then report the Sun, Moon, and Ascendant signs and degrees

Transit calendar for a horoscope app

A horoscope app shows users the exact dates when transiting planets aspect their natal chart. The transits operation takes a birth object plus from and to dates covering up to 92 days and returns exact transit-to-natal aspects by date, along with sign ingresses and stations, so the app can build a personal calendar without running an ephemeris itself.

Call POST /v1/transits with a birth object and a window from 2026-12-01 to 2027-02-28, then list the exact aspects that fall in January

Relationship compatibility with synastry

A dating or relationship app compares two people's charts. The synastry operation takes personA and personB birth data and returns inter-chart aspects with orbs, house overlays in both directions, and a score for each life sphere, giving the app structured inputs for a compatibility view.

Call POST /v1/synastry with personA and personB birth objects and summarize the three tightest inter-chart aspects by orb

Electional timing and relocation

A user planning a launch or a move wants dates and places that suit their chart. The timing operation scores every day of a window of up to 62 days for an activity such as business, travel, or home and lists the five best days first, while the locations rank operation orders major cities for one chart by chosen life spheres, worldwide or within a region.

Call POST /v1/timing with activity 'business' for the next 60 days, then call POST /v1/locations/rank with region 'Europe' and limit 5 for the same birth data

Key Endpoints

17 endpoints — the natalchart.

METHOD

PATH

DESCRIPTION

POST

/v1/chart/full

Compute a full natal chart

POST

/v1/chart/short

Compute the short chart

POST

/v1/transits

List transits over a date window

POST

/v1/synastry

Compare two charts

POST

/v1/solar-return

Cast a solar return chart

POST

/v1/timing

Score days for an activity

POST

/v1/locations/rank

Rank cities for a chart

GET

/v1/sky

Get the sky for a date

POST

/v1/chart/full

Compute a full natal chart

POST

/v1/chart/short

Compute the short chart

POST

/v1/transits

List transits over a date window

POST

/v1/synastry

Compare two charts

POST

/v1/solar-return

Cast a solar return chart

POST

/v1/timing

Score days for an activity

POST

/v1/locations/rank

Rank cities for a chart

GET

/v1/sky

Get the sky for a date

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring NatalChart.AI by hand means issuing a key from its developer page, sending it as a bearer token, and building the nested birth object with date, time, coordinates, and timezone for each operation. Through Jentic you install once, import NatalChart.AI from the API Directory, store the key once, and your agent calls it.

Permission scoping

NatalChart.AI carries the birth data inside the request body, so rules bound which operations your agent may call rather than whose chart. Limit the agent to the operations it needs, such as the short chart or daily sky, so quota-heavy calls like transits or city ranking are not included unless you add them.

Credential isolation

Your NatalChart.AI key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'calculate a natal chart' or 'find the best days for travel', and Jentic returns the matching NatalChart.AI operation with its input schema so the agent sends a correctly shaped birth object.

FAQs

Specific to using NatalChart.AI API through Jentic.

What authentication does the NatalChart.AI API use?

Per its OpenAPI spec, the NatalChart.AI API uses HTTP bearer authentication: you send the API key issued on the NatalChart.AI developer keys page in the Authorization header as a bearer token. Through Jentic the key is stored encrypted by your own instance and attached per call, so it never appears in the agent's context.

What birth data does the NatalChart.AI API need?

Chart operations take a birth object with a required date (YYYY-MM-DD, 1800 to 2399), latitude, and longitude, plus an optional local time in HH:mm and an optional IANA timezone. If time is null the chart is computed for noon and time-dependent values are withheld; if timezone is left out it is resolved from the coordinates.

What are the rate limits for the NatalChart.AI API?

The spec's API description states the free plan allows 10 requests a day and API Pro allows 1000 requests a day for $6.99 a month. GET /v1/usage returns your plan, today's count, and when the pool refills, and does not count against the limit.

Is there a NatalChart.AI MCP server?

You don't need an MCP server to give your agent NatalChart.AI. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the chart, transit, and synastry operations it needs, discovered on demand rather than loaded into its context up front.

How do I calculate a natal chart with the NatalChart.AI API through Jentic?

Import NatalChart.AI from the API Directory in your Jentic One instance and store your key. Your agent searches for 'calculate a natal chart', loads POST /v1/chart/full, and sends the birth date, time, latitude, and longitude. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the NatalChart.AI API?

Yes. Write a rule that allows only POST /v1/chart/short and GET /v1/usage, and the agent can return a quick Sun, Moon, and Ascendant reading and check its remaining quota, but cannot run the heavier transit, timing, or city-ranking calculations that spend the daily request pool. Every call it makes is logged.

NatalChart.AI API

AI ReadinessFoundational (D)45/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationbearer17 EndpointsREST

For Agents

Calculate natal charts, transits, synastry, solar returns, activity timing, and relocation scores from a birth date, time, and coordinates, returned as structured JSON.

Use for: I need to calculate a natal chart for someone born on 1991-09-06 at 18:30, Find the best days for a business launch in the next two months, Get the transits to my natal chart for the next 30 days, Compare two birth charts for compatibility

Not supported: Does not write horoscope interpretations, geocode place names, or calculate sidereal or Vedic charts. Use for Swiss Ephemeris tropical chart calculations only.

The NatalChart.AI API computes astrology charts from birth data using the Swiss Ephemeris and returns the results as JSON, with tropical zodiac, Placidus houses, and the five major aspects. Beyond the natal chart it calculates transits over a window of up to 92 days, synastry between two people, solar return charts, day-by-day timing scores for an activity, and relocation scores that rank major cities for one chart. Responses contain calculated positions and scores only, with no generated text and no AI calls, and the spec states that request bodies are never stored.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

32%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

49%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the NatalChart.AI API to your agent

Capabilities

Start building with NatalChart.AI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

NatalChart.AI API

Jentic AI Readiness Score

NatalChart.AI API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness