Cycle Intelligence

Use this tool when a company or user asks WHAT the EU Digital Product Passport (DPP) requires, WHEN it becomes mandatory, which ESPR/AGEC/French milestones apply to textile or fashion products, or whether the DPP is already obligatory. Returns the verified regulatory timeline (dates as of today), the mandatory data fields a textile DPP needs, and honest notes on what is in force vs pending delegated acts. Deterministic, no account needed. Informational, not legal advice.

{
  "type": "object",
  "properties": {
    "sector": {
      "type": "string",
      "description": "Optional sector hint (textile, fashion, beauty, fmcg). Default textile."
    }
  }
}

Use this tool when a company needs to know whether its product catalogue is READY for the EU Digital Product Passport (DPP/ESPR): pass an array of products (any reasonable JSON shape: name, sku, description, brand, composition/material, country of origin, supplier, care instructions...) and get a rule-based readiness score 0-100 per product plus the exact missing fields, and an aggregate with the single field that unlocks the most products. INPUT: array of product objects (flexible keys). OUTPUT: per-product score, ready flag, missing field labels; aggregate with top_missing_fields and unlock_hint. Deterministic rule-based validation (ESPR mandatory field set). Up to 200 products per call. No account needed.

{
  "type": "object",
  "properties": {
    "products": {
      "type": "array",
      "description": "Products to validate. Flexible keys accepted: name/title, sku, description, brand/vendor, composition/material/fabric, country/origin/manufacturing_country, supplier, care/care_instructions, compliance, certifications.",
      "items": {
        "type": "object"
      }
    }
  },
  "required": [
    "products"
  ]
}

Use this tool to verify a GTIN/EAN barcode number (check digit, GS1 mod-10) or a GS1 Digital Link URL (the QR standard behind Sunrise 2027 retail QR codes and DPP data carriers). Returns whether the identifier is valid, the normalised GTIN-14, and the exact error if not. Use it before printing labels or QR codes so they conform to GS1. Deterministic, no account needed.

{
  "type": "object",
  "properties": {
    "gtin": {
      "type": "string",
      "description": "GTIN/EAN-8/12/13/14 to validate."
    },
    "digital_link": {
      "type": "string",
      "description": "GS1 Digital Link URL to validate (e.g. https://id.example.com/01/09506000134352/21/SER123)."
    }
  }
}

Use this tool when an organisation wants to CREATE live Digital Product Twins in Cycle from its product data (after validating with validate_dpp_readiness). INPUT: array of products (same flexible shape as validate_dpp_readiness). OUTPUT: per product, a persistent id and a LIVE twin URL (scannable product page), plus DPP readiness and missing fields. Requires an organisation API key (Authorization: Bearer). Up to 100 products per call.

{
  "type": "object",
  "properties": {
    "products": {
      "type": "array",
      "items": {
        "type": "object"
      }
    }
  },
  "required": [
    "products"
  ]
}

Use this tool to issue the Digital Product Passport of a twin created with create_product_twin. Cycle validates conformance FIRST (ESPR mandatory field set) and REFUSES to create an incomplete passport - if fields are missing it returns exactly which ones. OUTPUT: the DPP dataset + its public URL. EU registry submission happens the moment the EU opens it for textile (Cycle is integrated and in approval as service provider). Requires an organisation API key.

{
  "type": "object",
  "properties": {
    "product_id": {
      "type": "string"
    },
    "sku": {
      "type": "string"
    }
  }
}

Use this tool to generate the printable data carrier (QR content) of a twin: a GS1 Digital Link URL (Sunrise 2027 standard) if you pass a valid GTIN, or a serialized twin URL fallback without one. The URL resolves to the product's live twin the moment it is created - it is connected, not a loose QR. Invalid GTINs are rejected before printing. Requires an organisation API key. OPTIONAL: pass allocation={channel|retailer, shipment?, region?, units?} to link the serial to its intended retail channel (channel-aware serialization: future scans of that unit resolve their channel, always labelled INFERRED).

{
  "type": "object",
  "properties": {
    "product_id": {
      "type": "string"
    },
    "sku": {
      "type": "string"
    },
    "gtin": {
      "type": "string"
    },
    "serial": {
      "type": "string"
    },
    "allocation": {
      "type": "object",
      "description": "optional intended retail channel: {channel, retailer, shipment, region, units}"
    }
  }
}