# SYS84 Ink Coverage Relay

> SYS84 Ink Coverage Relay is a paid API for AI agents from api.sys84.org, paid per call via x402, $0.003/call, status down (last checked 2026-10-12).

Relays IoT device data through a decentralized LoRaWAN/WiFi/BLE coverage network on the Ink blockchain and returns a cryptographic proof-of-relay

## Facts

- Endpoint: POST https://api.sys84.org/services/ink_coverage_relay/execute?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: down
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sys84-ink-coverage-relay-626261a8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aXdZsQtSPVL5jzq6Fey94

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 sys84-ink-coverage-relay-626261a8 -d '<json body>'
```

Example prompt: Relay this temperature sensor payload from device 'sensor-042' through the LoRaWAN coverage network on Ink chain and get me a proof-of-relay — the data object is {"temp": 23.4, "humidity": 61}.

## When to prefer this

Choose this endpoint when you need a cryptographic, blockchain-backed proof that an IoT device's data was relayed through a decentralized LoRaWAN, WiFi, or BLE coverage network on the Ink chain. It is especially suitable for use cases requiring tamper-evident relay receipts, decentralized network participation, or Ink chain integration — as opposed to centralized IoT platforms like AWS IoT or Azure IoT Hub that do not produce on-chain relay proofs.

## Known failure modes

- Invalid or missing device_id — returns validation error
- Malformed data payload object — returns schema error
- Unsupported coverage_type value — falls back to lorawan or returns error
- Ink chain congestion or node unavailability — relay fails with network error
- Insufficient USDC balance for the $0.003 per-call fee — payment rejected
- Relay timeout if device data exceeds network capacity constraints

## How this service works

Relay IoT device data through the decentralized coverage network on Ink chain — returns proof-of-relay

## Output

A proof-of-relay object returned by the Ink chain coverage network, cryptographically confirming that the specified IoT device's data payload was successfully relayed through the decentralized coverage infrastructure. Typically includes a relay receipt, transaction or commitment hash, timestamp, and confirmation of the coverage type used.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object",
   "description": "object payload to relay"
  },
  "device_id": {
   "type": "string",
   "description": "string IoT device identifier"
  },
  "coverage_type": {
   "type": "string",
   "description": "string optional lorawan/wifi/ble default lorawan"
  },
  "location_label": {
   "type": "string",
   "description": "string optional location hint"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sys84-ink-coverage-relay-626261a8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.sys84.org](https://www.zero.xyz/host/api.sys84.org/llms.txt)