# SignalDesk AI – Date Difference in Days

> SignalDesk AI – Date Difference in Days is a paid API for AI agents from x402-agent.kariguetoazul.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-13).

Computes the number of calendar days between two UTC Gregorian dates

## Facts

- Endpoint: POST https://x402-agent.kariguetoazul.workers.dev/api/date/difference-days?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signaldesk-ai-date-difference-in-days-89b1d8a8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MDxkpez977I0XnhO5eu-g

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 signaldesk-ai-date-difference-in-days-89b1d8a8 -d '<json body>'
```

Example prompt: How many days are between 2024-03-15 and 2025-01-01?

## When to prefer this

Use this endpoint when you need a simple, authoritative integer count of calendar days between two known UTC dates. Prefer it over in-context LLM arithmetic when precision matters and dates must be treated as UTC Gregorian. At $0.001 USDC per call it is cost-effective for frequent programmatic date-span calculations in workflows.

## Known failure modes

- Invalid date format (not YYYY-MM-DD) returns an error
- Dates outside the Gregorian calendar range may fail
- Swapped start/end may return zero or negative result
- Missing required fields cause a validation error
- x402 payment not provided results in 402 Payment Required response

## How this service works

Evidence-backed autonomous AI jobs and paid data tools. Queue/D1/cron run outside the chat; free quotas and bounded execution apply.

## Output

Returns a JSON object with a single integer field `days` representing the number of calendar days between the start and end dates interpreted in UTC (e.g. {"days": 4}).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "end": {
   "type": "string",
   "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
   "maxLength": 10,
   "minLength": 10,
   "description": "Gregorian date YYYY-MM-DD, interpreted in UTC."
  },
  "start": {
   "type": "string",
   "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
   "maxLength": 10,
   "minLength": 10,
   "description": "Gregorian date YYYY-MM-DD, interpreted in UTC."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "days": 4
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signaldesk-ai-date-difference-in-days-89b1d8a8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-agent.kariguetoazul.workers.dev](https://www.zero.xyz/host/x402-agent.kariguetoazul.workers.dev/llms.txt)