Install Jentic One Beta

Connect the Human Design Hub Pro API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Human Design Hub Pro 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%2Fhumandesignhub.app%2Fhumandesignhub" | 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%2Fhumandesignhub.app%2Fhumandesignhub" | 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 Human Design Hub Pro API.

Calculate a complete Human Design bodygraph from one birth datetime, with planetary ephemeris data when verbose is true

Resolve an offset-free local birth time and IANA timezone into the ISO 8601 datetime the chart endpoints expect

Search GeoNames city candidates for a birthplace and get coordinates plus the IANA timezone

Compare two people with a composite compatibility chart, or analyse a group of 3 to 5 with a Penta chart

GET STARTED

Start building with Human Design Hub Pro API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Human Design Hub Pro API for, with concrete tasks.

★ Chart readings from a chat agent through Jentic

A developer's assistant takes a user's birth date, time, and city in conversation and returns their Human Design chart. Through Jentic the agent finds the location search, timezone resolve, and bodygraph operations by intent and chains them; the X-API-KEY credential is injected by the developer's own Jentic One instance, so the agent only ever handles the birth data.

Call GET /v2/locations/search with query Porto to get the IANA timezone, POST /v2/timezone/resolve with that timezone, date 1990-05-12, and time 14:30, then POST /v2/bodygraph with the returned datetime

Relationship and team compatibility

Coaches and relationship apps compare people's designs. The composite endpoint takes two people, a and b, each with a birth datetime, and returns the combined chart; the Penta endpoint takes 3 to 5 members and returns the group analysis, with Chiron kept in raw positions but not activating Gates or Channels.

Call POST /v2/composite with a.datetime 1988-03-04T09:15+01:00 and b.datetime 1991-11-20T22:40+01:00, then summarise the channels the composite defines

Transit forecasts and alerts

Send users a heads-up when a transit touches their design. The transit-overlay-window call combines a natal chart with transit positions across a rolling window, and next-gate-transitions lists upcoming planetary Gate changes, so an app can schedule notices for the coming week.

Call POST /v2/transit-overlay-window with the user's birth_datetime, base_datetime set to today, and window_days 7, and list the transit events in that window

Chart images for reports

Generate bodygraph and transit chart images for PDFs, emails, or a web profile. The image endpoints return PNG by default or SVG when the format field is svg, accept width and height, and require the Standard plan or higher.

Call POST /v2/prompt/bodygraph-image with datetime 1990-05-12T14:30+09:00 and format svg, and attach the returned SVG to the client's report

Key Endpoints

19 endpoints — the human design hub pro api calculates human design charts from a birth datetime given in iso 8601 with a utc offset.

METHOD

PATH

DESCRIPTION

POST

/v2/bodygraph

Calculate a bodygraph chart

POST

/v2/timezone/resolve

Resolve a local birth time to an offset datetime

GET

/v2/locations/search

Search birth locations

POST

/v2/composite

Calculate a composite compatibility chart

POST

/v2/group/penta

Calculate a group Penta analysis

POST

/v2/transit-overlay

Overlay transits on a natal chart

POST

/v2/next-gate-transitions

Calculate upcoming Gate transitions

POST

/v2/prompt/bodygraph-image

Generate a bodygraph chart image

POST

/v2/bodygraph

Calculate a bodygraph chart

POST

/v2/timezone/resolve

Resolve a local birth time to an offset datetime

GET

/v2/locations/search

Search birth locations

POST

/v2/composite

Calculate a composite compatibility chart

POST

/v2/group/penta

Calculate a group Penta analysis

POST

/v2/transit-overlay

Overlay transits on a natal chart

POST

/v2/next-gate-transitions

Calculate upcoming Gate transitions

POST

/v2/prompt/bodygraph-image

Generate a bodygraph chart image

Why Jentic?

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

Setup

Wiring the Human Design Hub Pro API by hand means sending the `X-API-KEY` header, converting each local birth time to an ISO 8601 datetime with the right UTC offset, and knowing which image calls your plan allows. Through Jentic you install once, import Human Design Hub from the API Directory, store the key once, and your agent calls it.

Permission scoping

Human Design Hub carries the birth data inside the request body, so rules bound which operations your agent may call, not whose chart. You choose the operations it may call, so plan-gated image renders and group Penta analysis are not included unless you add them.

Credential isolation

Your Human Design Hub 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 'calculate a bodygraph' or 'resolve a birth timezone', and Jentic returns the matching Human Design Hub operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Human Design Hub Pro API through Jentic.

What authentication does the Human Design Hub Pro API use?

Per its OpenAPI spec, the Human Design Hub Pro API uses an API key sent in the `X-API-KEY` request header. Through Jentic the key is stored encrypted by your own Jentic One instance and added to the call at execution time, so your agent never holds it.

What datetime format do the chart endpoints expect?

The chart calls take an ISO 8601 datetime with a UTC offset, for example 1990-01-01T12:34+09:00. If you only have a local birth date and time, call POST /v2/timezone/resolve with the IANA timezone ID and the local date and time, and it returns the offset datetime to pass on. GET /v2/locations/search finds the timezone for a birthplace.

Which Human Design Hub endpoints need a higher plan?

The spec marks the three image endpoints, bodygraph-image, transit-image, and transit-overlay-image under /v2/prompt, as requiring the Standard plan or higher. The spec itself is described as tier-filtered, so check your plan before relying on an operation.

What are the rate limits for the Human Design Hub Pro API?

The OpenAPI spec does not specify rate limits. Check the Human Design Hub documentation at https://api.humandesignhub.app for current limits on your plan.

How do I calculate a bodygraph with the Human Design Hub API through Jentic?

Search Jentic for 'calculate a Human Design bodygraph' to get POST /v2/bodygraph, then send the birth datetime with its UTC offset, adding verbose true if you want planetary ephemeris data. To run it on your own infrastructure, install Jentic One from its GitHub repo and store your X-API-KEY once.

Is there a Human Design Hub MCP server?

You don't need an MCP server to give your agent Human Design Hub. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the chart operations you allow, discovered on demand instead of loaded into its context.

Can I limit what my agent is allowed to do with the Human Design Hub Pro API?

Yes. For example, allow only GET /v2/locations/search, POST /v2/timezone/resolve, and POST /v2/bodygraph, so the agent can produce a basic chart but cannot run the plan-gated image renders or group Penta calls. Every call it makes is logged by your Jentic One instance.

Humandesignhub App Human Design Hub Pro API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey19 EndpointsREST

For Agents

Calculate Human Design bodygraphs, transits, composites, and Penta group charts from birth datetimes, resolve birth locations and timezones, and render chart images as PNG or SVG.

Use for: Calculate my Human Design bodygraph for 1990-05-12 14:30 in Seoul, Find the timezone for someone born in Porto, Get a composite chart for two partners, Run a Penta analysis for a four-person team

Not supported: Does not store user profiles, write chart interpretations, or calculate Western astrology houses or horoscopes. Use for computing Human Design chart data and chart images from birth datetimes only.

The Human Design Hub Pro API calculates Human Design charts from a birth datetime given in ISO 8601 with a UTC offset. It returns full or lightweight bodygraphs, circuit breakdowns, Not-Self Gates and the Not-Self Deck, life-cycle events, DreamRave sleep charts, two-person composite charts, and Penta analysis for groups of 3 to 5 people. Transit endpoints compute the chart for any moment, overlay transits on a natal chart, list upcoming planetary Gate transitions, and scan a rolling window of up to 90 days. Supporting calls search GeoNames birth locations and resolve a local birth time plus IANA timezone into the offset datetime the chart calls expect, and image endpoints render bodygraph and transit charts as PNG or SVG.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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).

25%

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: B-Signals: 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: DSignals: 4

32%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

56%

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: C-Signals: 1

50%

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: ASignals: 1

83%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Human Design Hub Pro API to your agent

Capabilities

Start building with Human Design Hub Pro API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Humandesignhub App Human Design Hub Pro API

Jentic AI Readiness Score

Human Design Hub Pro 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