Pricing & pilot

Priced like infrastructure, not software seats.

Implementation to get your fleet reconciled and identified, then a simple annual fee per active robot to keep every record maintained.

Phase 1 · early adopter

Fleet Identity and Reconciliation Pilot

Paid implementation for teams reconciling a defined fleet before ongoing identity maintenance.

Scoped feeImplementation engagement · 50–500 robots

✓ Fleet record import and reconciliation
✓ Persistent IDWorthy identity issuance
✓ Controlled operational record configuration
✓ Reconciliation report and implementation findings
✓ Optional lifecycle, dashboard, and API scope agreed for the pilot

Discuss a paid pilot

Phase 2

Fleet identity

Implementation plus annual identity maintenance.

Per active robotAnnual + implementation

✓ Import, cleaning, duplicate resolution, identity issuance
✓ Lifecycle record retention & change monitoring
✓ QR resolver hosting & record exports
✓ API access & support

Talk to us

Phase 3+

Enterprise

Tiered by fleet size, integrations, and verification depth.

CustomSubscription

✓ Higher robot counts, users, and API volume
✓ Extended retention & support levels
✓ Private resolver & white-label options
✓ Transfer and software traceability verification

Contact sales

What a pilot looks like.

Stage 1

Reconcile records

Bring together available fleet data and surface duplicates, gaps, and conflicts.

Stage 2

Establish identities

Issue persistent IDs and link existing identifiers for the agreed scope.

Stage 3

Configure operational records

Define responsibility, maintenance, lifecycle, export, dashboard, and integration scope.

Stage 4

Deliver findings and next steps

Provide the reconciliation report, implementation findings, and agreed next steps.

FAQ

Common questions

Is this another identifier we have to manage?

No. IDWorthy links the identifiers you already have to one permanent identity.

What happens when a robot is sold or retired?

The identifier is never reassigned. A retired robot returns a controlled retirement status.

Who can see our fleet's data?

Only approved high-level fields are public; detailed operational data is permissioned.

Does an IDWorthy record mean a robot is rated?

No. Identity, verification, ratings, and assurance are separate concepts.

How does data get into the record?

Through imports, the API, and authorized evidence workflows.

Do you support drones or industrial arms?

Not initially. The first scope is commercial and service robots.

Paid early-adopter engagement

Discuss your fleet reconciliation pilot.

For integrators, managed-fleet operators, and multi-vendor operators with 50 to 500 commercial or service robots.

Discuss a paid pilot