# Delx Commerce — Seeded Schedule Offset

> Delx Commerce — Seeded Schedule Offset 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).

Computes a deterministic, seed-based time offset in seconds within a given window, without retaining any input data.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/seeded-schedule-offset?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-schedule-offset-a2d6db20
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vJgoFlqm4IeUN_4a73haE

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-schedule-offset-a2d6db20 -d '<json body>'
```

Example prompt: Using the seed 'agent-42-task-daily' and a window of 3600 seconds, compute a deterministic schedule offset so I know exactly how many seconds into the hour this agent should fire.

## When to prefer this

Use this endpoint when you need a deterministic, reproducible time offset derived from a string seed — such as staggering agent tasks, adding consistent jitter to retries, or assigning fixed schedule slots without coordinating through a shared database. Prefer this over random jitter when reproducibility across runs is required, and over centralized schedulers when stateless, pay-per-call operation is preferred.

## Known failure modes

- Missing or empty seed string causes a validation error
- window_seconds not provided or non-integer returns a schema error
- Window value of zero or negative integer may produce undefined behavior
- Payment failure via x402 results in a 402 response before computation occurs

## 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 the computed offset_seconds (an integer within the specified window), the operation name, a status of 'pass', and an evidence block confirming no data was retained, the input SHA-256 hash, and that zero external calls were made. The cryptographic field indicates whether the offset was cryptographically derived.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "seed": {
   "type": "string",
   "maxLength": 8192,
   "description": "Seed supplied to Seeded Schedule Offset; used only for this bounded calculation and processed in memory without retention."
  },
  "window_seconds": {
   "type": "integer",
   "description": "Window Seconds supplied to Seeded Schedule Offset; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "cryptographic": false,
   "offset_seconds": 657
  },
  "schema": "delx/util-seeded-schedule-offset/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "ac21cc240f8bfa7f6189d1f827526efa86d3d89b30cd29f945605e73721556ca",
   "external_calls": 0
  },
  "operation": "seeded_decision:seeded_schedule_offset"
 }
}
```

## More

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