# Agent Consensus – Weighted Vote

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

Aggregates weighted votes from multiple agents and returns the winning option along with its weighted share of the total vote.

## Facts

- Endpoint: POST https://agent-consensus.annushka1190.workers.dev/v1/vote/weighted
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-consensus-weighted-vote-37b0e862
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_h3SHwGBGel0rh1W4Xzl0M

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-weighted-vote-37b0e862 -d '<json body>'
```

Example prompt: I have five agents who all voted on whether to approve this transaction — three voted 'yes' with weights 0.8, 0.7, and 0.9, and two voted 'no' with weights 0.5 and 0.6. Run a weighted vote and tell me the winner and its share.

## When to prefer this

Choose this endpoint when agents have unequal trust or confidence levels and a simple majority vote would be misleading. Prefer weighted voting over plain majority vote when some agents are known to be more accurate, more recent, or more relevant to the decision. Ideal for ensemble AI systems, multi-model arbitration, and any scenario where vote sources carry different reliability scores.

## Known failure modes

- Missing required 'input' field returns a validation error
- Malformed vote entries or missing weights cause a 400-level error
- Tie votes may return an arbitrary winner or a tie indicator depending on implementation
- Empty vote list may return null winner
- Payment failure or insufficient USDC balance blocks the request via x402 flow

## 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 'winner' field (the winning option/label) and 'share' field (a float between 0 and 1 representing the winning option's proportion of total weighted votes, e.g. 0.67 means 67% of weighted vote mass).

## 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-weighted-vote-37b0e862/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)