# AgentResolver — 30-Day Managed Monitor for API, MCP & x402

> AgentResolver — 30-Day Managed Monitor for API, MCP & x402 is a paid API for AI agents from agentresolver.vercel.app, paid per call via x402, $19/call, status unknown (last checked 2026-10-16).

Continuously monitors whether AI agents can discover, call, and pay your API, MCP server, or x402 service over a 30-day window, returning health check results.

## Facts

- Endpoint: POST https://agentresolver.vercel.app/api/managed-monitor-30d?utm_source=zero.xyz
- Price: $19/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentresolver-30-day-managed-monitor-for-api-mcp-x402-d2ef4bd4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Di-S6mFsKyIbBsQB7OQPP

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 agentresolver-30-day-managed-monitor-for-api-mcp-x402-d2ef4bd4 -d '<json body>'
```

Example prompt: Set up a 30-day managed monitor called 'My Agent API' to continuously check that my API at https://myservice.example.com, my MCP server at https://mcp.myservice.example.com, and my x402 endpoint at https://pay.myservice.example.com are all discoverable, callable, and payable by AI agents.

## When to prefer this

Choose this endpoint when you need ongoing, automated 30-day health monitoring of an AI agent-facing API, MCP server, or x402 payment endpoint — particularly when you want continuous assurance that agents can discover, call, and pay your service rather than a single one-off check. Prefer the x402 Payment Preflight endpoint for a one-time pre-payment verification of a single x402 endpoint.

## Known failure modes

- Invalid or unreachable origin/MCP/x402 URL returns an error indicating the endpoint could not be reached
- Malformed URL (not matching https:// pattern) causes a validation error
- Missing all optional endpoint fields may result in an empty or partial health report
- Service unavailability on the monitored endpoint may cause check failures reported in the result
- Label exceeding 120 characters is rejected by schema validation

## How this service works

Continuously check whether AI agents can discover, call and pay your API, MCP server or x402 service. Free live checks and GitHub Action monitoring.

## Output

Returns a JSON object indicating the health status of the monitored endpoints across agent discoverability, callability, and payment readiness dimensions, covering the configured API origin, MCP server, and x402 endpoint over a 30-day monitoring window.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "label": {
   "type": "string",
   "maxLength": 120
  },
  "origin": {
   "type": "string",
   "pattern": "^https://",
   "maxLength": 500
  },
  "mcpEndpoint": {
   "type": "string",
   "pattern": "^https://",
   "maxLength": 500
  },
  "x402Endpoint": {
   "type": "string",
   "pattern": "^https://",
   "maxLength": 500
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentresolver-30-day-managed-monitor-for-api-mcp-x402-d2ef4bd4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentresolver.vercel.app](https://www.zero.xyz/host/agentresolver.vercel.app/llms.txt)