Ourbits AgentBridge: Digital Product Passport Interoperability on UNTP

Digital Product Passports are becoming part of a broader shift in how product data moves across supply chains. The challenge is not just creating a passport. Most manufacturers already have the relevant data. It sits across ERP systems, PLM tools, MES platforms, certification databases, supplier systems, traceability tools, and internal documents. The harder problem is making those systems exchange trusted product data in a common, machine-readable way. That is the problem we are building Ourbits AgentBridge to solve.

Update — October 2026

The product passport landscape has moved quickly since this article was published:

• The UNTP public review has closed and the UNTP team is working through comments ahead of the version 1.0 release. The specification is already suitable for pre-production pilots.
• The EU Digital Product Passport Registry became operational on 20 July 2026, with sector-specific requirements for iron and steel expected in Q4 2026.
• The battery passport becomes mandatory on 18 February 2027 for EV, light means of transport, and industrial batteries above 2 kWh.
• CIRPASS-2 is running 13 lighthouse pilots across textiles, electronics, construction products, and tyres to validate DPPs in real settings at scale.

For a deeper look at why point-to-point integration fails and how a decentralized agent network addresses it, read The Interoperability Problem No Product Passport Platform Solves.

What is AgentBridge?

AgentBridge is an interoperability layer for product passports, traceability, conformity, and lifecycle data. Ourbits AgentBridge is designed to connect existing enterprise systems to an emerging network of verifiable product and supply-chain information without forcing companies to replace the systems they already use. Our architecture is built around the United Nations Transparency Protocol, or UNTP. The system is designed to work with core UNTP data structures such as:

1. Digital Product Passports
2. Digital Facility Records
3. Digital Traceability Events
4. Digital Conformity Credentials
5. Identity resolution
6. Decentralized access control
7. Verifiable credentials
8. Shared vocabulary and schema definitions

The goal is to turn these specifications into operational workflows that can run across independent organizations and software platforms.

Why another DPP platform is not enough

The market is already filling with tools that can generate DPP pages, create QR codes, or store compliance data. Those tools solve part of the problem. The bigger challenge comes after creation. A useful product passport has to interact with:

1. Manufacturer systems
2. Supplier data
3. Product master records
4. Certification evidence
5. Logistics and traceability events
6. Facility information
7. Repair and post-sale lifecycle events
8. Regulators and downstream partners

That creates an interoperability problem. If every company needs a custom integration with every other participant, product passport infrastructure will remain fragmented. AgentBridge is designed to reduce that dependency.

Bridging existing enterprise infrastructure

The architecture includes bridge layers for common enterprise and supply-chain systems. Examples include:

1. ERP product masters
2. MES batch records
3. PLM systems
4. IoT platforms
5. Procurement tools
6. National and commercial identity registries
7. GS1 and EPCIS environments
8. E-invoicing and commerce systems
9. Existing agent frameworks

The objective is bidirectional exchange. A manufacturer should be able to use data already present in an ERP or PLM system to generate or update structured product passport information. Verified product and conformity data should also be able to flow back into enterprise systems when required. The design document defines this as the Agent Bridge layer and treats it as a core adoption mechanism rather than an optional integration feature.

From static passports to machine-readable workflows

1. A passport should not end as a webpage behind a QR code.
2. Product data becomes more useful when systems can act on it.

AgentBridge is being designed around a network of specialized software agents. Some agents issue and validate product passports or verify conformity credentials. Others resolve product and organization identities, or trace product transformations and movements across facilities and jurisdictions. Another group keeps lifecycle data current by requesting missing evidence, reconstructing product provenance, and updating records as products are repaired, resold, or recycled. Finally, some agents assemble jurisdiction-specific compliance packs on demand.

These agents can collaborate across systems while keeping each participating organization in control of its own infrastructure and data.

Why UNTP

UNTP provides a useful foundation because it is designed around decentralized interoperability. It does not require one central database. Different organizations can issue and consume verifiable information independently. The architecture defines common structures for product passports, traceability events, facility records, conformity evidence, identity resolution, access control, and shared vocabulary. AgentBridge is intended to operationalize those concepts through executable software and enterprise integrations rather than treating them only as static data specifications.

Identity, trust, and access control

Supply-chain transparency does not mean making all data public. Commercial information, supplier relationships, pricing data, and compliance evidence often require controlled access. The AgentBridge design includes support for:

1. Verifiable credentials
2. Decentralized identifiers
3. Identity anchors
4. Role-based access
5. Encrypted credentials
6. Shared-secret access
7. Public and restricted data layers

This allows organizations to expose the right information to the right participant without creating a single shared data warehouse.

What this means for manufacturers

For manufacturers, the goal is practical. Your existing systems should not need to be replaced just because Digital Product Passports become part of your compliance or product data strategy. AgentBridge is being built so companies can use the infrastructure they already operate while making their product information more interoperable. A typical future workflow might look like this:

1. A batch is released in an ERP.
2. AgentBridge maps the relevant product and facility data to the correct structured schema.
3. Existing conformity evidence is discovered or requested.
4. A product passport is generated and validated.
5. The resulting information becomes discoverable by authorized downstream systems.
6. Later lifecycle events can update the same product history.

This is much closer to how real supply chains operate than manually maintaining standalone DPP records.

Part of the wider Ourbits platform

AgentBridge is one part of a larger Ourbits thesis. Ourbits is building infrastructure around continuity of product data across the lifecycle. That starts with ownership and warranty information through HoldMyBill and expands into product identity, resale, brand workflows, compliance, and eventually verified circularity records.

1. AgentBridge strengthens the B2B side of that architecture.
2. It gives manufacturers, software providers, auditors, logistics operators, and compliance platforms a way to exchange structured lifecycle information across organizational boundaries.

What comes next

The first implementation focus includes:

1. A versioned schema knowledge layer
2. Product Passport and Identity Resolver agents
3. Core credential generation and validation
4. Enterprise data bridges
5. Traceability and conformity workflows
6. Multi-organization pilot deployments

1. The long-term goal is not another closed DPP platform.
2. It is infrastructure that allows product, facility, conformity, and lifecycle data to move between systems with less custom integration and stronger verification.
3. Ourbits AgentBridge is our next step toward that goal.
4. Visit Ourbits to follow the release and pilot program.