How it works

From fragmented data to one governed record.

IDWorthy links your robots' existing identifiers to one permanent identity, then maintains the record as evidence arrives—with human resolution wherever facts are contested.

Step 1

Reconcile the records

Bring together available manufacturer, serial, fleet, maintenance, and deployment data. Identify duplicates, gaps, and conflicts.

Step 2

Establish the record

Create a persistent IDWorthy identity and a controlled operational record for each in-scope robot.

Step 3

Link responsibility and evidence

Record who owns, operates, maintains, updates, or deploys the robot, with time-bound evidence.

Step 4

Maintain continuity

Preserve material changes across maintenance, configuration, software, transfer, handover, retirement, and controlled export.

Anatomy of an identity

One identity, standard representations.

Illustrative canonical UUIDv7-format example:

Canonical UUIDv7 text

019b8df2-7c35-7a14-8c95-6f26b73fd421

URN representation

urn:uuid:019b8df2-7c35-7a14-8c95-6f26b73fd421

Permanent resolver pattern

https://idworthy.com/id/{uuid}

Bitemporal history

Two clocks on every fact.

Every assertion records when it was true in the real world and when IDWorthy learned it.

Who was listed as operator on 1 March 2026?
What did we know about this robot on that date?
Was the transfer recorded before or after the incident?

Asserted valueNorthgate Facilities

SourceSigned fleet deployment agreement

Valid from2026-04-01

Recorded at2026-07-13

VerificationVERIFIED

AccessRestricted to authorized parties

Access model

Public identity. Permissioned everything else.

The platform never makes information public merely because it possesses it. Data is classified at field and evidence level.

Public

Approved identity fields

IDWorthy ID, entity class, approved manufacturer and model, and high-level status.

Authorized customer

Detailed operational record

Software versions, maintenance documents, relationships, and exports.

Restricted / security

Sensitive operational data

Exact locations, incident reports, credential metadata, and vulnerabilities.

For your engineers

A REST API that behaves like infrastructure.

OpenAPI 3.1 contracts, tenant-scoped authorization, idempotency keys, audit correlation IDs, and versioned schemas.

POST  /v1/entities
GET   /v1/entities/{id}
POST  /v1/entities/{id}/events
POST  /v1/evidence
GET   /v1/entities/{id}/record
GET   /v1/entities/{id}/export

Ready to reconcile your fleet's records?

Paid early-adopter pilots are designed for integrators and operators with 50 to 500 commercial or service robots.

Discuss a paid pilot See the Robot Operational Record