K9X.ai
Kafka: connecting… 0 events MCP: /mcp generator: stopped ← Home FAQ Architecture →

AI agents don't run on yesterday's data.

Live events flow through Kafka and a k9x Shield gate into live state. The Orchestrator hands the agent the invoice's current state; just before acting, the agent re-checks over MCP, and every answer is screened again. Start the generator, then run a scenario and watch the world change while the agent is reviewing.

Generator incoming AP events Kafka (Redpanda) topics ap.invoice.updated ap.payment.posted ap.vendor.flagged Shield gate screens every event ContextIngest Live state latest + recent changes as_of on every value MCP server get_current recent_changes Agent Orchestrator → Squad live_context + MCP k9x Shield decision dots: one per Kafka event (topic colour), red when the gate refuses it · violet: an MCP call from the agent to the live state and back · red at the MCP server: request refused, live state never read

Agent simulator · sample agents asking the MCP server for live context

or click an agent to send one request. Start the generator first so there is live data to ask about.

Threat simulator · each of these must be stopped

Requests and answers appear here: agent → MCP server, then MCP server → agent, with the value's age.

Incoming data

Rate: 1.0 events/s
ap.invoice.updated0 ap.payment.posted0 ap.vendor.flagged0

Scenarios

Live state · from Kafka, as of now

InvoiceVendorAmountStatusAs of
Start the generator to see invoices arrive.

Agent · run a scenario

The agent's steps, every MCP call (with its as-of time and Shield's verdict) and its decision appear here.

Event log · Kafka

No events yet.