Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Asterwise 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%2Fasterwise.com%2Fasterwise" | shStep 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%2Fasterwise.com%2Fasterwise" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Asterwise API.
Generate Vedic sidereal and Western tropical natal charts from birth date, time, and place
Compute Vimshottari and Yogini dasha timelines and planetary transits for a chart
Score relationship compatibility with Kundali Milan, Dashakoot, and numerology matching
Return daily, weekly, monthly, and yearly horoscopes by moon sign or sun sign
GET STARTED
Build numerology profiles including life path, expression, and personal-year numbers
Draw tarot spreads and look up crystal, dream-symbol, and nakshatra reference data
Patterns agents use Asterwise API for, with concrete tasks.
★ AI Agent Astrology Integration via Jentic
An AI agent that answers astrology, numerology, or divination questions can call Asterwise through Jentic without wiring the bearer key or reading the reference docs. The agent searches by intent, receives the matching operation schema, and submits birth or date inputs to get a structured reading back. This suits horoscope assistants, matchmaking bots, and spiritual-content tools that need accurate calculations rather than generated prose.
Search Jentic for 'generate a natal chart', load the operation schema, and call it with a birth date, time, and location to receive the chart as structured JSON
Natal Chart Generation
Produce a complete birth chart from a date, time, and place of birth. Asterwise returns a Vedic sidereal Janam Kundali or a Western tropical chart with planetary positions, houses, and aspects, and can extend to divisional charts, dashas, and transits for deeper reading. Useful for astrology apps that render a chart and interpret it.
Call POST /v1/astro/natal with a birth date, time, and place to read back the planetary positions and houses
Relationship Compatibility Matching
Score how two people match using Vedic Kundali Milan, Dashakoot, Papasamyam, and Porutham methods, or numerology compatibility. Asterwise takes two sets of birth details and returns a numeric compatibility result with the contributing factors, which a matchmaking product can present directly to users.
Call POST /v1/astro/matchmaking with two sets of birth details to get a Kundali Milan compatibility score
Daily Horoscope Delivery
Serve daily, weekly, monthly, and yearly horoscopes keyed by moon sign for Vedic readings or sun sign for Western readings. A content agent can fetch the reading for a sign and publish or summarise it, with the same shape across every cadence so one integration covers all four.
Call GET /v1/horoscope/daily/{moon_sign} for the Taurus sign to retrieve today's reading
122 endpoints — the asterwise api calculates vedic sidereal and western tropical astrology, numerology, tarot, and panchanga results from birth and date inputs, returning them as structured json.
METHOD
PATH
DESCRIPTION
/v1/astro/natal
Generate a Vedic natal chart (Janam Kundali)
/v1/western/natal
Generate a Western tropical natal chart
/v1/numerology/profile
Generate a numerology profile
/v1/astro/matchmaking
Kundali Milan compatibility matching
/v1/horoscope/daily/{moon_sign}
Daily horoscope by moon sign
/v1/tarot/draw
Draw tarot cards
/v1/crystals
List the crystal reference database
/v1/astro/panchanga
Daily Panchanga almanac
/v1/astro/natal
Generate a Vedic natal chart (Janam Kundali)
/v1/western/natal
Generate a Western tropical natal chart
/v1/numerology/profile
Generate a numerology profile
/v1/astro/matchmaking
Kundali Milan compatibility matching
/v1/horoscope/daily/{moon_sign}
Daily horoscope by moon sign
/v1/tarot/draw
Draw tarot cards
/v1/crystals
List the crystal reference database
/v1/astro/panchanga
Daily Panchanga almanac
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Asterwise API by hand means managing its bearer API key, posting birth and date inputs to the right chart, numerology, or tarot endpoint, and parsing the HMAC-signed JSON responses yourself. Through Jentic you install once, import Asterwise from the API Directory, store the key once, and your agent calls it.
Permission scoping
Asterwise carries no account or resource id in its paths; its endpoints just compute and return a reading. A rule bounds your agent to the operations it needs, such as natal-chart generation, horoscopes, and numerology, so it can run those and nothing else.
Credential isolation
Your Asterwise API 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 'generate a natal chart' or 'get today's horoscope', and Jentic returns the matching Asterwise operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Asterwise API through Jentic.
Is there an Asterwise MCP server?
You don't need a separate MCP server to give your agent the Asterwise API. Jentic connects it directly from the API Directory: import it, store your bearer key once, and your agent calls the chart, horoscope, numerology, and tarot operations it needs.
Can I limit what my agent is allowed to do with the Asterwise API?
Yes. Because every Asterwise endpoint only computes and returns a reading, you write a rule that allows just the operations your agent needs, such as natal-chart generation and daily horoscopes, so it can call those and touch nothing else. Every call it makes is logged by your self-hosted instance.
What authentication does the Asterwise API use?
The Asterwise API authenticates with a bearer API key sent in the Authorization header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.
Can I generate both Vedic and Western charts with the Asterwise API?
Yes. One operation returns a Vedic sidereal Janam Kundali and a separate operation returns a Western tropical chart, each from a birth date, time, and location. The API also covers divisional charts, dashas, transits, and matchmaking.
What are the rate limits for the Asterwise API?
The OpenAPI spec does not specify rate limits. Check the vendor's documentation at https://asterwise.com for current limits and plan tiers.
How do I generate a natal chart with the Asterwise API through Jentic?
Search Jentic for 'generate a natal chart' and it returns the Asterwise natal operation with its input schema; supply a birth date, time, and location and the agent receives the chart as structured JSON. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Generate Vedic and Western birth charts, numerology profiles, horoscopes, tarot draws, and panchanga timing from birth and date inputs. Returns every reading as structured JSON over a bearer-authenticated REST API.
Use for: I want to generate a Vedic natal chart from a birth date, time, and city, Calculate the Western tropical chart for a given birthday, Check the compatibility between two people using Kundali Milan, Get today's horoscope for the Aries moon sign
Not supported: Does not place product orders, process payments, or run live astrologer chat. Use for astrology, numerology, and divination calculations only.
The Asterwise API calculates Vedic sidereal and Western tropical astrology, numerology, tarot, and panchanga results from birth and date inputs, returning them as structured JSON. It generates natal and divisional charts, dasha timelines, planetary transits, and relationship-compatibility scores, and serves reference data for crystals, dream symbols, nakshatras, and tarot cards. Horoscope endpoints cover daily, weekly, monthly, and yearly readings by moon sign and sun sign.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>