chats.get
One Selda conversation: its latest messages, the tools Selda ran, what it built on the right (artifacts) and any card waiting for the person’s press. Read only.
| REST | no path of its own, see the RPC form below |
| RPC form | POST /mcp/query with "fn": "chats.get" |
| Scope | read |
| Sandbox key | allowed |
| Extra entitlement | none |
| MCP tools | selda_get_chat |
| Internal function | chatMcp:getForKey |
A free sandbox key may call it.
Arguments
| Argument | Type | Required | Notes |
|---|---|---|---|
projectId | id<"projects"> | required | |
chatId | string | required | |
limit | number | optional |
What Selda fills in
You never send these. The HTTP layer overwrites them from the API key, which is what keeps one organisation’s data out of another’s reach.
| Argument | Filled in from |
|---|---|
orgId | your organisation, resolved from the API key |
Example request
Required arguments only. Values in angle brackets are yours to fill in; the optional ones are in the table above.
curl -X POST https://api.selda.ai/mcp/query \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{ "fn": "chats.get", "args": { "projectId": "<projectId>", "chatId": "<chatId>" } }'{
"fn": "chats.get",
"args": {
"projectId": "<projectId>",
"chatId": "<chatId>"
}
}Example response
Every endpoint answers in the same envelope, whichever URL you called.
{
"value": <the function's return value>,
"request_id": "req_..."
}The shape of value is not documented here. chatMcp:getForKey declares no returns validator, so there is nothing to derive it from, and a shape written out by hand here is a shape that goes stale without anything noticing. Call it once against a test key and read what comes back.
On failure the body is { "error": { "type", "code", "message", "request_id" }, "request_id" } and request_id is echoed in the X-Request-Id header.
Generated from convex/lib/mcpRegistry.ts. Nothing in this reference sends: launchRun is in no
registry and never will be, so a script can prepare a campaign completely and a person still
presses send in the app.