Connect with an operator-issued execution credential and inspect metrics, policy, authority and receipt snapshots. The approval client is a different, privileged interface.
When to use this
Use this when several local processes need scoped access to one operator-owned runtime and its snapshots.
Install the matching API preview
These examples use the API 2 preview, not names promised by the public RC5 release. Existing RC5 entry points remain available. The Python wheel below is verified on Windows x64; it is not a cross-platform release.
python -m pip install https://docs.soterias.io/downloads/api-preview/soterias_local-0.1.0rc5%2Bapi2-cp311-abi3-win_amd64.whlnpm install https://docs.soterias.io/downloads/api-preview/soterias-core-0.1.0-rc.5-api.2.tgz
npm install --save-dev typescript@5.8.3 @types/node@24Python imports soterias. TypeScript imports @soterias/core. Use Python 3.11+ for this wheel and Node 22.23.4+ for these examples. For a .mts file, compile with npx tsc example.mts --target ES2022 --module NodeNext --moduleResolution NodeNext --skipLibCheck, then run the emitted .mjs file.
Before you run
Set SOTERIAS_DAEMON_URL and SOTERIAS_DAEMON_TOKEN from the already running local daemon's trusted operator setup. This complete example performs three real read-only snapshot calls. Execution and approval credentials remain separate.
The SDK never invents missing identities, policy, trust or custody. For protected features, obtaining those operator artifacts is a prerequisite, just as connecting to a database requires its configured credentials. The native test provisioning helper is contributor tooling, not the application API.
Application walkthrough
Choose Python or TypeScript. Create example.py or example.mts and append that language's chunks in order. Each language forms one complete program; indentation and open blocks carry across chunks.
Import the packages
Import the SDK and standard-library helpers. These are the real package exports used by the executable program.
import asyncio
import json
import os
from soterias import securityimport { security } from '@soterias/core';Connect with an execution credential
The operator runs and configures the daemon. Never reuse its approval credential.
# %% Connect with an execution credential
# The operator runs and configures the daemon. Never reuse its approval credential.
client = security.Daemon(os.environ["SOTERIAS_DAEMON_URL"],
os.environ["SOTERIAS_DAEMON_TOKEN"].encode())
async def inspect():
async with client:// %% Connect with an execution credential
// The operator runs and configures the daemon. Never reuse its approval credential.
const client = new security.Daemon({ url: process.env.SOTERIAS_DAEMON_URL!,
bearer: Buffer.from(process.env.SOTERIAS_DAEMON_TOKEN!) });
try {Read current snapshots without executing an effect
These snapshots describe state; they grant no new authority.
# %% Read current snapshots without executing an effect
# These snapshots describe state; they grant no new authority.
metrics = json.loads((await client.metrics_async()).canonical_bytes())
authority = json.loads((await client.authority_graph_async()).canonical_bytes())
warrants = json.loads((await client.warrants_async()).canonical_bytes())
print(json.dumps({"status": "PASS", "snapshots": 3,
"metrics_version": metrics["version"],
"authority_version": authority["version"],
"warrants_version": warrants["version"]})) // %% Read current snapshots without executing an effect
// These snapshots describe state; they grant no new authority.
const metrics = JSON.parse((await client.metricsAsync()).canonicalBytes().toString());
const authority = JSON.parse((await client.authorityGraphAsync()).canonicalBytes().toString());
const warrants = JSON.parse((await client.warrantsAsync()).canonicalBytes().toString());
console.log(JSON.stringify({ status: 'PASS', snapshots: 3,
metrics_version: metrics.version, authority_version: authority.version,
warrants_version: warrants.version }));
} finally {Close the caller-owned client after pending reads
For local IPC use security.Daemon.connect_ipc(root, name, bearer) instead.
# %% Close the caller-owned client after pending reads
# For local IPC use security.Daemon.connect_ipc(root, name, bearer) instead.
asyncio.run(inspect()) // %% Close the caller-owned client after pending reads
// For local IPC use the daemon's ipc option instead of url.
client.close();
}MCP composition
This complete stdio server calls this feature's real SDK operation. Its bounded tool inputs cannot replace host-selected trust, checkpoint or storage paths. Save it as mcp.mjs and configure your MCP client to launch node mcp.mjs. Public data inputs use the same environment settings as the application program. The code is a custom application tool, not a newly claimed built-in Soterias endpoint.
Install the matching adapter with npm install https://docs.soterias.io/downloads/api-preview/soterias-mcp-server-0.1.0-rc.5-api.2.tgz. Its SDK peer dependency shares the same native class identities as your installed preview.
mcp.mjs
Create mcp.mjs and append these chunks in order. Together they form one complete program; indentation carries across chunks.
Step 1
Import the SDK and standard-library helpers. These are the real package exports used by the executable program.
import { security, Soterias, observe, canonicalize, Metrics, audit, HistoricalPolicyInputs } from '@soterias/core';
import fs from 'node:fs';
import os from 'node:os';
import path from 'node:path';
import { McpServer } from '@modelcontextprotocol/server';
import { serveStdio } from '@modelcontextprotocol/server/stdio';
import * as z from 'zod/v4';
// Trusted startup: paths, trust and credentials are fixed by the host.
const client = new security.Daemon({url: process.env.SOTERIAS_DAEMON_URL, bearer: Buffer.from(process.env.SOTERIAS_DAEMON_TOKEN)});
// Agent input is bounded data. It cannot replace host configuration or trust.
const handle = serveStdio(() => {
const server = new McpServer({name: 'soterias-daemon', version: '1.0.0'});
server.registerTool('daemon_metrics', {
description: 'Use daemon through the host-selected native SDK.',
inputSchema: z.object({}).strict(),
}, async input => {
try {
const result = await (async () => {
return JSON.parse((await client.metricsAsync()).canonicalBytes().toString());
})();
return {content: [{type: 'text', text: JSON.stringify(result, (_key, value) => typeof value === 'bigint' ? value.toString() : value)}]};
} catch {Step 2
Finish outstanding work and release owned resources. Cleanup errors must not silently replace an existing application error.
return {isError: true, content: [{type: 'text', text: 'feature_request_refused'}]};
}
});
return server;
}, {maxSubscriptions: 0});
process.stdin.once('end', () => {
void (async () => { await handle.close(); client.close(); })();
});Test the tool over a real MCP connection
Save this client next to mcp.mjs, then run node client.mjs. It starts the host, calls the actual feature tool and closes the connection. It does more than list the tool catalog.
client.mjs
Create client.mjs and append these chunks in order. Together they form one complete program; indentation carries across chunks.
Step 1
Import the SDK and standard-library helpers. These are the real package exports used by the executable program.
import { Client } from '@modelcontextprotocol/client';
import { StdioClientTransport } from '@modelcontextprotocol/client/stdio';
import { fileURLToPath } from 'node:url';
const client = new Client({name: 'feature-example', version: '1.0.0'});
try {
await client.connect(new StdioClientTransport({
command: process.execPath,
args: [fileURLToPath(new URL('./mcp.mjs', import.meta.url))],
env: Object.fromEntries(Object.entries(process.env).filter(([, value]) => value !== undefined)),
}));
const result = await client.callTool({name: 'daemon_metrics', arguments: {}});
if (result.isError) throw new Error('Feature request refused');
console.log(JSON.stringify(result));
} finally { await client.close(); }Check the result
The application program prints a JSON result and preserves native refusals. For protected operations inspect status and target_observed: transport success does not imply a completed effect. The pure examples contain assertions for their exact expected values. Successful startup is not proof of production enrollment, a physical human review or current authority.
Put it into a workflow
Use the AML walkthrough for protected document reads, reviewed writes and signed outcome checks. Use multi-agent workflows for personal and enterprise orchestration. Keep each agent's proposals separate from operator authority.