# GENESIS Agent Assurance — Agent & MCP Readiness Check

> GENESIS Agent Assurance — Agent & MCP Readiness Check is a paid API for AI agents from genesis-agent-tools.genesisagenttools.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Validates whether an agent tool, API card, or instruction set is ready for autonomous agent and MCP use, returning readiness scores, evidence, and warnings.

## Facts

- Endpoint: POST https://genesis-agent-tools.genesisagenttools.workers.dev/api/flagships/agent-assurance?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/genesis-agent-assurance-agent-mcp-readiness-check-e45e07e8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dj7N7Tf5BLv2_smXKTESf

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 genesis-agent-assurance-agent-mcp-readiness-check-e45e07e8 -d '<json body>'
```

Example prompt: Run a quick agent-assurance check on this tool card for me — I want to know if it's MCP-ready, see any evidence collected, and get a list of warnings before I deploy it to my agent fleet.

## When to prefer this

Choose this endpoint when you need to validate whether an agent tool definition, API card, or set of agent instructions meets MCP and autonomous-agent readiness standards before deployment. It is specifically designed for the x402 agent tooling ecosystem and returns structured evidence and warnings, making it more appropriate than general-purpose linters or schema validators when the target is agent/MCP compatibility.

## Known failure modes

- Missing or malformed 'input' object returns validation error
- Invalid 'tier' value outside enum [quick, deep] causes rejection
- Empty tool/card/instructions fields may yield empty evidence and low-confidence results
- Payment failure via x402 prevents execution
- Ambiguous or overly brief text input may produce generic or inconclusive results

## How this service works

Pay-per-call x402 APIs for autonomous agents on Base USDC: API compatibility analysis, bounded HTTP/JSON workflows, URL evidence analysis, crypto price consensus, and agent/MCP readiness checks.

## Output

Returns a JSON object with an ok boolean, the tier used (quick or deep), a result object with readiness scores or flags, an evidence array of supporting observations, and a warnings array listing any issues found with the input tool or instructions.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tier": {
   "enum": [
    "quick",
    "deep"
   ],
   "type": "string"
  },
  "input": {
   "type": "object",
   "properties": {
    "card": {
     "type": "object"
    },
    "text": {
     "type": "string"
    },
    "tool": {
     "type": "object"
    },
    "instructions": {
     "type": "array"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tier": "quick",
  "result": {},
  "product": "agent-assurance",
  "evidence": [],
  "warnings": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/genesis-agent-assurance-agent-mcp-readiness-check-e45e07e8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from genesis-agent-tools.genesisagenttools.workers.dev](https://www.zero.xyz/host/genesis-agent-tools.genesisagenttools.workers.dev/llms.txt)