# Agent Consensus – Borda-Style Rank Merge

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

Merges multiple ranked lists from different agents into a single consensus ranking using a Borda-style algorithm, returning a winner and share score.

## Facts

- Endpoint: POST https://agent-consensus.annushka1190.workers.dev/v1/rank/merge
- Price: $0.005/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-borda-style-rank-merge-b6fa53c7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_P40DgFaQEpDQp0XW4xR3t

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-borda-style-rank-merge-b6fa53c7 -d '<json body>'
```

Example prompt: I have three agents that each ranked these five options differently — can you merge their rankings using Borda-style aggregation and tell me which option wins and with what share?

## When to prefer this

Choose this endpoint when you need to aggregate multiple ordered preference lists from different agents or sources into a single consensus ranking using Borda-count logic. It is ideal for multi-agent orchestration scenarios where several agents each produce a full ranking and you need a mathematically principled merge — as opposed to simple majority vote (use the majority-vote sibling endpoint) or weighted scoring. Prefer this when ranked order matters more than just pick frequency.

## Known failure modes

- Missing or malformed ranked lists in the request body returns a validation error
- Fewer than two ranked lists provided may produce trivial or undefined results
- Candidates appearing in some but not all rankings may cause partial Borda counts
- HTTP 402 if USDC payment via x402 is not attached or is insufficient
- Empty candidate sets or mismatched candidate names across lists cause aggregation errors

## 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 containing the consensus winner (the top-ranked candidate after Borda-style merging of all input ranked lists) and its share score (a float between 0 and 1 indicating how dominant the winner was across the aggregated rankings, e.g. {"winner": "option_A", "share": 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-borda-style-rank-merge-b6fa53c7/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)