Tool detail
digital-twin-sync
Merges local and remote scalar field-change lists by highest version per field and flags conflicts when equal versions differ.
Categories: Utilities
Use when
- resolve conflicting local vs remote IoT digital-twin field updates
- pick the newer value when two device state updates collide
Not for
- does not connect to a twin platform or merge nested documents
- does not resolve semantic conflicts, only reports them
Inputs
POST JSON body: { local_changes: [{field,value,version}], remote_changes: [{field,value,version}] } (both required, up to 10000 items each)
Inputs undocumented: type union outside Onelayer's profile
Endpoint
- Method
POST- URL
https://iot.halowerk.com/v1/digital-twin-sync
Payment
- Protocol
- x402
- Listed price
- 0.004 USDC per call on Base
- Payment method
- exact
- Network
- eip155:8453
- Asset
- 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Listed terms are catalog metadata. The caller supplies inputs and calls the tool outside Onelayer. If payment is required, the caller uses a compatible wallet to pay.
Source
- Directory
- Coinbase x402 Bazaar
- Record
- POST https://iot.halowerk.com/v1/digital-twin-sync
- Retrieved
- 2026-09-30T20:37:07.382Z
- Catalog file SHA-256
6837ccddf886f0007cf3727ea9d27faaa5047b51b4f425345c554ce1c271a524- Catalog built
- 2026-09-30T22:31:58.034Z