Use the API key generated in the console for the current environment. Keys start with dg_live_, belong to a team and currently authorize one project.Data endpoints do not use login JWTs, x-team-id or x-project-id. API and MCP use the same key and project authorization. Keep real keys out of public code examples and logs.| Environment | Public API Base URL |
|---|
| Production | https://api.dageno.ai/llm-data-service/api/v1/llm-data/public |
| Development | https://test-api.dageno.ai/llm-data-service/api/v1/llm-data/public |
Example#
Set LLM_PUBLIC_API_KEY in your environment:Use the returned projectId with GET /projects/{projectId} to discover authorized markets, brands, filters and effective limits.Subscription entitlement#
API/MCP access must be enabled in the effective subscription entitlements (mcpEnabled=true). The subscription must be non-Free, active or canceling, and unexpired. Starter access requires explicit enablement. The backend checks this on every data request; disabling entitlement, expiry or a downgrade to Free blocks existing keys.Missing, invalid, revoked or expired keys return 401 / INVALID_API_KEY. Subscription or module restrictions return 403 / MODULE_NOT_ENABLED. Missing and unauthorized projects, responses or entity details both return 404 / NOT_FOUND.MCP#
Configure https://api.dageno.ai/llm-data-mcp/mcp with the same Authorization header. Keep the key out of tool arguments. MCP also accepts a standalone x-api-key header for compatible clients; do not send both authentication headers. Modified at 2026-11-04 09:43:00
