# HumanMirror Fleet Consensus Lock

> HumanMirror Fleet Consensus Lock is a paid API for AI agents from humanmirror.fr, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-12).

Acquires a distributed consensus lock across an autonomous agent fleet, verifying coordinated agreement before a shared action proceeds.

## Facts

- Endpoint: POST https://humanmirror.fr/v1/fleet/consensus-lock?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/humanmirror-fleet-consensus-lock-e4ebf2ce
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_haqeWQXU4X3P2V-137Hba

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 humanmirror-fleet-consensus-lock-e4ebf2ce -d '<json body>'
```

Example prompt: Before my agent fleet proceeds with the shared database migration, acquire a consensus lock through HumanMirror to make sure all agents have agreed and the action is verified safe to execute — send it as a POST with a JSON body.

## When to prefer this

Use this endpoint when you need a distributed, verifiable consensus gate across a fleet of autonomous agents before a shared or irreversible action executes — particularly in multi-agent pipelines where race conditions, conflicting writes, or uncoordinated actions pose governance or safety risks. Prefer this over simple mutex or queue-based locking when trust verification and audit of agent agreement are required.

## Known failure modes

- Consensus not reached — fleet agents disagree, lock denied with non-ok status
- Malformed request body — missing required fields returns validation error
- Payment failure — insufficient USDC balance causes 402 rejection
- Timeout — fleet agents fail to respond within consensus window
- Duplicate lock attempt — re-submitting an already-held lock may return conflict status

## How this service works

HumanMirror est le control plane des agents autonomes : décision avant action, preuve après exécution, routage machine et gouvernance de flotte.

## Output

Returns a JSON object with an 'ok' boolean, a 'status' string (e.g. 'verified_success'), and a 'product' label confirming which HumanMirror product handled the lock. A successful response confirms the fleet consensus was achieved and the lock is granted.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "status": "verified_success",
  "product": "HumanMirror Next-Gen · Fleet Consensus Lock"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/humanmirror-fleet-consensus-lock-e4ebf2ce/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from humanmirror.fr](https://www.zero.xyz/host/humanmirror.fr/llms.txt)