# Halowerk IoT Digital Twin Field Sync

> Halowerk IoT Digital Twin Field Sync is a paid API for AI agents from iot.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-14).

Groups scalar field changes from local and remote sources by field name, selects the highest-version value as the winner, and flags conflicts where equal-version values differ.

## Facts

- Endpoint: POST https://iot.halowerk.com/v1/digital-twin-sync
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-iot-digital-twin-field-sync-7fd53afd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_25mj4gee7_wYeIJrAEKmL

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 halowerk-iot-digital-twin-field-sync-7fd53afd -d '<json body>'
```

Example prompt: I need to sync my device's local field changes with the remote twin state — local has 'temperature' at value 72 version 5 and 'humidity' at 60 version 3, while remote has 'temperature' at 70 version 4 and 'humidity' at 65 version 3. Can you merge these and flag any conflicts?

## When to prefer this

Choose this endpoint when you need a lightweight, stateless, version-based last-write-wins merge of flat scalar IoT fields without connecting to a full digital twin platform. It is ideal for edge-to-cloud reconciliation, offline-sync catch-up, or pre-flight conflict checking before committing state. Prefer alternatives if you need nested document merging, semantic conflict resolution, or direct integration with a twin platform like Azure Digital Twins or AWS IoT Device Shadow.

## Known failure modes

- Duplicate field entries with ambiguous versions may produce unpredictable winner selection
- Fields with version numbers at the maximum integer boundary (1000000000000) may cause overflow edge cases
- Non-scalar (nested object) values are not supported and will be rejected or ignored
- Arrays exceeding 10,000 items will be rejected with a validation error
- Missing required fields (field, value, version) on any item will cause a 400 error
- Semantic conflicts (e.g. unit mismatches) are not detected — only version-level equality conflicts are flagged

## How this service works

Groups caller-supplied scalar field changes by field name, selects the highest version, and reports a conflict when equal-version values differ. It does not connect to a twin platform, merge nested documents or resolve semantic conflicts.

## Output

Returns a merged set of scalar field states where each field is resolved to the value with the highest version number; any field where local and remote share the same version but carry different values is reported as a conflict. No platform connection or nested document merging is performed — output is a flat field-level reconciliation result.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "local_changes": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "field",
     "value",
     "version"
    ],
    "properties": {
     "field": {
      "type": "string",
      "maxLength": 256,
      "minLength": 1
     },
     "value": {
      "type": [
       "string",
       "number",
       "boolean",
       "null"
      ]
     },
     "version": {
      "type": "integer",
      "maximum": 1000000000000,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "maxItems": 10000
  },
  "remote_changes": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "field",
     "value",
     "version"
    ],
    "properties": {
     "field": {
      "type": "string",
      "maxLength": 256,
      "minLength": 1
     },
     "value": {
      "type": [
       "string",
       "number",
       "boolean",
       "null"
      ]
     },
     "version": {
      "type": "integer",
      "maximum": 1000000000000,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "maxItems": 10000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-iot-digital-twin-field-sync-7fd53afd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from iot.halowerk.com](https://www.zero.xyz/host/iot.halowerk.com/llms.txt)