Open standards

Plugs into the protocols your stack already speaks.

StudioX works through the standards your teams already run: for agents, APIs, sign-in, monitoring, events, audit and policy. Here is what each one lets you do.

Model Context Protocol (MCP)

Available

AI interoperability

The open protocol for giving AI agents tools and data sources.

  • Connect any MCP server and your assistants, workflows and missions can call its tools.
  • Turn your own APIs into MCP servers in Integrations, with no code.
  • Reach StudioX itself from any MCP client, signed in with your own API key.

In StudioX: Integrations, and the tools list of every assistant and mission.

modelcontextprotocol.io

Agent2Agent (A2A)

Available

AI interoperability

The Linux Foundation protocol for AI agents to discover and work with each other.

  • Your StudioX assistants and missions are published as A2A agents, each with its own Agent Card.
  • Other companies' agents can send them tasks and stream back the results.
  • Try any external A2A agent from the A2A playground in Studio before you rely on it.

In StudioX: The A2A gateway at /a2a, and the A2A playground in Studio.

a2a-protocol.org A2A on air-gapped networks

OpenAPI

Available

Integration

The standard description format for HTTP APIs.

  • Import an OpenAPI or Swagger spec and each operation becomes a tool your agents can call.
  • Merge several specs into one integration.
  • Network teams can start from YANG models, which StudioX converts to OpenAPI first.

In StudioX: Integrations → import an API.

openapis.org

OAuth 2.0

Available

Integration

The standard for granting an application access to another system without sharing passwords.

  • Connect mailboxes, business systems and MCP servers through their own sign-in screens.
  • Access is granted per connection and can be revoked at the source at any time.

In StudioX: Connections in Integrations and in workflow email listeners.

oauth.net/2

OpenTelemetry

Available

Observability & events

The CNCF standard for traces, metrics and logs.

  • Follow one agent run across every StudioX service as a single trace.
  • Send traces to the monitoring tool you already use: Datadog, Grafana, Splunk or any OTLP endpoint.
  • See which step, tool call or model call is slow or failing.

In StudioX: A per-deployment setting for where traces are sent.

opentelemetry.io

CloudEvents

Available

Observability & events

The CNCF standard format for describing events.

  • Missions send their events (a run finished, an approval is waiting, a decision was made) to your systems in a format any event bus understands.
  • Missions accept CloudEvents from your systems as triggers.

In StudioX: Each mission's event settings and its webhook trigger.

cloudevents.io

W3C PROV

Available

Governance

The W3C standard for recording where data came from and who or what produced it.

  • Download a provenance record for any agent run: which agent or person acted, what data it used and what it produced.
  • Hand auditors a record in a standard format their tools can read.

In StudioX: The reasoning panel beside each mission conversation: Download provenance.

w3.org/TR/prov-overview

Open Policy Agent (OPA)

Available

Governance

The CNCF policy engine, with policies written as code in Rego.

  • Write rules for what agents may do in the same policy language your security team uses for Kubernetes and APIs.
  • Every tool call is checked against your policies before it runs, and every allow or deny is logged.

In StudioX: Studio → Business settings → Security & Access → Agent Policies.

openpolicyagent.org

SAML 2.0

Available

Enterprise identity

The OASIS standard for single sign-on with an enterprise identity provider.

  • Your people sign in with your identity provider; no separate StudioX password.
  • Set up per business, with a step-by-step guide for Microsoft Entra ID.

In StudioX: Studio → Business settings → Security & Access → SSO.

OASIS SAML 2.0

SCIM 2.0

Available

Enterprise identity

The IETF standard for provisioning users and groups automatically.

  • Users and groups added in Microsoft Entra ID appear in StudioX, and leavers are removed.
  • Map directory groups to StudioX roles, and see every provisioning change in a log.

In StudioX: Studio → Business settings → Security & Access → SCIM.

RFC 7644

OpenID Connect

Available

Enterprise identity

The identity layer on top of OAuth 2.0, used for signing in with an existing account.

  • Sign in with a Google or Microsoft work account.

In StudioX: The StudioX sign-in page.

openid.net/connect

OWL

Available

Knowledge

The W3C Web Ontology Language, for describing the concepts in a domain and how they relate.

  • Import the ontologies your teams already maintain, so agents reason with your own vocabulary and relationships.
  • Files exported from Protégé or TopBraid load as they are: Turtle, RDF/XML, OWL/XML, JSON-LD, N-Triples and TriG.
  • Upload a new version under the same name, compare it with the last one, and restore an earlier version.

In StudioX: Each mission's Ontologies page.

w3.org/OWL

Need a standard we haven't listed?

Tell us what your architecture review asks for, and we'll show you how StudioX fits.