# Delx Commerce — Seeded Percentage Rollout

> Delx Commerce — Seeded Percentage Rollout 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 decides whether a subject falls within a percentage rollout based on a seed and threshold, returning a boolean inclusion result and bucket percentage.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/seeded-percentage-rollout?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-percentage-rollout-056fdb2d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4TjNxHHDzY6jD5lcTgIZ3

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-percentage-rollout-056fdb2d -d '<json body>'
```

Example prompt: Check if user ID 'user_abc123' is included in a 20% rollout using 'feature-dark-mode-v2' as the seed.

## When to prefer this

Choose this endpoint when you need a deterministic, reproducible, and verifiable percentage-based bucketing decision — especially in agent workflows where auditability matters (evidence hash provided). Prefer over home-rolled hash logic when you need pay-per-use, no-signup access with cryptographic proof of computation. Ideal for gradual rollouts, feature flags, or A/B assignment where the same seed+subject pair must always produce the same result.

## Known failure modes

- Missing required fields (seed, subject, or percentage) returns a validation error
- Percentage out of 0–100 range may return an error or unexpected behavior
- Payment failure via x402 protocol results in 402 response before computation occurs
- Malformed input types (non-numeric percentage) cause schema validation failure

## 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 containing: `included` (boolean indicating if the subject falls within the percentage), `bucket_percent` (the computed hash percentage for the subject), `status` ('pass'), and an `evidence` block with `retained: false`, `input_sha256` (hash of inputs for verifiability), and `external_calls: 0` — confirming the computation was local and stateless.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "seed": {
   "type": "string",
   "maxLength": 8192,
   "description": "Seed supplied to Seeded Percentage Rollout; used only for this bounded calculation and processed in memory without retention."
  },
  "subject": {
   "type": "string",
   "maxLength": 8192,
   "description": "Subject supplied to Seeded Percentage Rollout; used only for this bounded calculation and processed in memory without retention."
  },
  "percentage": {
   "type": "number",
   "description": "Percentage supplied to Seeded Percentage Rollout; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "included": false,
   "bucket_percent": 18.47354188710196
  },
  "schema": "delx/util-seeded-percentage-rollout/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "81678a13647db7a4f1b151b8288397c3c5f872a52bed79342f44fc6eb2ea00fe",
   "external_calls": 0
  },
  "operation": "seeded_decision:seeded_percentage_rollout"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-seeded-percentage-rollout-056fdb2d/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)