# GENESIS Agent Tools — Release Readiness Check

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

Compares current and previous agent/MCP release states to produce a signed release decision with supporting evidence

## Facts

- Endpoint: POST https://genesis-agent-tools.genesisagenttools.workers.dev/api/release-readiness?utm_source=zero.xyz
- Price: $2.5/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-tools-release-readiness-check-ca43b318
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sAgh5QCxIqLM5-JxDTgtt

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-tools-release-readiness-check-ca43b318 -d '<json body>'
```

Example prompt: Can you run a release readiness check on my agent — here's the current build state and the previous build state — and tell me whether it's safe to release and what evidence supports the decision?

## When to prefer this

Choose this endpoint when you need a structured, signed, evidence-backed release decision comparing two agent or MCP server states — especially in automated CI/CD pipelines for autonomous agents where auditability and cryptographic attestation of the release verdict are required. Prefer over manual review when you need a pay-per-call, on-demand gate with no subscription overhead.

## Known failure modes

- Missing required 'current' or 'previous' fields returns a 400 validation error
- Malformed or non-object values for current/previous result in schema rejection
- Payment failure or insufficient USDC balance blocks the call with a 402 response
- Ambiguous or empty state objects may produce low-confidence decisions
- Network timeouts on the Cloudflare Worker may return 503

## 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 containing a cryptographic signature authenticating the response, a release_decision field (e.g. 'approved' or 'rejected'), and a release_decision_evidence object detailing the factors and reasoning behind the decision.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "current",
  "previous"
 ],
 "properties": {
  "current": {
   "type": "object"
  },
  "previous": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "signature": {
   "type": "string"
  },
  "release_decision": {
   "type": "string"
  },
  "release_decision_evidence": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/genesis-agent-tools-release-readiness-check-ca43b318/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)