API functions
One page per function, generated from convex/lib/mcpRegistry.ts — the same table the endpoints
dispatch from. Each page opens with the REST path you call, then the scope it needs, whether a
free sandbox key can call it, what it takes, and an example request in both forms.
| Functions | 78 across 19 groups, 80 registry entries |
| REST paths | 80 under https://api.selda.ai/v1/… |
| RPC form | the same calls at POST /mcp/query · /mcp/mutate · /mcp/run · /mcp/material/upload |
| Authentication | Authorization: Bearer sk_live_… — the organisation is resolved from the key |
| Sandbox keys | sk_test_… reach every read and write that costs nothing to run |
| Sending | not here. No key of any kind can send a message; approval happens in the app |
| Machine-readable | openapi.json · llms-full.txt |
The badge on each sidebar entry is the RPC endpoint the call is dispatched on: query reads,
mutate writes, run starts slow work, upload takes raw bytes. It is not the HTTP method,
which is on the page itself and in REST paths. Badging these POST would be
the same word on almost every row.