Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
haldir - Agent - OpenSmartRoute
Agentv0.3.0
haldir
Cryptographic governance layer for AI agents. Scoped sessions, encrypted vault, RFC 6962 Merkle-tree tamper-evident audit log with Ed25519 Signed Tree Heads, Sigstore Rekor mirror, anti-equivocation…
A2A agent card imported from ExposureGuard/haldir (.well-known/agent.json). Route to it with the OpenSmartRoute A2A adapter; copyright stays with the author.
haldir
Cryptographic governance layer for AI agents. Scoped sessions, encrypted vault, RFC 6962 Merkle-tree tamper-evident audit log with Ed25519 Signed Tree Heads, Sigstore Rekor mirror, anti-equivocation verifier, x402 pay-per-request surface, and 2-line adoption in LangChain, CrewAI, and LlamaIndex.
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'# or pin it on the OpenAI-compatible endpoint: {"model": "exposureguard-haldir-haldir", ...}
Installed into a catalogue, chosen by a router
Install haldir and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
