APIR Agent Verification

ai.apirPublished by apir.aiOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & MonitoringAI & ML

Overview

AI-generated overview

Remote MCP server that lets an assistant verify third-party AI agents' signed credentials, human authority and published verification keys.

What you can do
  • Verify an AI agent's identity by name, credential id, UUID, domain or DID, returning a verdict such as VERIFIED, EXPIRED, REVOKED, SUPERSEDED, UNSIGNED, UNCHECKED or NO_RECORD
  • Resolve the human mandate behind an agent: permitted actions, value cap, expiry, whether the grant is signed, and the full delegation chain back to the human
  • Fetch APIR's published Ed25519 public keys as a JWKS or did:web document so signatures can be recomputed offline
When to use it
Useful when an assistant deals with agents it did not build and needs to check identity, scope of authority or revocation status before trusting them, or when you want to verify APIR signatures independently of APIR's own responses.
Requirements
Remote streamable HTTP endpoint at apir.ai; no packages, environment variables, headers or authentication are declared. Network access to the endpoint and to the published key set is needed.
Before you install
Verdicts come from APIR's own service, so treat them as one party's assertion unless you recompute signatures with the published keys; the tool description notes that verdict interpretation matters. No credentials or write actions are declared.

Installation

In SourceWeft

  1. Open APIR Agent Verification in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.apir%2Fverify/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "apir-agent-verification": {
      "type": "http",
      "url": "https://apir.ai/api/mcp"
    }
  }
}

Tools

3

verify_agent

Verify an AI 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 answer: VERIFIED means the Ed25519 signature recomputes against the key published at apir.ai and the credential is unexpired and unrevoked. It confirms WHO issued the credential and that its contents are unaltered. It is NOT a guarantee that the agent behaves well. NO_RECORD is an honest, first-class answer: it means nothing is on file, which is not evidence of wrongdoing and not a warning. It means any claim the agent makes about itself is unverified. Free, unauthenticated, and no account is required.

Parametersqueryrequired

check_authority

Check what an agent is allowed to do

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.

Parametersqueryrequired

get_verification_keys

Get APIR public signing 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.

Takes no parameters.

Version history

1
  1. v1.0.0LatestOct 13, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.