canonical: https://jentic.com/apis/humandesignhub.app/humandesignhub # Humandesignhub App Human Design Hub Pro API 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. ## For AI 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. ## Scope 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. ## Capabilities - 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 - Compute transits for any moment, overlay them on a natal chart, and scan a rolling window of up to 90 days - List upcoming planetary Gate transitions from a given datetime - Render a bodygraph, transit, or transit-overlay chart image as PNG or SVG ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Bodygraph charts** — Full and simple bodygraphs, circuits, Not-Self Gates, Not-Self Deck, cycle analysis, and DreamRave charts - **Relationship charts** — Two-person composite and 3 to 5 person Penta analysis - **Transits** — Transit charts, natal overlays, rolling windows, and upcoming Gate transitions - **Locations and timezones** — GeoNames birthplace search and local-time to offset datetime resolution - **Chart images** — Bodygraph, transit, and overlay renders in PNG or SVG ## AI readiness 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. - **Score:** 64 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 81 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 47 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 83 / 100 - **View full report:** https://jentic.com/apis/humandesignhub.app/humandesignhub/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Astronomy API** — Positions of celestial bodies and astronomical events - **Free Horoscope & Tarot API** — Daily horoscopes and tarot readings by zodiac sign - **OpenAI API** — Language models for turning chart data into written readings ## FAQ ### 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.