# Bounty Engineer Structured Record Merge

> Bounty Engineer Structured Record Merge is a paid API for AI agents from bounty-engineer-x402-prod.onrender.com, paid per call via x402, $0.015/call, status unknown (last checked 2026-10-12).

Merges multiple structured data records by finding field-level consensus across sources and flagging conflicts where values disagree.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/structured-record-merge?utm_source=zero.xyz
- Price: $0.015/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bounty-engineer-structured-record-merge-b8747b57
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bqoAiRJcEwJ8S8ONTcucw

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 bounty-engineer-structured-record-merge-b8747b57 -d '<json body>'
```

Example prompt: I have 3 slightly different versions of the same company record from different sources — merge them into one canonical record, flag any conflicting field values, and require at least 2 sources to agree on a value before including it.

## When to prefer this

Choose this endpoint when you have 2–20 structured records representing the same real-world entity from different sources and need a programmatic, provenance-tracked consensus merge with explicit conflict reporting. It is especially valuable when you need to know not just the merged result but which sources agreed and where they disagreed, making it suitable for data quality pipelines, entity resolution workflows, and agent-driven deduplication tasks.

## Known failure modes

- Fewer than 2 records provided — merge cannot proceed
- More than 20 records submitted — exceeds maxItems limit
- min_sources set higher than the number of supplied records — no fields can merge
- All fields conflict across sources — merged record is empty
- Payment of 0.015 USDC not fulfilled — 402 response returned
- Malformed record structure — schema validation error

## How this service works

Machine-buyable infrastructure for autonomous agents: API cost routing, margin optimization, funding-rate data, webpage extraction, result verification, spend controls, retry planning, state, tender search and GitHub bounty intelligence.

## Output

Returns a merged record containing only fields where the required minimum number of sources agree, along with a list of conflicting fields where sources disagreed, a provenance map showing which sources contributed each field value, the total field count merged, conflict count, and any limitations of the merge approach.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "records": {
   "type": "array",
   "maxItems": 20,
   "minItems": 2
  },
  "min_sources": {
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "mode": "structured_record_merge",
  "merged": {
   "name": "Acme",
   "country": "GR"
  },
  "decision": "merged",
  "conflicts": [],
  "provenance": {
   "name": [
    "a",
    "b"
   ],
   "country": [
    "a",
    "b",
    "c"
   ]
  },
  "limitations": [
   "Merge uses exact value agreement across caller-supplied records. It does not decide which disagreeing source is factually correct."
  ],
  "min_sources": 2,
  "source_count": 3,
  "conflict_count": 0,
  "merged_field_count": 2
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-engineer-structured-record-merge-b8747b57/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bounty-engineer-x402-prod.onrender.com](https://www.zero.xyz/host/bounty-engineer-x402-prod.onrender.com/llms.txt)