ATP STUDIO 2.0 · ENTERPRISE CONTROL PLANE

Human control for AI agent actions in production.

ATP Studio verifies identity, checks authority and policy, requires human approval when risk demands it, and records every decision through MCP and protocol adapters.

See operator console
  • DID identity did:atp · ML-DSA-65
  • Guardian in-path · fail-closed
  • Evidence evaluation confidence · freshness · scope
  • Audit evidence hash-chained · driver shown
ATP Studio 2.0 / Enterprise Preview Guardian · enforcing
GuardianEnforcing
Agents enforced 4 of 5
Fleet avg trust66.8
Policy pass · 24h94%

Illustrative data—not a live deployment. Your authenticated console shows tenant-scoped results.

The problem

Most agent stacks still run on trust, not control.

AI agents can read records, call tools, trigger workflows, and delegate actions. But most teams still rely on model wrappers, prompt rules, and fragmented logs instead of verifiable identity, policy enforcement, and evidence-grade audit trails.

No stable identity

for agents across tools and vendors

Weak policy enforcement

at the moment of action

Poor incident evidence

when an agent misbehaves

How ATP works

A trust layer for agent operations

01

Issue identity

Give each agent a DID-based identity before it touches tools, APIs, or sensitive systems.

02

Enforce policy

Route actions through ATP Guardian for synchronous allow, deny, throttle, or review decisions.

03

Score trust

Track trust over time using policy results, risk signals, and revision events.

04

Prove what happened

Write auditable events, live streams, and anchored exports for investigation and compliance.

Operator console

Built for operators, with every claim traceable.

ATP Studio gives security and platform teams a working control plane to review agents, inspect trust shifts, simulate policies, and investigate enforcement events in one place.

ATP Studio 2.0 / Enterprise Preview Guardian · enforcing
Guardian Enforcing p50 41ms
Fleet trust 66.8 ▲ 4.2 this week
Policy pass 94% floor 90%

Needs attention 3

Review blocked agent unknown-scraper-x · trust 23 · 12 DENY Review
Inspect scoring revision impact data-egress-worker → 58 · below floor 60 Inspect
orchestrator-prime did:atp:agt_9f2a… · MCP 92

Live audit STREAMING

  • 12:04:11 orchestrator-prime · tool.read customer_pii ALLOW
  • 12:04:09 unknown-scraper-x · tool.export bulk_users DENY
  • 12:03:55 billing-reconciler · a2a.invoke settle() ALLOW
  • 12:03:12 data-egress-worker · tool.read s3://logs THROTTLE

8,412 today Export anchored slice

Guardian enforcing Needs attention · 3 Trust Score Detail · 92 Live Audit Export anchored slice

Illustrative data—not a live deployment. Your authenticated console shows tenant-scoped results.

Who it's for

For teams deploying agents in high-consequence environments

Enterprise SaaS

Customer-facing copilots touching records and workflows.

Fintech / payments

Agents interacting with financial operations and approvals.

Security / platform teams

Owners of the controls other teams' agents run inside.

Pilot program

Pilot ATP Studio in 30 days

Start with 1–3 agents in a staging or production-adjacent workflow. ATP adds DID identity, Guardian enforcement, trust scoring, and audit visibility without requiring a full platform rewrite.

WHAT'S INCLUDED

  • 1–3 agents instrumented
  • One sensitive workflow
  • Operator dashboard included
  • Incident/audit review flow included

30-DAY PILOT

Request a pilot