APIR Agent Verification

{
  "mcpServers": {
    "ai.apir/verify": {
      "url": "https://apir.ai/api/mcp"
    }
  }
}

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

3 shown · authentication unknown

• Check what an agent is allowed to do

  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: authority may only ever narrow. No hop can hold an action, a target or a spending cap wider than the hop above it, and the root must be a human. Use this before letting an agent transact, sign, spend or commit on someone else's behalf. An agent holding a valid credential may still be acting outside its mandate, and those are different questions. The answer is the mandate on file as of checked_at. It is not proof the permission still holds at the moment the action runs: check again at the point of action, and treat a record as proof of what was recorded and when.

  Schema valid · SHA-256 9e743e8af039…

  View input schema

  {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Agent name, credential id, or agent UUID."
      }
    },
    "required": [
      "query"
    ]
  }

• Get APIR public signing keys

  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.

  Schema valid · SHA-256 8e9ea5f4b215…

  View input schema