canonical: https://jentic.com/apis/bodygraphchart.com/bodygraphchart # Bodygraphchart Bodygraph API The Bodygraph API turns a person's birth date, time, and location into structured chart data for Human Design and astrology. An agent generates a single Human Design chart (the bodygraph), relationship data for two people, and astrology chart data, then uses the response to build a chart in an app or site. A locations operation returns places with their timezones so the birth time is resolved accurately before the chart is computed. ## For AI agents Generate Human Design and astrology chart data from birth details: a single bodygraph, relationship data for two people, astrology data, and a locations-with-timezones lookup. ## Scope Does not provide written interpretations, store user accounts, or render chart images. Use for Human Design and astrology chart data generation only. ## Capabilities - Generate Human Design chart data (the bodygraph) from birth date, time, and location - Generate Human Design relationship data for two people - Generate astrology chart data from birth details - Look up locations with their timezones for accurate birth-time resolution ## Use cases ### Agent-generated charts An AI agent builds a Human Design or astrology chart on demand. Through Jentic the agent resolves the birth place to a timezone, then calls the chart operation with the birth date, time, and location and reads back structured chart data to render. This lets an app offer charts without implementing the ephemeris math itself. Example prompt: Resolve a birth location to a timezone, then generate the Human Design chart data for the birth date and time ### Relationship charts A product compares two people's charts. The HD-relationship-data operation returns Human Design relationship data for two sets of birth details, so an agent can produce a compatibility-style chart from the same inputs it uses for single charts. The response is structured data an app renders into a relationship view. Example prompt: Generate Human Design relationship data for two people from their birth dates, times, and locations ### Accurate birth-time resolution Charts are only correct when the birth time is in the right timezone. The locations operation returns places with their timezones, so an agent resolves the birth city to a timezone before computing a chart and avoids an off-by-hours error. This matters most for births near a timezone boundary or a daylight-saving change. Example prompt: Look up a birth city in the locations list, read its timezone, and use it when generating the chart ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v221006/hd-data` | Generate HD Data (Traditional Single Chart) | | GET | `/v221006/hd-relationship-data` | Generate HD Relationship Data | | GET | `/v240815/astro-data` | Generate Astrology Data | | GET | `/v210502/locations` | Returns a list of locations with their timezones | ## Key resources - **HD data** — Generate a single Human Design chart (bodygraph) from birth details - **HD relationship data** — Generate Human Design relationship data for two people - **Astro data** — Generate astrology chart data from birth details - **Locations** — List locations with their timezones for accurate birth-time resolution ## 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:** 36 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 61 / 100 - Developer Experience & Jentic Compatibility: 67 / 100 - AI-Readiness & Agent Experience: 23 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 72 / 100 - **View full report:** https://jentic.com/apis/bodygraphchart.com/bodygraphchart/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 Bodygraph API by hand means handling its api_key query-parameter auth, its versioned endpoint paths, and the locations lookup that gives you a timezone before you can compute an accurate chart. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The Bodygraph API carries birth details in the request, not the URL path, so there is no per-resource id to pin. You choose which of its operations your agent may call: it can generate single-person chart data without the relationship-data operation unless you add it. - **Credential handling:** Your Bodygraph api_key is held 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 'generate a Human Design chart' or 'generate astrology data', and Jentic returns the matching Bodygraph operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **AstroFabric** — Generates Human Design and astrology chart data - **AstronomyAPI** — Computes raw astronomical positions and ephemeris data - **Free Horoscope API** — Returns horoscope and astrology data ## FAQ ### What authentication does the Bodygraph API use? The Bodygraph API authenticates with an API key passed as the api_key query parameter per its OpenAPI spec. Through Jentic the key is injected at call time by your own Jentic One instance, so it never enters the agent's prompt or logs. ### Can I generate a Human Design chart with the Bodygraph API? Yes. The HD-data operation returns Human Design chart data (the bodygraph) from a person's birth date, time, and location, and the HD-relationship-data operation returns relationship data for two people. The astro-data operation generates astrology chart data from the same kind of birth details. ### What are the rate limits for the Bodygraph API? The OpenAPI spec does not specify rate limits. Check the provider's documentation at https://bodygraphchart.com for current limits and plan tiers before generating charts at volume. ### Why does the Bodygraph API need a location and timezone? Human Design and astrology charts depend on the exact local time of birth, so the locations operation returns places with their timezones. Resolve the birth place to a timezone first, then pass accurate birth details to the chart operations. ### Is there a Bodygraph MCP server? You don't need an MCP server to give your agent the Bodygraph API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls it, so you skip installing and syncing a separate server. ### Can I limit what my agent is allowed to do with the Bodygraph API? Yes. Write a rule that allows only the chart-generation operations, such as HD-data and astro-data, so your agent can produce chart data but you leave out any operation it does not need. Every call it makes is logged. ### How do I generate a Human Design chart with the Bodygraph API through Jentic? Search Jentic for 'generate a Human Design chart' and it returns the HD-data operation with its input schema; the agent passes birth date, time, and location and reads back the bodygraph data. To run it on your own infrastructure, install Jentic One from its GitHub repo.