AKARI Keymaster
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://ai-akari.ai/a2a/keymaster/jsonrpc
· transport
· protocol JSONRPC
https://ai-akari.ai/a2a/keymaster/rest
· transport
· protocol HTTP+JSON
Get Secret get_secret
Fetch an approved secret for a given service and key name through the read-only Keymaster boundary.
secretsvaultkeymasterruntime-authList Services list_services
List known service and key-name combinations that Keymaster can expose.
discoveryservice-catalogvaultList Secrets list_secrets
Enumerate retrievable secret paths in service/key_name form for audit-safe discovery.
discoverysecretsverificationHealth Check healthcheck
Check Keymaster reachability and validate known credentials against supported upstream services.
healthmonitoringopsRotate Secret Instructions rotate_secret
Explain the safe Vault-side rotation path while keeping the A2A agent read-only.
rotationvaultsecurityread-only2026-10-30 from https://ai-akari.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.