# Bounty Engineer Record Deduplication API

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

Deduplicates an array of records by one or more key fields, returning only unique records and reporting which duplicates were found and kept based on a first/last strategy.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/record-dedupe?utm_source=zero.xyz
- Price: $0.003/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-record-deduplication-api-b7680adc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_folVFcYJJ8jgm6SgVa1kx

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-record-deduplication-api-b7680adc -d '<json body>'
```

Example prompt: Deduplicate these 3 records by their 'id' field using the 'first' strategy: [{"v":1,"id":"A"},{"v":2,"id":"A"},{"v":3,"id":"b"}] — keep the first occurrence of each duplicate and return only the unique ones.

## When to prefer this

Use this endpoint when an AI agent needs to deduplicate structured JSON records on-the-fly as part of an automated pipeline, especially when paying per-call via x402/USDC is acceptable and no persistent database deduplication layer is available. Prefer this over in-agent logic when you need SHA256-verified key matching and a clear audit trail of which duplicates were found.

## Known failure modes

- Missing or empty 'records' array returns an error
- Missing 'keys' array causes deduplication to fail
- Invalid strategy value (not 'first' or 'last') returns a validation error
- Malformed JSON in records array causes parse failure
- Payment not included or insufficient USDC results in 402 response
- Very large record arrays may hit payload size limits

## 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 JSON object with ok:true, the keys used, the strategy applied, a list of unique records, the count of inputs/uniques/duplicates, and an array of duplicate pairs each containing the kept index, duplicate index, and SHA256 hash of the key value. Duplicates may be truncated if very large.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "keys": {
   "type": "array"
  },
  "records": {
   "type": "array"
  },
  "strategy": {
   "enum": [
    "first",
    "last"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "keys": [
   "id"
  ],
  "mode": "record_dedupe",
  "strategy": "first",
  "duplicates": [
   {
    "kept_index": 0,
    "key_sha256": "ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb",
    "duplicate_index": 1
   }
  ],
  "input_count": 3,
  "unique_count": 2,
  "unique_records": [
   {
    "v": 1,
    "id": " A "
   },
   {
    "v": 3,
    "id": "b"
   }
  ],
  "duplicate_count": 1,
  "duplicates_truncated": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-engineer-record-deduplication-api-b7680adc/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)