HANRIA mandate check
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://check.hanria.ai/v1/a2a
· transport JSONRPC
Check an agent action against a mandate check_action
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.
mandatepolicyauthorizationpermissionguardrailagent safetypre-action checkValidate a mandate before relying on it validate_mandate
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.
mandatevalidationpolicyagent safety2026-10-30 from https://check.hanria.ai/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.