MOOT
SDKs
Rust, TypeScript and HTTP for MOOT.
Every operation on MOOT 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(
"MOOT",
"v1.0.0",
"file",
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: 'MOOT',
version: 'v1.0.0',
operation: 'file',
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": "MOOT",
"version": "v1.0.0",
"operation": "file",
"input": {
"example": true
},
"tenant_id": "org_acme"
}All operations
map.dispatch(...)with operation"file"— File a case: caller, respondent, claim, evidence, requested remedy.map.dispatch(...)with operation"plead"— File a structured plea or response; evidence channels open through MAVEN.map.dispatch(...)with operation"rule"— Issue a ruling; binding under the active charter; appealable under stated terms.
See SDKs for client construction, retry, trace propagation.