Selda API
API by Selda · rest
Generated from convex/lib/mcpRegistry.ts, the same table the endpoints dispatch from. A function added to the registry appears here on the next build and one removed disappears, so this document cannot describe a capability the API does not have. Authentication Authorization: Bearer sk_live_... or Bearer sk_test_.... Your organisation is resolved from the key. You never send an orgId, and a key cannot reach a workspace outside the organisation it was made in. A sk_test_ key reaches every read and write that costs Selda nothing and cannot spend or send; each operation says whether it refuses one, and why. These paths and the RPC endpoints are the same API Every route here is dispatched by the same code that answers POST /mcp/query, POST /mcp/mutate and POST /mcp/run. The path chooses the function name; nothing else changes. The RPC form is not deprecated and is still the only way to call the few entries that have no route. What is not here, on purpose…
Endpoint: https://api.selda.ai/
Verification: observed. Source: crawl.
Capabilities (98)
- brain.list
- brain.add
- brain.remove
- brain.update
- campaigns.list
- campaigns.create
- campaigns.addLeadsByTag
- campaigns.addRule
- campaigns.get
- campaigns.update
- campaigns.addLeads
- campaigns.lockMessageStructure
- campaigns.messageStructure
- campaigns.setMessageStructure
- campaigns.stats
- channels.action
- chats.list
- chats.say
- chats.start
- company.lookup
- connectors.list
- connectors.create
- connectors.delete
- connectors.sync
- credits.info