Zerker/Operator Console

Run every agent from one place

See what needs attention. Open the evidence.

Interactive operator preview

Start with what needs an owner.

Source-backed Console workflows with example tenant data. This preview reads no production system and sends no mutations.

reference tenant / operator viewExample data

Operator queue

Attention

Derived conditions that need a person, ordered by impact.

Updated 18s ago

Needs owner3Example conditions

Active agents121 suspended

Priced traffic41 settlement failure

ConditionAgentEvidenceOwner

Settlement failedUpstream did not runresearch-agentinv_01J8…F73CRevenue

Elevated failures17.2% in selected windowsupport-resolution12 invocationsPlatform

Agent suspendedOperator action remains activecontract-reviewChanged 38m agoLegal ops

System of record

Agent catalog

Identity, protocol, upstream, protection, pricing, and operating state together.

12 agents

AgentDue Diligence Agentagt_research_01

StateActiveNot suspended

ProtocolsHTTP · MCPStreamable HTTP

UpstreamProtectedcredential_ref ·••82A1

Rate boundary40 / minutePer Gateway process

Pricing$2.40 / runVerify and settle

Operator action

Suspend without deleting the record

Keep history intact, stop new routed work, and confirm the authoritative state after the action.

Evidence explorer

Invocations

Filter the work that reached the upstream and open the exact record.

Server-filtered · paginated

agent: allresult: allsettlement: alllast 24 hours

InvocationAgent / modeResultSettlement

inv_01J8…F73Cresearch-agentstream · TTFT 842msCompletedFailed

inv_01J8…08D1support-resolutionMCP · tools/callCompletedNot priced

inv_01J8…9A20contract-reviewtransaction · 202CompletedSettled

Policy denials and unpaid 402 challenges stop before an invocation record exists. This view does not call them invocations.

Commercial state

Settlement evidence

Know whether authorization was verified, funds settled, and the upstream was allowed to run.

x402 exact · USDC on Base

01Challenge$2.40 payment required

02VerifyAuthorization accepted

03SettleFacilitator timeout

04ForwardUpstream did not run

Failure evidencesettlement_failed · facilitator_timeout

Guardrail outcomeNo upstream execution

Next operator stepCheck facilitator readiness and retry policy

The operator loop

Find the problem. Follow the evidence. Act.

Current connected views read the Gateway contract directly and keep unavailable data distinct from a real zero.

01Own
Know each agent, upstream, status, owner, pricing rule, and credential reference.
CATALOG
02Inspect
Filter invocations by agent, result, mode, time, error, and settlement state.
INVOCATIONS
03Act
Suspend or resume an agent and work the conditions surfaced by the attention queue.
CONTROL
04Confirm
Read the authoritative tenant state again. Unknown never becomes zero.
EVIDENCE

Connected views

Nine live views today.

Each view reads the Gateway REST contract directly. Several are read-only and scoped to what their endpoint can actually produce. Unknown, unavailable, and zero remain different states.

Operate the whole agent record.

See catalog status, suspension, protocol, upstream, rate boundary, credential reference, pricing, tags, and per-agent traffic. Register, suspend, or resume an agent from the same view.

GET · POST · PATCH

Find the exact invocation.

Filter server-side by result, mode, agent, time, error class, and settlement state, with the policy decision shown per row. Page through results or look up an invocation ID directly.

/v1/invocations

Work a real attention queue.

Rules flag suspended or pending agents, elevated failures, settlement failures, priced agents without settlement, and credentials no agent references.

6 NAMED RULES

Read the tenant at a glance.

Overview and analytics report live tenant state, with every metric Gateway cannot compute safely removed rather than estimated.

OVERVIEW · ANALYTICS

Inspect credentials, policies, and activity.

Read-only views over stored credentials, the policies applied to them, and recent agent activity scoped to what the summary endpoint can produce.

READ-ONLY

Follow payments and settlement posture.

Read the settlement state behind priced agents and the payment posture of the tenant, without acting on it from the browser.

READ-ONLY

Keep Gateway tokens out of the browser.

The same-origin BFF holds the Gateway bearer server-side. The browser gets an opaque, secure session and sends Console requests to its own origin.

OIDC · BFF

Product truth

Unknown stays unknown.

Console does not invent totals or joins when Gateway cannot supply them safely.

Traffic boundary

Denied and unpaid calls are not invocations.

Policy denials and 402 challenges stop before an invocation row exists. The explorer shows traffic allowed to proceed, not every attempt.

Data boundary

Unknown never becomes zero.

A failed analytics read is unavailable. It does not become zero calls, zero errors, or an empty queue that looks healthy.

Overview, analytics, credentials, and policy.

These views are being connected within the exact REST contract. Until each migration lands, designed previews are not presented here as live operations.

What it operates

Gateway remains the enforcement and data plane. Console is the human operating surface. Portals and managed Rooms become operator surfaces only as their contracts ship.

Open the tenant. Start with attention.

Open Console →Talk to Zerker