---
title: "Intelligence Status"
method: GET
path: "/api/intelligence/status"
tags: ["Intelligence API"]
---

# Intelligence Status

`GET /api/intelligence/status`

## Request

- Base URL: `https://api.xfinlab.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.xfinlab.com/api/intelligence/status`
- Auth: none declared

Public, unauthenticated -- lets a prospective developer check what's
live before they even have a key, same pattern as
GET /api/agent-debate/status.

2026-08-17 (task #4 follow-up, "重有咩可以升級" -- upgrade #4, live status
widget): extended from the original 3 keys (events/sentiment/debate) to
cover all 7 public endpoints. Only sentiment and debate have a genuine
binary gate here -- their route handlers explicitly raise 503 if
finbert_available()/debate_available() is false (see intelligence_
sentiment/intelligence_debate above). The other 5 (events, intel,
technical, stress_test, regime_signal) never 503 by design -- on an
upstream hiccup they soft-fail to 200 with an `error` field or null
sub-fields instead (see the schema docs on intelligence-api.html). So
`True` here means "not gated behind an external reachability check",
not a claimed uptime guarantee -- deliberately not fabricating a
monitoring signal that doesn't exist for endpoints that don't have one.

## Response `200`

Successful Response

- unknown

---

[API](https://skmtc.dev/xfinlab/apis/xfinlab-api.md) · [All operations](https://skmtc.dev/xfinlab/apis/xfinlab-api/llms.txt) · [OpenAPI document](https://skmtc.dev/xfinlab/apis/xfinlab-api/revisions/205f85614bc6?raw)