Skip to content

Use txcast with AI agents

txcast exposes the durable command set through:

  • the private built-in assistant;
  • Streamable HTTP MCP at https://api.txcast.com/mcp/v2; and
  • JSON REST at https://api.txcast.com/agent/v2.

Both transports use the same schemas, credential scopes, controlled-account grants, CAS, idempotency, and audit provenance.

  1. Connect an MCP host to the v2 URL.
  2. Sign in and approve only the required organisations, scopes, and controlled accounts.
  3. Ask the agent to read context, networks, accounts, contracts, and workflows.
  4. Have it validate source before creating or saving a workflow.
  5. Review the capability envelope before each save.
  6. Keep all human responses and wallet signing in txcast’s browser UI.

With the relevant scope, an agent may:

  • inspect organisation context, networks, the audit log, controlled accounts, address-book entries, and contracts;
  • create, update, and delete controlled accounts, address-book entries, and registered contracts when it has the admin-only registry.write scope;
  • validate TypeScript source;
  • create, save, restore, fork, and inspect workflow versions;
  • start runs atomically, inspect and cancel them;
  • inspect concrete effects and request EVM/HTTP source refreshes.

Agents cannot answer human.* effects, submit wallet signatures, sign or broadcast transactions, or administer personal wallets, membership, billing, or notification destinations through the durable v2 command set.

Every scoped command supplies organisationId; a credential has no mutable “current organisation.” txcast rechecks current membership, seat, role, scope, ownership, and controlled-account grant for every call.

Meaningful mutations record credential and client provenance. Exact idempotent replays return the original result without repeating the mutation.