# 4SEC Crypto Price Alert Extend

> 4SEC Crypto Price Alert Extend is a paid API for AI agents from api.foursec.xyz, paid per call via x402, $0.01/call, status down (last checked 2026-09-15).

Extends the expiration time of an existing crypto price alert by adding up to 168 hours to its active duration.

## Facts

- Endpoint: GET https://api.foursec.xyz/price-alert/%7Bid%7D/extend
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/4sec-crypto-price-alert-extend-c72aeb9b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uJBVn8Qr0dj8pJUJAxkTq

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 4sec-crypto-price-alert-extend-c72aeb9b
```

Example prompt: Extend my 4SEC price alert with ID abc123 by 48 more hours so it keeps monitoring the token price without expiring.

## When to prefer this

Use this endpoint when you have an existing active price alert on the 4SEC platform and need to extend its active monitoring window without creating a new alert. This is preferable to deleting and recreating an alert when you want to maintain continuity of monitoring with the same alert ID and configuration.

## Known failure modes

- Invalid or non-existent alert ID returns an error status
- add_hours exceeds the 168-hour maximum, causing a validation error
- Alert already expired before extension request is processed
- Missing or malformed add_hours parameter causes a bad request error
- Payment failure via x402 protocol prevents the request from completing

## How this service works

Real-time multi-DEX aggregated crypto market data. Pay per request with USDC on Base via x402 protocol.

## Output

Returns a JSON object confirming the extension with the alert ID, the number of hours successfully added, the updated expiration datetime, and a status string indicating success or failure.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "add_hours": {
   "type": "integer",
   "description": "Hours to add (max 168)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "status": {
   "type": "string"
  },
  "alert_id": {
   "type": "string"
  },
  "added_hours": {
   "type": "integer"
  },
  "new_expires_at": {
   "type": "string",
   "format": "date-time"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/4sec-crypto-price-alert-extend-c72aeb9b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.foursec.xyz](https://www.zero.xyz/host/api.foursec.xyz/llms.txt)