Documentation

Build with governed context

Everything you need to integrate Strattum into your enterprise AI agent stack: quickstart guide, full API reference, connector configuration, and the SDK for custom data sources.

Start the quickstart API reference

~15 min First connector

REST API interface

SDK Custom connector

Guides and reference

Documentation sections

Quickstart

Install the Strattum client, configure your first connector, write a policy, and run your first governed context query in about 15 minutes.

Get started

API Reference

Full reference for the context query endpoint, connector management API, policy API, and audit log query API. Request/response schemas and status codes.

Read API docs

Connector Reference

Configuration schemas for each pre-built connector. Auth setup, schema declaration, scope mapping, and connector vault credential storage.

Connector docs

Policy Engine Reference

Policy rule syntax, evaluation order, agent identity binding, scope declarations, classification label filters, and policy versioning.

Policy docs

Audit Log Reference

Audit event schema, field definitions, query parameters, export formats, and SIEM integration examples for Splunk, Elastic, and Datadog.

Audit docs

Connector SDK

Build a custom connector for any proprietary data source. SDK interfaces, required methods, schema declaration protocol, and testing utilities.

SDK docs

Common questions

Frequently referenced topics

How policies evaluate queries

The policy engine evaluates agent identity, connector, scope, and classification labels against ordered allow/deny rules before any connector query executes.

Connector vault and credential management

Source credentials are stored in the connector vault during connector registration. Agents never receive credentials; they receive scoped query tokens only.

What the audit log records

Every context query generates an event record with agent ID, query scope, policy rule applied, resolution status, and millisecond-precision timestamp. No data content is logged.

Setting up Salesforce or SAP connectors

Each pre-built connector has a dedicated configuration guide covering auth method, required credentials, schema declaration, and testing the connection.

Building a custom connector

The connector SDK exposes four required interfaces: connect, query, schema, and disconnect. Implement these and the SDK handles policy integration, audit capture, and credential storage automatically.

SIEM-compatible audit export

Audit events can be streamed to Splunk HEC, Elastic Beats, or Datadog Logs directly. JSON field names follow RFC 5424 naming conventions. CSV export is also available on Enterprise.