Sageox Health API
Service health and readiness endpoints for orchestration platforms. The `/live` endpoint returns service liveness; `/ready` confirms database connectivity and dependency availability.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/sageox-health-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: SageOx Health API
version: 1.0.0
description: '# API Reference
## Overview
SageOx is a platform that captures team knowledge from discussions, decisions, and work context into a Ledger (per-repo historical record) and Team Context (team-wide shared knowledge).'
contact:
name: SageOx Team
license:
name: MIT
servers:
- url: http://localhost:3000
description: Devcontainer
- url: https://test.sageox.ai
description: Test
- url: https://sageox.ai
description: Production
security:
- bearerAuth: []
tags:
- name: Health
description: Service health and readiness endpoints for orchestration platforms. The `/live` endpoint returns service liveness; `/ready` confirms database connectivity and dependency availability.
paths:
/live:
get:
operationId: getLiveness
summary: Liveness probe
description: Returns basic service health status to indicate the service is running
tags:
- Health
security: []
responses:
'200':
description: Service is alive
content:
application/json:
schema:
type: object
required:
- status
- timestamp
properties:
status:
type: string
enum:
- ok
example: ok
timestamp:
type: string
format: date-time
description: ISO 8601 timestamp
example: '2025-12-03T18:45:30Z'
/ready:
get:
operationId: getReadiness
summary: Readiness probe
description: Returns detailed service readiness status including dependency health checks
tags:
- Health
security: []
responses:
'200':
description: Service readiness status
content:
application/json:
schema:
type: object
required:
- ready
- timestamp
- checks
properties:
ready:
type: boolean
description: Whether the service is ready to accept traffic
example: true
timestamp:
type: string
format: date-time
description: ISO 8601 timestamp
example: '2025-12-03T18:45:30Z'
checks:
type: object
required:
- database
properties:
database:
type: string
description: Database connectivity status
enum:
- ok
- error
example: ok
'503':
description: Service is not ready
content:
application/json:
schema:
type: object
required:
- ready
- timestamp
- checks
properties:
ready:
type: boolean
example: false
timestamp:
type: string
format: date-time
example: '2025-12-03T18:45:30Z'
checks:
type: object
required:
- database
properties:
database:
type: string
enum:
- ok
- error
example: error
components:
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: 'JWT token obtained from the auth service (/api/auth/token).
Token is validated using JWKS from the auth service.
Required claims: sub (user_id), email, name, tier.
'