# Agent Consensus – Majority Vote

> Agent Consensus – Majority Vote 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).

Determines the majority winner from a set of agent votes and returns the winning option with its share percentage.

## Facts

- Endpoint: POST https://agent-consensus.annushka1190.workers.dev/v1/vote/majority
- 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-majority-vote-68cfeafc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aNdgtlKoLMqeV5eeW3P23

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-majority-vote-68cfeafc -d '<json body>'
```

Example prompt: I have 10 agents that each voted on whether to approve a transaction — 7 said 'yes', 3 said 'no'. Can you run a majority vote and tell me which option won and by what share?

## When to prefer this

Use this endpoint when you need a simple, stateless majority-vote aggregation across agent outputs without managing your own voting logic. It is ideal for multi-agent orchestration pipelines where you want to resolve disagreement between an odd or even number of agents cheaply ($0.003/call) and without API keys. Prefer this over weighted vote or Borda merge when all agents carry equal authority and you only need the plurality winner with its share.

## Known failure modes

- Missing or malformed 'input' body causes validation error
- Tie between top candidates may result in undefined or arbitrary winner selection
- Empty votes array may return an error or null winner
- Payment failure via x402 protocol results in 402 response and no result
- Malformed JSON body returns a 400-level error

## 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 'winner' (the option that received the most votes) and 'share' (a decimal between 0 and 1 representing the fraction of total votes the winner received, e.g. 0.67 for 67%).

## 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-majority-vote-68cfeafc/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)