Why This API Works Well with AI
- Consistent structure — every response has the same envelope (
success,errorCode,data) - Machine-readable errors — agents can branch on
errorCodewithout parsing text - camelCase fields — no special casing surprises for JSON parsers
- OpenAPI spec — import directly into tool-building frameworks
- Deterministic — same birth data always produces the same chart
llms.txt
This documentation site serves an auto-generatedllms.txt file:
llms-full.txt with the complete documentation content is also available at /llms-full.txt.
OpenAI Function Calling
Define the API as a tool in the OpenAI function calling format:Claude Tool Use
Define as an Anthropic tool:Coordinates Endpoint for Agents
If your agent already has latitude and longitude (e.g., from a prior geocoding step), use the coordinates endpoint to skip the geocoding key entirely:ChartResult without requiring an HD-Geocode-Key header.
No-Code Platforms (Zapier, Make, n8n)
Use an HTTP request module with these settings:| Setting | Value |
|---|---|
| Method | POST |
| URL | https://api.humandesignapi.nl/v2/charts/simple |
| Headers | Authorization: Bearer YOUR_API_KEY, HD-Geocode-Key: YOUR_GEOCODE_KEY, Content-Type: application/json |
| Body | {"birthdate": "YYYY-MM-DD", "birthtime": "HH:MM", "location": "City, Country"} |
data from the response for the chart result.
Recommended Endpoints for Agents
| Use Case | Endpoint | Why |
|---|---|---|
| Quick personality summary | POST /v2/charts/simple | Smaller response, all plan tiers |
| Full chart reading | POST /v2/charts | All properties, advanced tier |
| Agent with geocoding | POST /v2/charts/coordinates | No geocode key needed |
Error Handling for Agents
Always checksuccess and branch on errorCode:

