# Delx Commerce Step Budget Plan

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

Splits a total millisecond time budget proportionally across ordered workflow steps using optional weights

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/step-budget-plan?utm_source=zero.xyz
- Price: $0.003/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-step-budget-plan-13c1e0cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rd9WhB7MMms4-zIrnq-xI

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-step-budget-plan-13c1e0cf -d '<json body>'
```

Example prompt: I have a 3-step agent pipeline — fetch, parse, and decide — with a total budget of 3000ms; can you split the budget so parse gets twice the time as the other two steps?

## When to prefer this

Choose this endpoint when an AI agent or orchestrator needs to programmatically split a known total latency or time budget across named pipeline stages with optional weighting — particularly useful for enforcing SLA-aware step-level timeouts in multi-step agent workflows. It is ideal over manual math when weights are uneven or step counts change dynamically.

## Known failure modes

- Missing or empty steps array returns an error
- Mismatched length between steps and weights arrays may cause incorrect allocation
- Non-numeric total_budget_ms causes a validation error
- Payment failure via x402 (insufficient USDC balance) blocks the request
- Zero or negative total_budget_ms produces undefined behavior

## 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 a plan array where each element includes the step name, its assigned weight, and its computed budget in milliseconds; also includes total step count, total budget in ms, and a schema identifier string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "steps": {
   "type": "array",
   "description": "Ordered workflow step names to allocate the total budget across."
  },
  "weights": {
   "type": "array",
   "description": "Optional relative weights aligned with steps; equal weights if omitted."
  },
  "total_budget_ms": {
   "type": "number",
   "description": "Total millisecond budget to split across steps."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "plan": [
   {
    "step": "fetch",
    "weight": 1,
    "budget_ms": 750
   },
   {
    "step": "parse",
    "weight": 2,
    "budget_ms": 1500
   },
   {
    "step": "decide",
    "weight": 1,
    "budget_ms": 750
   }
  ],
  "schema": "delx/util-step-budget-plan/v1",
  "step_count": 3,
  "total_budget_ms": 3000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-step-budget-plan-13c1e0cf/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)
