# LimitGuard Agent Identity & Reputation Check

> LimitGuard Agent Identity & Reputation Check is a paid API for AI agents from limitguard.ai, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Verifies an AI agent's identity and returns a reputation score and risk level before inter-agent transactions

## Facts

- Endpoint: POST https://limitguard.ai/v1/mcp/check-agent
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/limitguard-agent-identity-reputation-check-23fb269d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IlTp9OKvnRPeDvGj6Al0C

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability limitguard-agent-identity-reputation-check-23fb269d -d '<json body>'
```

Example prompt: Before I let agent 'DataFetcherBot' (agent ID: agnt_0x9f23ab) run tasks on my behalf, can you verify its identity and reputation score through LimitGuard to make sure it's not a high-risk agent?

## When to prefer this

Use this endpoint when you need to verify the identity and trustworthiness of a specific AI agent before allowing it to participate in inter-agent transactions or delegated tasks. Prefer this over the entity check endpoints when the subject is specifically an AI agent (not a human or company), and over the wallet-check endpoint when you need identity verification beyond just on-chain activity.

## Known failure modes

- Unknown agent_id returns unverified status with no reputation data
- Missing required agent_id or agent_name fields returns a 400 validation error
- Payment failure (insufficient USDC balance) returns a 402 Payment Required response
- Rate limiting or service unavailability returns 429 or 503 errors
- Agent found but insufficient data for scoring may return a partial or low-confidence score

## How this service works

MCP tool: verify AI agent identity and reputation score before inter-agent transactions.

## Output

Returns a boolean agent_verified field, a numeric reputation_score (0–100, higher is better), and a risk_level string (e.g. 'low', 'medium', 'high') indicating how trustworthy and safe the queried AI agent is.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "required": [
    "agent_id",
    "agent_name"
   ],
   "properties": {
    "agent_id": {
     "type": "string",
     "description": "Unique agent identifier"
    },
    "agent_name": {
     "type": "string",
     "description": "Human-readable agent name"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  },
  "sandbox": {
   "type": "object",
   "required": [
    "url"
   ],
   "properties": {
    "url": {
     "type": "string"
    },
    "curl": {
     "type": "string"
    },
    "note": {
     "type": "string"
    }
   }
  },
  "recovery": {
   "type": "object",
   "required": [
    "url"
   ],
   "properties": {
    "url": {
     "type": "string"
    },
    "curl": {
     "type": "string"
    }
   }
  },
  "documentation_url": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {
  "risk_level": "low",
  "agent_verified": true,
  "reputation_score": 95
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/limitguard-agent-identity-reputation-check-23fb269d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from limitguard.ai](https://www.zero.xyz/host/limitguard.ai/llms.txt)