API access

Create and manage credentials for programmatic access to D8ly calculation and AI-assisted reading features.

API keys

HTTP API v1 requests require a bearer API key associated with your D8ly account. Keep it private and revoke or replace it if exposed.

Authentication and limits

Send the key in the Authorization header as a bearer token. The published account-wide limit is 100 requests per day; applications should handle errors and rate limits gracefully.

Authorization: Bearer <your-api-key>"model": "openai" | "gemini"

Available endpoints

POST /api/v1/bazi
POST /api/v1/daily
POST /api/v1/number-energy
POST /api/v1/tarot
POST /api/v1/compatibility
POST /api/v1/kids
POST /api/v1/face
POST /api/v1/aura
POST /api/v1/couple-face

Location can be supplied with city or latitude/longitude.

MCP without an API key

For deterministic, read-only calculations, an MCP-compatible agent can connect to https://d8ly.app/mcp. Use the authenticated HTTP API when the integration needs AI-generated readings.

Data and safety

Only submit birth or image data with the subject’s permission. MCP calculation arguments are not saved; API-generated material is for entertainment and reflection. Consult the developer guide and OpenAPI 3.1 contract before production use.