AsyncAPI channel · Accept · MIDAS External Event Contract

midas.decisions

Decision lifecycle events. Partition key is {request_source}:{request_id}.

Open source AsyncAPI → All Accept channels Accept provider profile
Provider: Accept AsyncAPI: v3.0.0 Spec: MIDAS External Event Contract Operations: 2 Messages: 2

Channel address

midas.decisions

Operations

receive
receiveOutcomeRecorded
receive
receiveEnvelopeClosed

Messages

decision.outcome_recorded
Emitted when an evaluation produces a terminal outcome (accept, escalate, reject, request_clarification).
Content-Type: application/json
decision.envelope_closed
Emitted when a governance envelope reaches closed state; includes an optional review object for escalated envelopes.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.