Accept
Accept Labs is the company behind MIDAS, an open-source authority-governance engine for autonomous decisions. MIDAS evaluates every agent or AI-system action against explicit authority, operational boundaries, and execution context before the action occurs, then produces exactly one outcome (accept, escalate, reject, or request_clarification) and one tamper-evident audit envelope. The platform is Apache-2.0 Go software with a runtime evaluation API (POST /v1/evaluate), a YAML control-plane for surfaces/profiles/grants, an evidence and integrity API, drift detection, an Explorer UI, and OIDC/local IAM. It is positioned for enterprise teams governing what automated actors are authorised to decide.
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 Accept the way a machine reads it — 29 machine-readable artifacts across 23 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 — Accept scores 48.0/100 (developing), with a separate agent-readiness read of 84/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 Accept
Each block below is one kind of artifact we hold for Accept. 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 23
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.
Accept Agents API
The Agents API from Accept — 1 operation(s) for agents.
Accept Aisystems API
The Aisystems API from Accept — 5 operation(s) for aisystems.
Accept Businessservices API
The Businessservices API from Accept — 3 operation(s) for businessservices.
Accept Capabilities API
The Capabilities API from Accept — 5 operation(s) for capabilities.
Accept Controlplane API
The Controlplane API from Accept — 18 operation(s) for controlplane.
Accept Coverage API
The Coverage API from Accept — 1 operation(s) for coverage.
Accept Decisions API
The Decisions API from Accept — 1 operation(s) for decisions.
Accept Drift API
The Drift API from Accept — 15 operation(s) for drift.
Accept Envelopes API
The Envelopes API from Accept — 2 operation(s) for envelopes.
Accept Escalation Targets API
The Escalation Targets API from Accept — 4 operation(s) for escalation targets.
Accept Escalations API
The Escalations API from Accept — 1 operation(s) for escalations.
Accept Evaluate API
The Evaluate API from Accept — 1 operation(s) for evaluate.
Accept Evidence API
The Evidence API from Accept — 4 operation(s) for evidence.
Accept Fail Mode Policies API
The Fail Mode Policies API from Accept — 3 operation(s) for fail mode policies.
Accept Grants API
The Grants API from Accept — 2 operation(s) for grants.
Accept Graphs API
The Graphs API from Accept — 2 operation(s) for graphs.
Accept Healthz API
The Healthz API from Accept — 1 operation(s) for healthz.
Accept Platform API
The Platform API from Accept — 1 operation(s) for platform.
Accept Processes API
The Processes API from Accept — 3 operation(s) for processes.
Accept Profiles API
The Profiles API from Accept — 4 operation(s) for profiles.
Accept Readyz API
The Readyz API from Accept — 1 operation(s) for readyz.
Accept Reviews API
The Reviews API from Accept — 1 operation(s) for reviews.
Accept Surfaces API
The Surfaces API from Accept — 4 operation(s) for surfaces.
Scroll within the panel for all 23 ·
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.
accept-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.
MIDAS External Event Contract
External event contract for MIDAS decision governance. Events are written to a transactional outbox in the same Postgres transaction as domain state changes, then dispatched to ...
ASYNCAPISecurity Posture 3
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.
Agentic 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 Accept — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/accept · machine-readable index on apis.io