# Delx Commerce Seeded Pairing

> Delx Commerce Seeded Pairing is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Deterministically pairs a list of participants into matched pairs (with optional bye) using a seed value, returning verifiable, reproducible results.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/seeded-pairing?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-seeded-pairing-bc4f6b72
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hcp6PIk40ErUJ6HdPZiH9

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 delx-commerce-seeded-pairing-bc4f6b72 -d '<json body>'
```

Example prompt: Pair up these 5 players — Alice, Bob, Carol, Dave, and Eve — into tournament matchups using the seed 'round1-2024', and tell me who gets the bye.

## When to prefer this

Choose this endpoint when you need deterministic, reproducible, and verifiably fair pairings — especially when an audit trail matters (e.g. proving no post-hoc manipulation). It is ideal for tournament brackets, partner assignments, and any matchmaking scenario where the same seed + participant list must always yield the same result. Prefer it over ad-hoc random shuffles when reproducibility or verifiability is a requirement, and over complex matchmaking engines when the only constraint is seeded randomness.

## Known failure modes

- Participants list exceeds 256 items — request rejected
- Seed or participant string exceeds 8192 characters — validation error
- Empty participants list — undefined pairing behavior or error response
- Malformed JSON body — HTTP 400 bad request
- Payment not included or insufficient — HTTP 402 payment required

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

Returns a JSON object with a 'pairs' array of two-element arrays (each a matched pair), an optional 'bye' field naming the participant who sits out, an operation identifier, a schema version string, a status of 'pass', and an evidence block containing the SHA-256 hash of the input, a flag confirming no data was retained, and a count of zero external calls — enabling full verifiability of the result.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "seed": {
   "type": "string",
   "maxLength": 8192,
   "description": "Seed supplied to Seeded Pairing; used only for this bounded calculation and processed in memory without retention."
  },
  "participants": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 8192
   },
   "maxItems": 256,
   "description": "Participants supplied to Seeded Pairing; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "bye": "b",
   "pairs": [
    [
     "d",
     "a"
    ],
    [
     "c",
     "e"
    ]
   ]
  },
  "schema": "delx/util-seeded-pairing/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "0bfb1a13590bf6beabbd01835232e976edb6c53d8cd2ab2a61049c2b2b57645a",
   "external_calls": 0
  },
  "operation": "seeded_decision:seeded_pairing"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-seeded-pairing-bc4f6b72/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from commerce.delx.ai](https://www.zero.xyz/host/commerce.delx.ai/llms.txt)
