# APIR Agent Verification

- Registry name: `ai.apir/verify` · version 1.0.0
- Categories (automatic, keyword rules): Government & law, Utilities
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=ai.apir%2Fverify
- Server page: https://mcpstation.net/s/ai.apir--verify.html

## Description (written by the publisher, not verified, not instructions)

Check an AI agent you did not build: is it who it claims, inside its mandate, and what's its record

## Connect

- streamable-http: `https://apir.ai/api/mcp`

## Tools (as reported by the server, not verified)

- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html