Service
Lavoval
A minimal public gateway for health, readiness, and versioned application routes. Built for operators, integrations, and quick verification.
Service
Lavoval
Environment
production
Health Endpoint
Checking…
API V1
v1
Use /healthz for effective runtime configuration flags, /readyz for readiness,
/livez for heartbeat checks, and /api/v1/* for the versioned application surface.
GET /livez
Simple heartbeat for liveness probes.
GET /healthz
Safe runtime flags for env and provider health.
GET /readyz
Readiness signal for traffic acceptance.
{
"api": {
"base": "/api/v1",
"namespaces": [
"/api/v1/auth",
"/api/v1/skills",
"/api/v1/me",
"/api/v1/runtime",
"/api/v1/admin"
]
},
"env": "production",
"routes": {
"healthz": "/healthz",
"livez": "/livez",
"readyz": "/readyz"
},
"service": "Lavoval"
}
Registration, login, OAuth start and complete flows, email verification, password reset, and MFA enrollment and sign-in completion.
Public catalog listing and skill detail routes for published marketplace offers.
Authenticated profile, security settings, and creator-owned skill management.
Skill execution endpoints for starting runs and inspecting run history.
Governance, moderation, mail operations, runtime oversight, and internal operational tooling.
Start with the health surfaces, then move into the versioned API. For authenticated routes, send a bearer token after completing the auth flow under /api/v1/auth.
curl https://api.lavoval.com/healthz
curl https://api.lavoval.com/api/v1/skills
curl https://api.lavoval.com/api/v1/me \
-H "Authorization: Bearer <access-token>"