Maisa
Maisa is an enterprise agentic-AI company whose platform, Maisa Studio, lets non-technical teams build, deploy, and manage "Digital Workers" — AI agents that automate complex, regulated, end-to-end business processes. Its proprietary Knowledge Processing Unit (KPU) and Chain-of-Work approach combine large and small language models to deliver deterministic, auditable, hallucination-resistant execution rather than probabilistic responses, making it regulator-ready from day one. Maisa targets highly regulated verticals — banking and financial services, insurance, manufacturing and supply chain, and engineering/infrastructure — with an employee-based pricing model instead of per-token API billing. Maisa also exposes a developer REST API at api.maisa.ai (API-key authenticated via X-API-Key) with capabilities (compare/extract/summarize over text and media), models (embeddings, rerank), a KPU run endpoint, a file-interpreter (PDF/DOCX/HTML/image/audio), and Mainet search — with official first-party Python and Node SDKs both named "maisa"; the Maisa Studio product and the docs portal (docs.maisa.ai) sit behind an AWS Cognito login. Backed by Creandum and ForgePoint, Maisa has raised a $25M seed round and been named a Gartner front-runner in agentic AI. This profile was enriched from Maisa's public marketing surface, llms.txt, and the official open-source SDK repositories.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Maisa the way a machine reads it — 4 machine-readable artifacts across 1 API, 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 — Maisa scores 26.7/100 (emerging), with a separate agent-readiness read of 33/100 (agent aware). 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 Maisa
Each block below is one kind of artifact we hold for Maisa. 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 1
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.
Maisa API
Maisa's developer REST API. Key-authenticated (X-API-Key), base URL https://api.maisa.ai, all operations under /v1. Surfaces: capabilities (compare/extract/summarize over text a...
MCP 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.
maisa-mcp.yml
MCP SERVERSecurity Posture 2
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.
Resources
Every other property we hold for Maisa — 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.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/maisa · machine-readable index on apis.io