Back to Aeroz
Card snapshot
api.aeroz.io
·
2026-10-31 08:22:41 UTC
·
24924c4c8e75cdc3ac51072b57a611506c181f723cd3ccdefc7ae8e34c2893d6
This is a frozen copy of the agent's agent-card.json as we observed it at the timestamp above. We capture a new snapshot every time the card's content hash changes. Useful for: forensic drift analysis, verifying downstream callers see the right version, reproducing routing decisions made historically.
{
"name": "Aeroz",
"description": "Physical-world trust layer: item authentication, recall watch, transit monitoring with route optimisation, EU DPP readiness, and a per-business compliance agent.",
"url": "https://api.aeroz.io/mcp",
"provider": {
"organization": "Aeroz",
"url": "https://aeroz.io"
},
"version": "0.2.0",
"documentationUrl": "https://api.aeroz.io/docs",
"capabilities": {
"streaming": false,
"pushNotifications": false,
"stateTransitionHistory": false
},
"authentication": {
"schemes": [
"bearer"
],
"credentials": "Aeroz API key \u2014 POST https://api.aeroz.io/v1/signup"
},
"defaultInputModes": [
"application/json",
"text/plain"
],
"defaultOutputModes": [
"application/json"
],
"skills": [
{
"id": "verify",
"name": "Physical item authentication",
"description": "Verify that a physical item is the one its record describes: a factory-locked NFC/RFID chip UID plus a cryptographic signature, checked against the manufacturer's record. Four outcomes \u2014 authentic, recalled, signature_mismatch, not_found \u2014 and no product data on a failed signature.",
"tags": [
"is this item genuine",
"is this product counterfeit",
"verify NFC tag",
"verify chip signature",
"proof of presence",
"anti-counterfeit check",
"authenticate a physical product",
"slab authentication",
"verify a graded card"
],
"examples": [
"is this item genuine",
"is this product counterfeit",
"verify NFC tag",
"verify chip signature"
]
},
{
"id": "recall",
"name": "Recall watch",
"description": "Whether a specific unit, GTIN, NDC or lot is subject to an active recall, checked against openFDA (drug, device, food), FDA firm announcements and EU Safety Gate \u2014 and an honest statement of which sources are NOT monitored.",
"tags": [
"is this lot recalled",
"recall check",
"FDA recall lookup",
"EU Safety Gate RAPEX",
"is it safe to dispense",
"can I ship this batch"
],
"examples": [
"is this lot recalled",
"recall check",
"FDA recall lookup",
"EU Safety Gate RAPEX"
]
},
{
"id": "transit",
"name": "Products in motion \u2014 cold chain, fragile and high-value transit",
"description": "Track shipments against a sensitivity profile: temperature excursions and mean kinetic temperature on cold-chain and frozen lanes, shock and tilt on fragile ones, light (container opened) and chip-verified custody on high-value ones; silence and dwell on all. Routes ranked on traffic and weather for the lane.",
"tags": [
"cold chain monitoring",
"temperature excursion",
"mean kinetic temperature",
"MKT",
"shipment tracking",
"chain of custody",
"route optimization traffic weather",
"is my shipment still moving",
"was the container opened",
"GDP compliant transport",
"DSCSA transaction history"
],
"examples": [
"cold chain monitoring",
"temperature excursion",
"mean kinetic temperature",
"MKT"
]
},
{
"id": "dispatch",
"name": "Cairn by Aeroz \u2014 planning a legal day",
"description": "Plan a whole day's jobs across drivers and trucks without proposing anything illegal. Driver hours are judged by the market's own law \u2014 UK assimilated 561/2006 and the Working Time Regulations, US FMCSA 49 CFR 395, UAE labour law and the emirate truck bans \u2014 and the drive to the pickup counts as driving, because the law counts it. Every verdict carries the rule pack and version that produced it, the limits, the before and after numbers, and what it could not assess. A refusal says what would unlock it. A distance we do not hold is a refusal, never a guessed zero. Committing a plan turns every move into an Aeroz shipment under the profile its load calls for, so temperature, stops and silence are watched from the moment the day is committed \u2014 Cairn plans the move, Aeroz proves it.",
"tags": [
"drivers hours compliance",
"tachograph rules",
"EU 561/2006 driving time",
"FMCSA hours of service",
"11 hour driving limit",
"14 hour window",
"is this driver legal for this job",
"daily driving limit 9 hours",
"45 minute break",
"Abu Dhabi truck ban hours",
"Dubai truck curfew",
"haulage dispatch planning",
"reduce empty running",
"deadhead miles",
"which driver can take this load",
"why was this job subcontracted"
],
"examples": [
"drivers hours compliance",
"tachograph rules",
"EU 561/2006 driving time",
"FMCSA hours of service"
]
},
{
"id": "chain",
"name": "Track and trace \u2014 custody, proven and provable",
"description": "One serialized unit, its whole history, and a verdict on it. Every hop \u2014 commissioned, packed, shipped, received, dispensed, repurposed \u2014 is an append-only event with no update path, hash-linked to the one before it, so an altered or deleted event is detectable by anyone who recomputes the chain, without trusting Aeroz. Rule packs judge that history against the regulation that applies: DSCSA (product identifier, unbroken custody, authorized trading partners, transaction data, saleable returns, recall containment) and the EU Digital Product Passport (EN 18219 identifier, EN 18223 header, granularity lineage, delegated-act fields, carrier reachability, identifier persistence). Every check cites the clause it enforces and every verdict says, in words, that it is a readiness signal and not a legal compliance determination. One trace call returns the history, the tamper check, every pack's verdict and the map path.",
"tags": [
"track and trace",
"chain of custody",
"DSCSA compliance check",
"EPCIS events",
"where has this product been",
"product journey",
"serialized unit history",
"authorized trading partner check",
"saleable returns verification",
"was this dispensed after a recall",
"unbroken chain of custody",
"tamper evident audit log",
"prove the audit log was not edited",
"battery passport lineage",
"granularity change traceability",
"second life battery passport",
"traceback drill",
"simulate a supply chain"
],
"examples": [
"track and trace",
"chain of custody",
"DSCSA compliance check",
"EPCIS events"
]
},
{
"id": "collectibles",
"name": "Graded collectibles \u2014 the slab, made unforgeable",
"description": "Bind a factory-locked chip to a PSA, CGC, SGC, BGS or TAG slab so the chip vouches for exactly that grader, cert, grade and card. A buyer taps with any phone and sees one of five words: authentic, signature mismatch (a copied chip), binding broken (a real chip on the wrong label), not found, not public \u2014 plus the provenance chain. Cross-checks PSA certs against PSA's own record. Does not grade, and says so.",
"tags": [
"verify a PSA slab",
"is this graded card real",
"fake PSA slab check",
"counterfeit slab detection",
"label harvesting",
"card provenance",
"slab authentication NFC",
"verify cert number",
"trading card authentication",
"crack and resubmit"
],
"examples": [
"verify a PSA slab",
"is this graded card real",
"fake PSA slab check",
"counterfeit slab detection"
]
},
{
"id": "dpp",
"name": "EU Digital Product Passport readiness",
"description": "Which data fields the delegated act for a product category requires, which a product has, which are missing, and when the mandate binds \u2014 with provisional dates marked provisional. A readiness signal, not a legal determination.",
"tags": [
"digital product passport",
"DPP readiness",
"ESPR delegated act",
"EU battery regulation passport",
"GS1 Digital Link",
"are we ready for DPP",
"what passport fields are missing"
],
"examples": [
"digital product passport",
"DPP readiness",
"ESPR delegated act",
"EU battery regulation passport"
]
},
{
"id": "agent",
"name": "A dedicated compliance agent per business",
"description": "Every organisation gets an agent that knows its onboarding state, categories, mandate dates, coverage and obligations, and answers questions from that data \u2014 computed where it can, screened where a model composes, and declined where it does not know.",
"tags": [
"what do we still need to do",
"when is our deadline",
"what is Aeroz waiting on",
"compliance status",
"onboarding next step"
],
"examples": [
"what do we still need to do",
"when is our deadline",
"what is Aeroz waiting on",
"compliance status"
]
},
{
"id": "integrations",
"name": "WMS / ERP connectors and webhooks",
"description": "SAP S/4HANA, NetSuite, Manhattan, Blue Yonder, EPCIS 2.0, generic REST and EDI X12 connectors; signed webhooks on every finding.",
"tags": [
"connect SAP to verification",
"EPCIS events",
"webhook on recall",
"ERP integration for traceability"
],
"examples": [
"connect SAP to verification",
"EPCIS events",
"webhook on recall",
"ERP integration for traceability"
]
},
{
"id": "catalog",
"name": "Product catalog and bulk import",
"description": "Register products by GTIN, NDC, UPC or SKU, or import up to 5,000 at once with a dry run first; each change notifies subscribed webhooks.",
"tags": [
"import my product catalog",
"bulk upload products",
"register a product for recall watch"
],
"examples": [
"import my product catalog",
"bulk upload products",
"register a product for recall watch"
]
}
],
"interface": {
"protocol": "mcp",
"endpoint": "https://api.aeroz.io/mcp",
"card": "https://api.aeroz.io/.well-known/mcp.json"
}
}