# Agent Consensus

> Agent Consensus is a paid API for AI agents from agent-consensus.annushka1190.workers.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Aggregates votes or rankings from multiple agents using majority vote, weighted vote, plurality, agreement score, or Borda-style rank merge

## Facts

- Endpoint: POST https://agent-consensus.annushka1190.workers.dev/v1/agree
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-consensus-b1a4eed3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qcHL8ZeH-TMv3aK-Bf-RS

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 agent-consensus-b1a4eed3 -d '<json body>'
```

Example prompt: I have 5 agents that each voted on whether to approve this request — 3 said yes, 1 said no, 1 said maybe — can you run a majority vote and tell me the winner and vote share?

## When to prefer this

Use this endpoint when you have multiple AI agents or models producing independent outputs (votes, rankings, or scores) and need a principled aggregation — majority, weighted, plurality, agreement, or Borda merge — without managing your own voting logic. Prefer it over custom aggregation code when you need pay-per-use, account-free access in agent pipelines that already use x402 micropayments.

## Known failure modes

- Missing required 'type' or 'method' fields in input body returns validation error
- Malformed vote data (e.g. non-numeric weights) causes computation failure
- Ties in majority/plurality vote may result in ambiguous or null winner
- Payment not included or insufficient USDC triggers 402 Payment Required response
- Empty votes array produces undefined consensus result

## How this service works

Consensus utilities for multi-agent systems: majority vote, weighted vote, plurality counts, agreement score, and Borda-style rank merge. Pay-per-request USDC via x402. No API keys, no accounts.

## Output

Returns a JSON object with the winning candidate (e.g. 'winner': 'yes') and its share or score (e.g. 'share': 0.67), representing the consensus outcome of the specified voting or aggregation method across agent inputs.

## 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"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "const": "json"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "share": 0.67,
  "winner": "yes"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-consensus-b1a4eed3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-consensus.annushka1190.workers.dev](https://www.zero.xyz/host/agent-consensus.annushka1190.workers.dev/llms.txt)