Health & Status
Responses
200
Service is healthy
application/json
statusstring · enumRequiredPossible values:
Service health status
servicestringRequiredExample:
Service identifier
enterprise-inference-workerregionstringRequiredExample:
Deployment region
eu-westprivacystringRequiredExample:
Privacy compliance status
zero-data-retentionauthenticationstringRequiredExample:
Authentication requirement
enterprise-onlytimestampnumber · doubleRequired
Unix timestamp
get
/health200
Service is healthy
Authorizations
AuthorizationstringRequired
Primary authentication method - Required for all endpoints except /health.
Three Authentication Methods:
1. OAuth 2.0 Client Credentials (Recommended)
Get token:
curl -X POST https://enterprise.bitmind.ai/v1/oauth/token \
-d "grant_type=client_credentials" \
-d "client_id=YOUR_ID" \
-d "client_secret=YOUR_SECRET"
Use token:
Authorization: Bearer eyJhbGciOiJSUzI1NiJ9...
- Token lifetime: 1 hour
- Fast local JWT verification (<1ms)
- Recommended for all M2M integrations
2. OAuth + mTLS (High Security)
Get token (certificate replaces secret):
curl -X POST https://enterprise.bitmind.ai/v1/oauth/token \
-H "X-Client-Cert: $(base64 -w 0 client.crt)" \
-d "grant_type=client_credentials" \
-d "client_id=YOUR_ID"
Use token + certificate:
Authorization: Bearer eyJhbGc...
X-Client-Cert: LS0tLS1CRUdJTi...
- Certificate authenticates token request (no client_secret)
- Certificate also required on all API calls
- Required for government/healthcare/financial clients
- Complies with RFC 8705
3. Organization API Key (Legacy)
Authorization: Bearer enterprise-YOUR_API_KEY
- Long-lived until revoked
- No token refresh needed
- Simple but less secure than OAuth
Responses
200
Service status and client information
application/json
statusstring · enumRequiredPossible values:
servicestringRequired
regionstringRequired
timestampnumber · doubleRequired
401
Unauthorized - Invalid or missing authentication
application/json
get
/statusLast updated