Tools and capabilities

Connect a local or remote client using MCP setup. List tools after connecting to see the catalog exposed by that server. A listed tool describes an API contract; it does not grant permission, confirm a subscription, or prove every workflow works for your Account.

Account tools

The maintained 38-operation catalog contains 31 Account tools. Use your Account key for this site and omit an explicit workspace selector for these tools. They use the Account's canonical product owners and Personal context. An Enterprise application is not required for ordinary Personal access. An explicit Team selector is rejected for Account tools; it is never silently dropped.

Organization runtime tools

These seven operations form the legacy organization runtime contract. Their presence does not establish Team availability on the host you connect to. Explicit workspace use requires advertised server capability and current Account membership, role, surface ceiling, grant and operation permission. A workspace UUID is only a selector. If the client reports workspace_capability_unsupported, keep the intended context and stop; do not retry against Personal.

Tool catalog

Tool	API method and path
`createSoulSourceAsset`	`POST /v1/soul-source-assets`
`createSoul`	`POST /v1/souls`
`getSoul`	`GET /v1/souls/{soul_id}`
`updateSoul`	`PATCH /v1/souls/{soul_id}`
`createSoulResponse`	`POST /v1/souls/{soul_id}/responses`
`createSoulGeneration`	`POST /v1/souls/{soul_id}/generations`
`getOperation`	`GET /v1/operations/{operation_id}`
`createPost`	`POST /v1/posts`
`createMediaUpload`	`POST /v1/media/uploads`
`preparePostGeneration`	`POST /v1/posts/generation-pricing`
`generatePost`	`POST /v1/posts/generations`
`monetizeSoul`	`POST /v1/souls/{soul_id}/monetize`
`unmonetizeSoul`	`POST /v1/souls/{soul_id}/unmonetize`
`publishSoul`	`POST /v1/souls/{soul_id}/publish`
`createAccountSoul`	`POST /v1/account/actions/createAccountSoul`
`getAccountSoul`	`POST /v1/account/actions/getAccountSoul`
`listAccountSoulDrafts`	`POST /v1/account/actions/listAccountSoulDrafts`
`getAccountSoulDraft`	`POST /v1/account/actions/getAccountSoulDraft`
`updateAccountSoulDetails`	`POST /v1/account/actions/updateAccountSoulDetails`
`generateAccountSoulLooks`	`POST /v1/account/actions/generateAccountSoulLooks`
`generateAccountSoulVoice`	`POST /v1/account/actions/generateAccountSoulVoice`
`selectAccountSoulVoice`	`POST /v1/account/actions/selectAccountSoulVoice`
`updateAccountSoulLanguages`	`POST /v1/account/actions/updateAccountSoulLanguages`
`reviewAccountSoul`	`POST /v1/account/actions/reviewAccountSoul`
`promoteAccountSoul`	`POST /v1/account/actions/promoteAccountSoul`
`getAccountSoulLore`	`POST /v1/account/actions/getAccountSoulLore`
`updateAccountSoulLore`	`POST /v1/account/actions/updateAccountSoulLore`
`createAccountSoulReferenceUpload`	`POST /v1/account/actions/createAccountSoulReferenceUpload`
`finalizeAccountSoulReferenceUpload`	`POST /v1/account/actions/finalizeAccountSoulReferenceUpload`
`abandonAccountSoulDraft`	`POST /v1/account/actions/abandonAccountSoulDraft`
`deleteAccountSoulDraft`	`POST /v1/account/actions/deleteAccountSoulDraft`
`prepareAccountSoulEditSeed`	`POST /v1/account/actions/prepareAccountSoulEditSeed`
`checkAccountSoulHandle`	`POST /v1/account/actions/checkAccountSoulHandle`
`startAccountSoulConversation`	`POST /v1/account/actions/startAccountSoulConversation`
`createAccountSoulResponse`	`POST /v1/account/actions/createAccountSoulResponse`
`getAccountSoulResponses`	`POST /v1/account/actions/getAccountSoulResponses`
`getAccountOperation`	`POST /v1/account/actions/getAccountOperation`
`getAccountCreatorPlan`	`POST /v1/account/actions/getAccountCreatorPlan`

Read, prepare and mutate deliberately

Read-like Account actions can use POST routes; the HTTP method alone does not identify product effects. Inspect each tool's input schema and description. Pricing/preparation is distinct from accepting work, payment, publication or a finished output. Upload intents still require the canonical upload/finalization workflow. An operation locator or accepted/pending response is not terminal success.

Mutations that require an idempotency key must reuse the original key and identical input for the same intent. Changed input can conflict. Do not automatically issue a new key after a timeout, cancellation or transport error: the original command may have committed. Read its canonical operation/lifecycle state where available. Tool registration never bypasses safety, moderation, current permissions, paid terms or resource limits. Generation or other billable work requires the corresponding product authorization; tool discovery is not approval to spend.

Availability and compatibility

Local stdio and remote HTTP clients expose the shared catalog, but client transport support differs. Current remote setup uses an explicit Account bearer key, not OAuth discovery or consent. Match the key and connection surface. See setup and troubleshooting for environment variables, remote headers and client limitations.

The retained hosted verification covered discovery of 38 tools, selected free Personal Creator Plan reads and refusal/protocol boundaries on the public endpoints. It did not exercise all 38 business workflows, prove positive Team execution, or establish paid/provider terminal output. Package publication, local factory tests and hosted product proof are separate evidence. The catalog here is derived from the published package snapshot; newly proposed tools are not added here until their canonical contract and selected package/server catalog are updated.

For endpoint schemas and response fields, use the API reference. The SDK quickstart includes installation and language-client examples. Installing a newer client does not itself upgrade server capability or workspace authority.