Moveworks
Moveworks is an enterprise agentic AI assistant platform that lets employees search and act across 100+ business applications (Slack, ServiceNow, Workday, Jira, Salesforce, SAP, Microsoft) through conversational AI agents. Its "Build with Moveworks" developer platform and Agent Studio expose REST APIs to send events and proactive messages, drive AI Assistant conversations (including streaming), export analytics data, and receive inbound webhooks, plus a set of customer-hosted gateways (Content, Identity, Knowledge, Forms) that feed enterprise data to the AI. All APIs use HTTP Bearer authentication with OAuth 2.0 Client Credentials issuing short-lived access tokens, are published as OpenAPI 3.1 with a discoverable /.well-known/api-catalog, and are deployed across US, EU, Canada, GovCloud (FedRAMP), Japan and UK regions.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Moveworks the way a machine reads it — 19 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Moveworks scores 57.7/100 (developing), with a separate agent-readiness read of 75/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Moveworks
Each block below is one kind of artifact we hold for Moveworks. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Moveworks authentication API
The authentication API from Moveworks — 2 operation(s) for authentication.
Moveworks conversations API
The conversations API from Moveworks — 3 operation(s) for conversations.
Moveworks Default API
The Default API from Moveworks — 14 operation(s) for default.
Moveworks deprecated API
The deprecated API from Moveworks — 1 operation(s) for deprecated.
Moveworks events API
The events API from Moveworks — 1 operation(s) for events.
Moveworks messages API
The messages API from Moveworks — 3 operation(s) for messages.
Moveworks responses API
The responses API from Moveworks — 3 operation(s) for responses.
Moveworks smartForms API
The smartForms API from Moveworks — 3 operation(s) for smartforms.
Moveworks webhooks API
The webhooks API from Moveworks — 1 operation(s) for webhooks.
Scroll within the panel for all 9 ·
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOMoveworks — start an AI Assistant conversation and read the reply
Create a conversation, request a response, then list the resulting messages.
ARAZZOMoveworks — authenticate and notify employees for an event
Mint an OAuth client-credentials token, verify it, then send an event-triggered message to employees.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
moveworks-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Moveworks Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Moveworks Trust Center
SOC 2 Type 2, ISO 27001, ISO 27017, ISO 27018, ISO 27701, ISO 42001, CSA STAR Level 2, FedRAMP, GDPR, CCPA
SECURITYAgentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Moveworks — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 6
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 7
Status, limits, changes, and where to get help
Scroll within the panel for all 7 ·
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/moveworks · machine-readable index on apis.io