For robotics integrators and fleet operators

One trusted operational record for every robot.

Reconcile fragmented robot records and maintain a controlled history across deployment, maintenance, software changes, responsibility, transfer, and handover.

Discuss a paid pilot See a sample record

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

Illustrative UUIDv7-format example · Meridian Robotics · MRD-40

● activerecord v41

Identity

Serial: SN 40-08812
GS1: (01) 09521234…
Cloud ID: iot:dev/mrd40
Fleet ID: NG-EAST-117

Responsibility

Owner: Axiom Leasing
Operator: Northgate Facilities
Maintainer: RoboServe GmbH
Since: 2025-08-14

Software & AI

Firmware: v4.2.1
Autonomy: nav-core 12.3
AI model: percept-lg-0625
SBOM: linked · sha256✓

Recent lifecycle events

2026-07-11software_updatedverified

2026-06-28maintenance_performedverified

2026-05-02component_replacedcorroborated

2025-08-14operator_changedverified

The problem

One robot accumulates disconnected identities.

Each system identifies the robot for its own purpose. None provides integrators and multi-vendor operators with one controlled record across deployment, maintenance, software, responsibility, transfer, and handover.

manufacturer serialmodel numberGS1 identifiercloud device IDfleet IDIoT device IDdigital twin IDcertificateregistration index

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

Illustrative canonical UUIDv7-format example. One permanent identity, issued once. Every operator, replacement, and software version links back to it.

The principle

The record evolves. The identifier never does.

An IDWorthy identifier is never reassigned—not after transfer, retirement, or decommissioning. Retired records continue to resolve instead of becoming broken links.

2024-03Manufactured

2024-08Sold & deployed

2025-02Autonomy stack updated

2025-11Ownership transferred

2026-04Sensor module replaced

2028-06Retired — identity resolves

019b8df2-7c35-7a14-8c95-6f26b73fd421illustrative UUIDv7-format example · unchanged through all of it

The product

The Robot Operational Record

Not another identifier, registry, or rating. A controlled, evidence-backed record that links fleet data, accountable parties, software history, maintenance, transfer, and lifecycle events around one permanent identity.

01 · Identity

Every identifier, linked

Serial numbers, GS1, cloud, fleet, and regulatory IDs mapped to one permanent IDWorthy identity.

02 · Responsibility

Who answers for this robot

Manufacturer, owner, operator, maintainer, and deployment organization—with validity periods and evidence.

03 · Software

What it runs, and since when

Firmware, autonomy stack, AI-model references, and configuration versions on a per-machine timeline.

04 · Lifecycle

Every intervention on record

Inspections, incidents, replacements, and work orders connected to evidence and provenance.

05 · Continuity

Manufacture to retirement

Sale, transfer, deployment, incident, suspension, retirement, and succession without identity reassignment.

06 · Trust

Claims you can check

Every assertion carries source, effective time, and verification status—never blurred.

Explore the full record →

Evidence, not assertion

Every claim carries its verification state.

IDWorthy distinguishes what is observed, corroborated, verified, and disputed—and preserves when a fact was true separately from when it was recorded.

Self-declared

Submitted by an originating party.

Observed

Ingested from a source, not independently verified.

Corroborated

Supported by more than one independent source.

Verified

Matches an authoritative source at a verification moment.

Disputed

Contested and routed to human resolution.

Resolver & API

Public identity. Permissioned data.

A permanent, login-free resolver can confirm identity while detailed responsibility, software, evidence, location, and security data stays restricted to authorized parties.

Read how it works →

Illustrative UUIDv7-format example · GET /v1/entities/019b8df2…/record

{
  "id": "019b8df2-7c35-7a14-8c95-6f26b73fd421",
  "class": "robot",
  "status": "active",
  "canonical": "019b8df2-7c35-7a14-8c95-6f26b73fd421",
  "verification": "permissioned"
}

Fleet identity and reconciliation pilot

Start with the fleet records you already have.

A paid early-adopter engagement for fleets of 50 to 500 commercial or service robots.

Discuss a paid pilot Explore the product