What does “DPP as agentic infrastructure” mean?
A Digital Product Passport becomes agentic infrastructure when its persistent identity and governed data can be queried by authorized software agents, not only rendered as a compliance page for a person. The agent still needs permissions, provenance, confidence and tools; the DPP supplies a durable product context on which those controls can operate.
“Agentic infrastructure” is an architectural interpretation, not a term defined by the ESPR. A January 2026 SSRN working paper by Petteri Teikari and Neliana Fuenmayor articulated a related strategic framework for fashion and highlighted the limits of digitally verifying physical-world claims.
What does EU law actually require?
The ESPR requires the DPP to connect a data carrier to a persistent unique product identifier. Its data must be based on open standards and, where appropriate, be machine-readable, structured, searchable and transferable through an interoperable network without vendor lock-in. The applicable delegated act must define the dataset, access rights and whether the passport is at model, batch or item level.
The final textile delegated act is not yet a universal schema or item-level mandate. Agentic use must therefore be presented separately from legal requirements.
What technical layers make a passport useful to an agent?
- Persistent identity: a stable product, batch or unit identifier independent of a seasonal product page.
- Resolution: a carrier and resolver that can direct humans or machines to the appropriate resource.
- Governed data: structured facts with owner, source, effective date and evidence status.
- Access control: different views for consumers, partners, recyclers, authorities and internal agents.
- Deterministic checks: rules and calculations that an agent can invoke without improvising legal or business numbers.
- Authorized tools: explicit services such as care, support, repair, return or resale, gated by risk and permission.
How does Cycle apply this model today?
Cycle separates product identity, the governed catalogue record and the Digital Twin experience. It supports product, SKU, batch and optional serialized-unit references; DPP and consumer views; GS1 Digital Link-compatible identity construction; regulatory and product-data checks; and agent tools across web, iOS and Shopify.
This is applied product infrastructure, but it is not a claim that every physical assertion is independently verified or that autonomous agents already transact across every Twin. Evidence quality remains bounded by sources and assurance, while broader service execution is introduced through explicit, controlled tools.
What is real now versus the longer-term direction?
Real now: persistent product and optional unit identity, structured product records, resolvable Digital Twin experiences, DPP preparation, deterministic calculations and controlled agent actions. Direction: wider machine-to-machine discovery, richer assurance levels and agents that can initiate multi-step product services across organizations. The distinction matters because machine-readable data can exist today while trusted autonomous commerce remains an emerging operating model.