ai.apir/verify · v1.0.0 · agents-and-memory
APIR Agent Verification is healthy: it completed an MCP handshake in 3061 ms and exposes 3 tools. It scores 59/100.
Check an AI agent you did not build: is it who it claims, inside its mandate, and what's its record
Endpoint: https://apir.ai/api/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| health | 17 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 7 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 5 / 10 |
Scoring v0.3, computed 2026-10-14T14:16:22.083Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T08:59:37.245Z | Healthy | 3061 |
verify_agent | Check whether an AI agent carries a real, cryptographically signed credential. Accepts an agent name, a credential id (TP-...), an agent UUID, a domain or a DID. Returns one of seven verdicts: VERIFIED, EXPIRED, REVOKED, SUPERSEDED, UNSIGNED, UNCHECKED or NO_RECORD. IMPORTANT for interpreting the an |
check_authority | Resolve the human mandate behind an AI agent: which actions a named person actually permitted, any value cap, the expiry, and whether the grant itself is signed. Where authority was delegated agent to agent, the full chain is walked back to the human at the root, and one law is enforced at every hop |
get_verification_keys | Return the Ed25519 public keys APIR publishes, so a signature can be recomputed offline without trusting any APIR response, including this one. Keys are published as a JWKS at apir.ai/.well-known/jwks.json and as did:web:apir.ai. Retired keys stay published so older credentials still verify. |