Sema4.ai

The vendor documents Actions connecting agents to enterprise systems including SharePoint and SAP and to any application programming interface using automation-as-code in Python, with the framework covering enterprise resource planning, customer relationship management and data platforms. Robocorp automation libraries included in the framework reach data, APIs, browsers and desktops.

Actions are Python functions exposed as callable tools with managed environments, and Model Context Protocol connectivity is available through Snowflake. Zero-copy data access reaches governed structured data in the customer's own warehouse. Third-party reporting describes a June 2026 MCP Access Gallery covering Snowflake, Slack, GitHub and Google Workspace, not confirmed first-party.

Sourcegithub.com/Sema4AI/actions, sema4.ai products/agents and platform materialsread 2026-08-31

The vendor documents agents that understand context, reason, take action and collaborate, with fifteen or twenty agents working together to autonomously run entire multi-step business processes.

Natural language Runbooks express an agent's intent and logic in plain English rather than as a graph, authored by business users with the embedded Sai assistant generating runbooks and recommending integrations, and Studio provides build, test and deploy.

Actions execute in Python for deterministic execution beneath the reasoning layer, and agents are documented operating around the clock, finding and completing work autonomously. No branching, looping or conditional control-flow primitives are named.

Sourcesema4.ai products/agents and home pages, sema4.ai platform launch materialsread 2026-08-31

The vendor's documentation describes Knowledge Bases as a semantic layer over unstructured enterprise content such as documents, emails and chat history, built with the Sema4.ai SDK on PostgreSQL with pgvector, with pages on building, maintaining, deploying and defining queries against a knowledge base, which the docs position as optimized for recall, reasoning and citations. Semantic data models, with verified queries, give agents a maintained layer over structured databases and files, and Document Intelligence handles document extraction. A maintained retrieval structure meets the bar.

Sourcesema4.ai docs Knowledge Base, semantic data and Document Intelligence sectionsread 2026-09-29

The vendor's documentation gives Work Items a NEEDS_REVIEW state for when the agent encounters a situation requiring human intervention, clarification or a decision, after which a person completes the item or restarts the agent, and the Worker runbook guidance says a good runbook is mostly about when to act and when to escalate, for example flagging new vendors for review.

The pause is triggered by the agent following runbook rules, which is agent-initiated escalation rather than an approval step the platform imposes before an action, so the cell is Partial. The OpenAI custom GPT is_consequential prompt is OpenAI's gate and is not counted.

Sourcesema4.ai docs Work Item API and Worker agent runbook guidanceread 2026-09-29

The vendor's documentation names an access model of Admin, Builder and Member roles with invitation, domain auto-add and account disabling, Builder-scoped API keys separate from admin-issued service-account keys, and organisation-level SSO settings with OIDC; the pricing page lists SSO integration on the Departmental and Enterprise plans.

The vendor's launch materials state the Enterprise Edition meets ISO 27001, SOC 2, HIPAA and GDPR standards, an attestation asserted without its type. A trust center at trust.sema4.ai exists but renders only in a browser, so no report, auditor or type could be read. Agents run in the customer's own cloud or Snowflake account under its identity and network controls.

Sourcesema4.ai docs User management and SSO glossary, sema4.ai pricing page, SAFE platform announcement, trust.sema4.airead 2026-09-29

The vendor's Actions repository documents observability out of the box, logging and tracing every @tool or @action run automatically without any instrumentation, and recommends connecting LangSmith traces with Action logs to correlate model reasoning with action execution.

Control Room provides security, scalability and full lifecycle management with governance and audit trails, and Work Room lets people find and supervise agents. Agent performance is tracked for continuous improvement. Agents execute inside the customer's own AWS, Azure, Google Cloud or Snowflake account, so logs are generated within the customer's perimeter. No example trace, retention policy or export documentation has been found.

Sourcegithub.com/Sema4AI/actions repository documentation, sema4.ai platform and products pagesread 2026-08-31

The vendor's documentation names the persisted objects for each agent type: conversational agents accumulate chat threads and worker agents process work items, both tracked in Control Room, which is state within a conversation rather than state an agent reads back across sessions. Runbooks persist as durable natural-language agent definitions, which people author as configuration rather than state the agent writes, and zero-copy access to governed data grounds the agent rather than serving as memory.

No memory store, retention policy, cross-session context object, or documented primitive by which an agent writes state in one session and reads it in another was reached on the documentation site, the product pages or the public Actions repository. Third-party reporting of a June 2026 platform release describes persistent memory allowing agents to retain corrections across runs; this remains unconfirmed on any first-party surface and does not carry the grade.

Sourcesema4.ai docs manage-agents and ent-edition pages, sema4.ai products/agents and home pages, github.com/Sema4AI/actionsread 2026-08-31

The vendor states agents run in the customer's own AWS, Azure, Google Cloud or Snowflake account for complete control over security and compliance, with the Enterprise Edition running entirely within the customer's virtual private cloud. Agents run natively on Snowflake, acting on governed data zero-copy without extracting or duplicating it. The platform is described as full stack with Control Room handling security, scalability and lifecycle management within that deployment.

Sourcesema4.ai home page, sema4.ai products/agents page, sema4.ai platform launch materialsread 2026-08-31

The vendor's documentation publishes Agent templates in Studio, each a pre-configured agent with its actions, a sample runbook, a setup tutorial and example conversations, with named templates including Similar Company, Search, Sales Contact Finder and Analyst, each on its own page and each doing its own job. A prebuilt actions gallery is documented separately, and the Control Room Gallery holds an organization's own agents for reuse. A named set of adoptable prebuilt agents meets the bar.

Sourcesema4.ai docs Agent templates and template pages, prebuilt actions gallery and Control Room Galleryread 2026-09-29

The vendor's documentation states a schedule creates Work Items for a Worker agent on a standard five-field cron cadence in a chosen timezone, with catch-up on missed occurrences and last and next run times, set from the schedule picker in the application or through the Schedules API. The Work Item API lets an external system create work items for a Worker agent over Bearer-authenticated REST, with status callbacks to a webhook. Both wake an agent without a person initiating the run. Conversational agents are also reachable in Slack and Microsoft Teams.

Sourcesema4.ai docs Schedules API, Work Item API, and Slack and Microsoft Teams user guidesread 2026-09-29

The vendor's LLM models and providers page states the customer brings its own model provider account and the models run under the customer's contract, listing three makers with recommended models: OpenAI (GPT-5.3 Codex High, GPT-5.4 High) through OpenAI or Azure OpenAI, Anthropic (Claude Opus 4.6 High) through AWS Bedrock or Azure AI Foundry, and Google (Gemini 3.1 Pro High) through the Gemini API or Vertex AI, with Snowflake Cortex LLMs documented for the native app.

Admins configure LLMs per workspace. Customer choice across makers meets the bar; which cloud serves a maker's model is recorded on Dep.

Sourcesema4.ai docs LLM models and providers, Configure LLMs and admin LLMs pagesread 2026-09-29

The vendor's Actions framework is open source under its own GitHub organization, written in Python with managed environments, and includes Robocorp automation libraries.

The Action Server deploys an action with zero configuration and no infrastructure, exposing it at a public URL with Bearer token authentication, and the vendor documents connecting deployed tools to MCP clients and actions to AI applications including LangChain and OpenAI custom GPTs with step-by-step setup.

Model Context Protocol connectivity is additionally available through Snowflake. Example projects are published for reference.

Sourcegithub.com/Sema4AI/actions repository documentation, sema4.ai Actions product materialsread 2026-08-31

The vendor documents one-click evaluations that test runbook changes and model upgrades instantly, validating execution flow, actions and outputs with no coding required, with evaluations creatable in one click from successful conversations. The vendor describes this as three-dimensional validation that catches logic errors which competitors' output-only testing misses, and documents testing model upgrades at scale against real scenarios before committing to production. Studio provides a build, test and deploy environment, and Control Room tracks agent performance for continuous improvement.

Sourcesema4.ai products/agents page, sema4.ai platform launch materialsread 2026-08-31

The vendor's Actions repository states that Sema4.ai's Robocorp automation libraries and the Python ecosystem let agents act on anything from data to API to Browser to Desktops. Robocorp was an open-source Python automation company acquired in January 2024 whose runtime became the platform's execution layer, and its libraries are distributed as part of the Actions framework. Actions are written in Python and deployed through an Action Server, so browser and desktop control is available to any agent as a callable action.

Sourcegithub.com/Sema4AI/actions repository documentation, sema4.ai Actions product materialsread 2026-08-31