Run a detector for lease overlap
List the detectors, run lease-overlap, and read the conflicts it cites with their evidence, then read the cases it filed for review.
detection.run
List the detectors, run lease-overlap, and read the conflicts it cites with their evidence, then read the cases it filed for review.
detection.runPut admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
You want to know when two agents hold the same resource, before it becomes an outage. A detector is a pure function over leases or events. A hit cites what it saw, and each hit is filed as a case at rung 0 of the ladder.
The code reads the key from INTRAMEDIAL_KEY. Keep it in your shell or your secret store, never in a file you commit. Calls that need a signed-in person cannot use a key: the console makes them.
The catalogue lists each detector and its last run. Ten near-path detectors are pure functions, and none uses a model.
The run lists conflicts and the cases filed.
{
"detector": { "id": "lease-overlap", "path": "near", "llm": },
: [],
: [
{
: ,
: ,
: [, ],
: ,
: [, ],
:
}
],
: ,
: [{ : , : }],
: [],
: { : , : }
}suppressed.detection.rundetection-run
curl -sS https://api.intramedial.com/api/v1/acp/detection/catalog \
-H "Authorization: Bearer $INTRAMEDIAL_KEY"const res = await fetch("https://api.intramedial.com/api/v1/acp/detection/catalog", {
headers: { Authorization: `Bearer ${process.env.INTRAMEDIAL_KEY}`, },
});
console.log(res.status, await res.json());import os, requests
res = requests.get(
"https://api.intramedial.com/api/v1/acp/detection/catalog",
headers={"Authorization": "Bearer " + os.environ["INTRAMEDIAL_KEY"]},
timeout=30,
)
print(res.status_code, res.json())Send the detector id; an unknown id returns 404. forceInline matters only for semantic-intent, the one detector that sends text to a model. The ten near-path detectors are pure functions of leases or events.
curl -sS -X POST https://api.intramedial.com/api/v1/acp/detection/run \
-H "Authorization: Bearer $INTRAMEDIAL_KEY" \
-H "Content-Type: application/json" \
-d '{
"id": "lease-overlap",
"forceInline": true
}'const res = await fetch("https://api.intramedial.com/api/v1/acp/detection/run", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.INTRAMEDIAL_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
id: "lease-overlap",
forceInline: true,
}),
});
console.log(res.status, await res.json());import os, requests
res = requests.post(
"https://api.intramedial.com/api/v1/acp/detection/run",
headers={"Authorization": "Bearer " + os.environ["INTRAMEDIAL_KEY"]},
json={
"id": "lease-overlap",
"forceInline": True,
},
timeout=30,
)
print(res.status_code, res.json())A hit cites ledger event ids or lease ids. filed lists the cases opened; suppressed holds repeats while a case for the same parties is open.
Copied from: /docs/detection-run
The ledger is append-only and sealed under Merkle roots. The time on an entry is Intramedial's own clock, and a signed bundle can be checked offline with the published key.
Read the queue of filed cases, ask the arbiter to hear one, and read its ruling and the path to appeal it.
arbitration.arbiterSend nine datasets, each with a completeness declaration, then read the eight metrics and the ranked recommendations to move resources from observe to enforce.
conflict.audit-latestRun the six fixed Intralock scenarios, read the result of each one, and set a cadence so the drill repeats on its own.
drills.frtOne short email when we add recipes to the cookbook. No other mail, and you can unsubscribe from any message.
No key or account: Try it on the coordination.admit module page runs the real kernel in your browser. Use a workspace key for your own workspace.