MAZE
SDKs
Rust, TypeScript and HTTP for MAZE.
Every operation on MAZE is reachable from every shipped SDK plus the raw HTTP wire.
Rust
use map_sdk::Client;
use serde_json::json;
let client = Client::from_env()?;
let resp = client
.dispatch(
"MAZE",
"v1.0.0",
"topology",
json!({
"example": true
}),
)
.await?;
println!("{:#?}", resp);TypeScript
import { MapClient } from '@l1fe/map';
const map = new MapClient({
apiKey: process.env.MAP_API_KEY!,
agentDid: process.env.MAP_AGENT_DID!,
tenantId: 'org_acme'
});
const resp = await map.dispatch({
protocol: 'MAZE',
version: 'v1.0.0',
operation: 'topology',
input: {
"example": true
}
});HTTP wire
POST /v1/dispatch HTTP/2
Host: api.multiagentic.dev
Authorization: Bearer $MAP_API_KEY
X-Agent-Did: $MAP_AGENT_DID
X-Tenant-Id: org_acme
Content-Type: application/json
{
"protocol": "MAZE",
"version": "v1.0.0",
"operation": "topology",
"input": {
"example": true
},
"tenant_id": "org_acme"
}All operations
map.dispatch(...)with operation"topology"— Render the current topology of relationships, scoped by access policy.map.dispatch(...)with operation"prove"— Produce a ZK proof of a structural property without revealing the graph.map.dispatch(...)with operation"path"— Find paths between two nodes under capability scope.
See SDKs for client construction, retry, trace propagation.