# Delx Commerce — Carry-to-Spot Price Calculator

> Delx Commerce — Carry-to-Spot Price 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-02).

Derives the implied spot price from a futures/mark price by backing out the carry (funding) over a given delivery horizon.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/carry-to-spot?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-carry-to-spot-price-calculator-80577517
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r7ppyOHiICNsZHei3KfFE

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-carry-to-spot-price-calculator-80577517 -d '<json body>'
```

Example prompt: The BTC futures mark price is $101,000 with an annualized carry rate of 18% and 30 days to delivery — what's the implied spot price?

## When to prefer this

Use this endpoint when you need a quick, trustless, pay-per-use computation to derive implied spot price from futures/mark price and a known carry (funding) rate, especially in agent workflows where no signup or API key management is desired. Prefer it over manual formula implementation when you want verifiable, on-chain-settled micro-payments (USDC on Base/Solana) and a canonical schema-versioned response. Not suitable for scenarios requiring real-time live price feeds — this is a pure mathematical derivation from inputs you supply.

## Known failure modes

- Missing required fields (days, future, carry_apr) returns an error response
- Non-positive days value may produce nonsensical or error output
- Carry rate passed as a percentage instead of a decimal (e.g. 18 instead of 0.18) produces wrong implied spot
- Payment failure via x402 protocol blocks the call
- Invalid JSON body returns 400-level error

## How this service works

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

## Output

A JSON object containing the schema identifier ('delx/util-carry-to-spot/v1') and a single numeric field 'implied_spot' representing the derived spot price, e.g. {"schema":"delx/util-carry-to-spot/v1","implied_spot":100.5866302864939}.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "days": {
   "type": "integer",
   "description": "Days to delivery or horizon"
  },
  "future": {
   "type": "number",
   "description": "Futures/mark price"
  },
  "carry_apr": {
   "type": "number",
   "description": "Annualized carry rate as decimal"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-carry-to-spot/v1",
  "implied_spot": 100.5866302864939
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-carry-to-spot-price-calculator-80577517/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)