AI Discovery endpoints return 404 (ai-manifest.json, tools.json, context.json, workflows.json)

[alien8d]

Summary

The AI discovery endpoints documented in the SDK types all return 404:

curl -s https://api.cerebe.ai/.well-known/ai-manifest.json -H "X-API-Key: $CEREBE_API_KEY"  # 404
curl -s https://api.cerebe.ai/ai/tools.json -H "X-API-Key: $CEREBE_API_KEY"                 # 404
curl -s https://api.cerebe.ai/ai/context.json -H "X-API-Key: $CEREBE_API_KEY"               # 404
curl -s https://api.cerebe.ai/ai/workflows.json -H "X-API-Key: $CEREBE_API_KEY"             # 404

These endpoint types exist in the generated SDK types (types.gen.ts) but the routes are not deployed.

Priority

Low — these are supplementary discovery endpoints, not core functionality.

[alien8d]

Investigated — the AI discovery routes (/.well-known/ai-manifest.json, /ai/tools.json, /ai/context.json, /ai/workflows.json) are correctly registered in main.py at root level (no prefix).

The 404s are likely caused by the ingress/reverse proxy not forwarding requests to these root-level paths. This is an infrastructure issue — the Kubernetes ingress rules may only forward /api/* paths to the backend pod.

Action needed: Update the ingress configuration to also forward /.well-known/* and /ai/* to the backend service.