# Delx Commerce — Vesting Remaining Calculator

> Delx Commerce — Vesting Remaining Calculator 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 how many tokens have vested and how many remain unvested given a vesting schedule and evaluation timestamp

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/vesting-remaining?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-vesting-remaining-calculator-25b537a3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3iOAAypAVU_kIQfRkNaWt

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-vesting-remaining-calculator-25b537a3 -d '<json body>'
```

Example prompt: I have a token grant of 1000 tokens that started vesting on Jan 1 2024 and ends Jan 1 2026 — the cliff was July 1 2024. How many tokens have vested as of today and how many are still locked?

## When to prefer this

Use this endpoint when you need a fast, stateless, pay-per-call computation of token vesting progress without setting up a dedicated smart contract or on-chain query. Ideal for agents that need to evaluate vesting schedules dynamically at arbitrary timestamps, especially when integrating cliff logic. Preferable over on-chain queries when the vesting schedule parameters are known off-chain and you want a deterministic numeric result instantly.

## Known failure modes

- Missing required fields (total, start_ts, end_ts, now_ts) returns an error
- now_ts before start_ts may return 0 vested and full remaining
- now_ts after end_ts returns full vested and 0 remaining
- Invalid or non-integer timestamps cause parsing errors
- now_ts before cliff_ts returns 0 vested (cliff not yet reached)
- Payment failure via x402 results in 402 response without computation

## 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 the schema 'delx/util-vesting-remaining/v1' containing: 'vested' (number of tokens that have vested), 'remaining' (number of tokens still unvested), and 'fraction_vested' (decimal proportion of total that has vested, e.g. 0.4 means 40% vested).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "total": {
   "type": "number",
   "description": "Total token amount to vest"
  },
  "end_ts": {
   "type": "integer",
   "description": "Vesting end unix timestamp"
  },
  "now_ts": {
   "type": "integer",
   "description": "Evaluation unix timestamp"
  },
  "cliff_ts": {
   "type": "integer",
   "description": "Optional cliff unix timestamp"
  },
  "start_ts": {
   "type": "integer",
   "description": "Vesting start unix timestamp"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-vesting-remaining/v1",
  "vested": 400,
  "remaining": 600,
  "fraction_vested": 0.4
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-vesting-remaining-calculator-25b537a3/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)