# Agent Consensus – Plurality Vote

> Agent Consensus – Plurality 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-13).

Counts votes across agent responses to determine the plurality winner and its share of total votes.

## Facts

- Endpoint: POST https://agent-consensus.annushka1190.workers.dev/v1/vote/plurality
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-consensus-plurality-vote-6dffd588
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yFs2poSp-MJKaPpOXJHsS

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-plurality-vote-6dffd588 -d '<json body>'
```

Example prompt: I have 9 agent responses voting between 'yes', 'no', and 'maybe' — can you tally them up and tell me which option won by plurality and what share of votes it got?

## When to prefer this

Choose this endpoint when you need simple plurality counting — the option with the most votes wins regardless of whether it has a majority. Prefer it over majority-vote endpoints when you have more than two options and don't require a strict 50%+ threshold. Ideal for fast, lightweight vote tallying in agent ensembles without needing weighted scoring or rank-order aggregation.

## Known failure modes

- Missing or malformed 'input' body returns a validation error
- Empty vote set or tie handling may return unexpected winner or null
- Non-POST method returns 405
- Payment not completed via x402 results in 402 Payment Required response
- Malformed JSON body returns 400

## 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 float between 0 and 1 representing the winner's fraction of total votes, e.g. 0.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-plurality-vote-6dffd588/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)