Workspace
Demo workspace: sample data stored in this browser. Sections marked “Needs integration” are not active.
Developers
API keys and MCP are realAPI keys
Real keys for the Kinetic MCP server. A key acts on your account and spends your credits. Only a short prefix is stored for display; the full key is shown once.
API usage statistics
Usage stats need request logging that is not enabled. Credit spend is tracked in the ledger, but it is not attributed per API key, so no real per-key count can be shown.
Sample chart: requests per day
Demo dataRequest logs
Request logging is not enabled, so there are no real logs to show. The table below only illustrates the layout.
| Time | Request | Status | Latency |
|---|---|---|---|
| POST /api/mcp tools/call generate_image | 200 | 1840 ms | |
| POST /api/mcp tools/list | 200 | 38 ms | |
| POST /api/mcp tools/call generate_video | 402 | 52 ms | |
| POST /api/mcp tools/call search_community | 200 | 91 ms | |
| POST /api/mcp tools/call generate_image | 429 | 12 ms |
Documentation & developer resources
Links go only to things that exist.
- MCP setup (Connect page)
- README on GitHub (opens in a new tab)
- /api/mcp JSON-RPC description (opens in a new tab)
curl quickstart
Lists the MCP tools (this call needs no key). Use kn_YOUR_KEY as a placeholder: tools/call needs a real key from the API keys section.
curl -s https://<your-host>/api/mcp \
-H "Authorization: Bearer kn_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'There is no separate API reference site. The README and the Connect page are the documentation. Open Connect