ReflexioDeveloper Docs
Menu
Local OSS

reflexio doctor / reflexio api

Run setup diagnostics and make raw HTTP calls to any Reflexio endpoint.

Two low-level tools for debugging and development:

  • doctor check — automated setup diagnostics (env file, API key, server reachability, Python version).
  • api call — make a raw HTTP request to any Reflexio endpoint, with automatic Bearer-token auth.

reflexio doctor check

doctor is oriented toward Local OSS. Its failure hints point at reflexio services start, local ports, and local .env files.

Run diagnostic checks on your Reflexio configuration and connectivity. Useful as a first step when something isn't working.

reflexio doctor check

Checks performed

CheckWhat it verifies
env_fileA .env file exists at ~/.reflexio/.env. Warning only — the CLI can still work with env variables set in the shell.
api_keyREFLEXIO_API_KEY is resolved from env, .env, or --api-key. Warning if missing.
server_healthGET {REFLEXIO_URL}/health returns 200. Failure if the server is unreachable or unhealthy.
python_versionPython ≥ 3.12 (recommended). Warning if older.

Exits with code 1 if any check reports fail. Warnings (missing env file, older Python) are non-fatal.

reflexio doctor check
reflexio --json doctor check  # structured output for CI

reflexio api call

Raw HTTP client for Reflexio endpoints. Handles Bearer-token auth and JSON serialization so you can test new endpoints without writing a full script.

reflexio api call <METHOD> <PATH> [--data '<json>']

Prop

Type

Enterprise readiness

On enterprise servers, GET /health reports cached required dependency readiness and returns HTTP 503 while a required check is pending, failed, or stale. GET /healthz checks process liveness. Standalone OSS health behavior is unchanged.

Use reflexio api call GET /api/readiness with your API key and normal project context to inspect your organization/project. The response includes safe check statuses, reasons, and check timestamps. Platform tenant failures are isolated from other tenants after startup; new managed tasks wait for initial tenant checks to pass before their first healthy response. Self-host tenant compatibility contributes to global health. Vector operations require qualification; lexical search remains available. Cloud inference execution is reported as not_checked to avoid billable probes. Runtime corpus checks inspect bounded subsets of up to 100 rows per vector column/project and aggregation table/route. Their successful reason is sampled_vector_contract: this can miss problems outside the sample and cannot establish historical encoder provenance. Full validation belongs to explicit maintenance, such as embedding-model conversion or restoring data.

Examples

# Health check
reflexio api call GET /health

# List agent playbooks with a filter
reflexio api call POST /api/get_agent_playbooks --data '{"limit": 5}'

# Load a larger payload from disk
reflexio api call POST /api/publish_interaction --data @payload.json

# Structured output for piping to jq
reflexio --json api call POST /api/search_profiles \
  --data '{"user_id":"user_123","query":"travel"}' \
| jq '.data[0]'

api call sends the same Authorization: Bearer header as every other CLI command, derived from REFLEXIO_API_KEY or --api-key. You do not need to add auth headers manually.