Documentation
API reference, verification checklist, and status definitions for the Vincent Status Dashboard.
What This Is
- ✓Public observability dashboard for Vincent infrastructure
- ✓Read-only status API safe to browse and integrate
- ✓Authenticated control plane for privileged operations
- ✓Delayed market data snapshots (not real-time)
What This Is NOT
- ✗NOT an official Lit Protocol product
- ✗NOT a custodial wallet or key management service
- ✗NOT financial advice or a trading platform
- ✗NOT guaranteed to be always available
Vincent "unconfigured": If Vincent shows as "unconfigured", this means SDK/PKP credentials are not set up on this instance. This is not a failure state - the dashboard simply needs to be configured with valid credentials to connect to Vincent. See Trust & Security for details.
60-Second Verification Checklist
Run these checks to confirm the system is operational.
| Check | Test | Expected |
|---|---|---|
| Status API responds | /api/v1/status | {"ok":true,...} |
| Health API responds | /api/v1/health | {"ok":true,"data":{"overall":...}} |
| Lit network reachable | /api/v1/health/lit | rpcStatus.status = "healthy" |
| Chain RPCs responding | /api/v1/health/chain | yellowstone.status = "healthy" |
| Dashboard loads | /dashboard | Page renders without errors |
Quick test: Run this command to verify the API is responding:
curl -s https://lit-with-intent.web.app/api/v1/status | jq .okAPI Endpoints
All responses use the format: { ok, data, error, request_id, ts }
PUBLICRead-Only Endpoints
| Method | Path | Description |
|---|---|---|
| GET | /api/v1/status | Overall system status summary |
| GET | /api/v1/health | Detailed health snapshot for all components |
| GET | /api/v1/health/lit | Lit network node connectivity status |
| GET | /api/v1/health/vincent | Vincent SDK and dashboard status |
| GET | /api/v1/health/chain | Yellowstone and Base RPC health |
| GET | /api/v1/executions | Recent execution history (limit=25 default) |
PRIVILEGEDAuthenticated Endpoints
Requires X-API-Key header. Rate limited. Audit logged with request_id.
| Method | Path | Description |
|---|---|---|
| POST | /api/v1/health/run | Trigger fresh health check (stores to Firestore) |
| POST | /api/v1/vincent/setup | Bootstrap PKP and Vincent environment |
| POST | /api/v1/vincent/send | Execute token transfer with policy enforcement |
Curl Examples
/api/v1/statuscurl -s https://lit-with-intent.web.app/api/v1/status | jq .
/api/v1/healthcurl -s https://lit-with-intent.web.app/api/v1/health | jq .
/api/v1/health/litcurl -s https://lit-with-intent.web.app/api/v1/health/lit | jq .
/api/v1/health/vincentcurl -s https://lit-with-intent.web.app/api/v1/health/vincent | jq .
/api/v1/health/chaincurl -s https://lit-with-intent.web.app/api/v1/health/chain | jq .
/api/v1/executionscurl -s "https://lit-with-intent.web.app/api/v1/executions?limit=10" | jq .
/api/v1/health/run(auth required)curl -X POST -H "X-API-Key: YOUR_KEY" https://lit-with-intent.web.app/api/v1/health/run
/api/v1/vincent/setup(auth required)curl -X POST -H "X-API-Key: YOUR_KEY" -H "Content-Type: application/json" https://lit-with-intent.web.app/api/v1/vincent/setup
/api/v1/vincent/send(auth required)curl -X POST -H "X-API-Key: YOUR_KEY" -H "Content-Type: application/json" -H "Idempotency-Key: unique-id" -d '{"to":"0x...","amount":"0.01"}' https://lit-with-intent.web.app/api/v1/vincent/sendStatus Definitions
All health checks return one of these status values.
Component is operating normally. All checks pass.
Component is partially working or experiencing issues. May still function but with limitations.
Component is down or failing. Cannot perform its function.
Component requires configuration (credentials, keys, etc.). Not a failure - just needs setup.
Cannot determine status. May be unreachable or check not implemented.
Response Format
All API responses follow this structure:
{
"ok": true, // boolean - request succeeded
"data": { ... }, // response payload (on success)
"error": "...", // error message (on failure)
"request_id": "abc-123", // correlation ID for debugging
"ts": "2026-01-22T..." // ISO timestamp
}