{"id":"io.aeroz/aeroz","slug":"io-aeroz-aeroz","title":"Aeroz","description":"Prove a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody.","version":"0.2.0","publisher":{"kind":"domain","id":"aeroz.io","label":"aeroz.io","url":"https://aeroz.io"},"website":"https://aeroz.io","repository":"","remotes":[{"type":"streamable-http","url":"https://api.aeroz.io/mcp","headers":[{"description":"Aeroz API key (free sandbox key via POST https://api.aeroz.io/v1/signup). Not needed for get_passport and verify_passport_credential.","value":"Bearer {aeroz_api_key}","isSecret":true,"variables":{"aeroz_api_key":{"description":"Aeroz API key, starts with ak_. Free sandbox key via POST https://api.aeroz.io/v1/signup. Leave empty to use only the keyless tools.","isSecret":true,"placeholder":"ak_..."}},"name":"Authorization"}]}],"packages":[],"published":"2026-10-15","updated":"2026-10-15","status":"online","auth":"","latency_ms":1341,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"verify_chip","title":"Verify a chip","description":"Verify a physical item by its Aeroz chip: the UID plus whatever signature the tap carried. Same answer as GET /v1/verify. Use this before trusting any claim about a physical unit — a database record proves a record exists, not that the object in front of you is the one it describes. Read `proof` and `proves`: proof \"presence\" means the chip answered a fresh one-time SUN challenge (picc_data + cmac","read_only":false},{"name":"check_recall","title":"Check a recall","description":"Check whether a specific unit is subject to an active recall, from the register: reads only, verifies no signature and spends no chip answer. Returns known (on the register), recalled, and the recall reason, severity, date and id when one applies. recalled:null means the status is UNKNOWN (the UID is not on the register, or the register could not be read) — never report that as \"not recalled\". Thi","read_only":true},{"name":"dpp_readiness","title":"Passport readiness","description":"Assess how ready a product category is for an EU Digital Product Passport, against the delegated act that applies to it. Returns the required data fields, which are present, and which are missing. For batteries (category \"batteries\", or \"lmt\" / \"ev\" / \"industrial\" / \"stationary\") the assessment is against the Commission's 71 numbered data points: score, missing, not-required-yet, awaiting first re","read_only":true},{"name":"list_findings","title":"List compliance findings","description":"List findings raised by the Aeroz compliance agents watching this organisation — recall hits, DPP data gaps, regulatory changes, dwell anomalies, and clone detections. Use this to answer \"what needs my attention\".","read_only":true},{"name":"list_agents","title":"List agents","description":"List the Aeroz compliance agents available to this organisation and which are currently enabled. Use this to explain monitoring coverage or to find an agent worth enabling.","read_only":true},{"name":"get_usage","title":"Usage","description":"Return this organisation's Aeroz verification volume and outcome breakdown over a recent period. Use for reporting on scan volume, authentication failure rates, and trend. The buckets — authentic, recalled (any tap whose answer carried a recall, verified or not), mismatched (failed static or SUN signature), not_found, unverified (no or unchecked signature, test tag, held or disabled unit) and othe","read_only":true},{"name":"list_sandbox_chips","title":"List sandbox chips","description":"List the seeded sandbox chips for this organisation, with the UID and signature to pass to verify_chip, one per scenario: authentic, recalled, signature_mismatch (listed with a deliberately WRONG signature) and not_found (a UID that is not on the register). Sandbox only — use when building or testing an integration before physical chips ship.","read_only":true},{"name":"onboarding_status","title":"Onboarding status","description":"Report where this organisation stands in Aeroz onboarding: current stage, percentage complete, health, the single next action, and every open step with which side owns it. Use this to answer \"what do we still need to do\", \"why are we not live yet\", or \"what is Aeroz waiting on\". Steps marked side=\"aeroz\" are Aeroz's obligation, not the customer's — say so plainly rather than presenting them as hom","read_only":false},{"name":"onboarding_next_step","title":"Next onboarding step","description":"Return only the single most important next action and how to complete it. Use when the user asks what to do next and does not want the whole checklist.","read_only":false},{"name":"complete_onboarding_step","title":"Complete an onboarding step","description":"Mark a manual onboarding step complete on behalf of this organisation. Only steps the customer owns and that Aeroz cannot verify automatically can be set this way; an automatically verified step will refuse, because a self-report that contradicts the platform data is worse than no report. Pass the step key from onboarding_status.","read_only":false},{"name":"business_brief","title":"Business brief","description":"The full picture of this business as Aeroz holds it: declared product categories with their mandate dates and whether each date is fixed or provisional, onboarding state, open findings, and — importantly — which recall sources are NOT being monitored. Use this to orient before answering anything about the account. Never present an empty findings list as evidence of safety without also reporting co","read_only":false},{"name":"ask_agent","title":"Ask the Aeroz agent","description":"Ask this organisation's dedicated Aeroz agent a question in plain language and get a grounded answer. Use it for anything a human at the business would ask their account manager: \"what do we still need to do\", \"when is our deadline\", \"what is Aeroz waiting on\", \"what is not being monitored\", \"how do we go live\". It also looks up lots, units, holds and shipments (\"where is lot X\", \"which units of Y","read_only":false},{"name":"agent_conversation","title":"Agent conversation","description":"The recent conversation between this organisation and its Aeroz agent, across the dashboard, MCP and email. Use it to see what has already been asked and answered before asking again.","read_only":true},{"name":"create_shipment","title":"Create a shipment","description":"Register a shipment of physical items under a sensitivity profile so Aeroz can watch it in transit. Profiles: cold_chain (2–8 °C, mean kinetic temperature), frozen (≤ −15 °C), ambient_crt (15–30 °C, MKT ≤ 25), fragile (shock, tilt), high_value (light = container opened, dwell, chip-verified custody at every handoff), standard (movement only). Origin and destination need decimal-degree coordinates.","read_only":false},{"name":"shipment_status","title":"Shipment status","description":"Everything Aeroz holds about one shipment: profile and thresholds, status, items, custody events with their chip verification, the telemetry assessment (min/max/mean temperature, mean kinetic temperature, minutes out of range, peak shock, whether an excursion is open), the ranked routes, and open findings. Use for \"where is it\", \"is the cold chain intact\", \"was it ever opened\". An open excursion o","read_only":true},{"name":"list_shipments","title":"List shipments","description":"List this organisation's shipments, optionally by status (planned | in_transit | delivered | exception | cancelled).","read_only":true},{"name":"log_telemetry","title":"Log telemetry","description":"Record sensor readings for a shipment — position, temperature, humidity, shock, tilt, light, battery — up to 500 per call. Aeroz judges the whole recent stream against the lane's thresholds immediately and returns the assessment and any findings raised. A shipment in `planned` moves to `in_transit` on its first reading. Readings from a logger read out at the dock are accepted after `delivered` if ","read_only":false},{"name":"record_custody","title":"Record custody","description":"Record a custody event on a shipment: pickup, checkpoint, handoff, delivered, exception or note. Pass the chip `uid` (and `signature`) read at the handoff and Aeroz verifies it on the spot, turning a signature on a form into proof of presence. On a high_value lane a handoff without a verified chip raises a finding, and so does a chip that is not among the shipment's items (even an authentic one: `","read_only":false},{"name":"plan_route","title":"Plan a route","description":"Compute and rank routes for a shipment at a departure time, scored for its sensitivity profile: traffic-aware duration and delay, ambient heat or cold along the way against the lane's ceiling, and rain, snow or gusts. Lower score is better and only comparable within one computation. The best route is marked chosen. The response says plainly when routing or weather data was unavailable and the rank","read_only":false},{"name":"shipment_profiles","title":"Shipment profiles","description":"The sensitivity profiles Aeroz can judge a shipment against and the exact thresholds each applies, plus whether traffic and weather providers are configured for this deployment.","read_only":true},{"name":"bind_graded_item","title":"Bind a graded item","description":"Bind an Aeroz chip to a graded collectible slab (PSA, CGC, SGC, BGS, TAG). The chip UID, grader, cert number, grade and card identity are signed together, so the chip vouches for exactly this label: a label moved to another holder, or a cert reprinted on a copy, shows as \"binding broken\" on a buyer's tap. For PSA, the cert is cross-checked against PSA's own record when PSA_API_TOKEN is configured;","read_only":false},{"name":"graded_item","title":"Graded item","description":"A graded item as Aeroz holds it: grader, cert, grade, identity, whether the grader's own record matched, how many times it has been verified by tap, and its full provenance chain (sealed, sold, consigned, vaulted, shipped, verified…). Use for \"is this slab the one that was sealed\", \"where has it been\", \"has anyone tried to pass off a copy\". Report what this proves AND what it does not.","read_only":true},{"name":"record_provenance","title":"Record provenance","description":"Append an event to a graded item's chain: sold, consigned, vaulted, withdrawn, shipped, received, flagged, retired, note. Events are append-only and, when public, appear on the buyer's tap page. `flagged` marks the item and needs a `note` saying why. `retired` ends the binding (the slab was re-holdered or destroyed) and needs a `note` saying why: the chip stops vouching for any label and the grade","read_only":false},{"name":"list_graded_items","title":"List graded items","description":"List this organisation's chip-bound graded items, optionally by status (sealed | active | flagged | retired).","read_only":true},{"name":"my_section","title":"My section","description":"Return everything the Aeroz agent has built for this organisation: the regulatory calendar with only ADOPTED dates, the passport scaffold per product showing exactly which fields are missing, the identifier audit, the GS1 route, monitoring coverage, integration readiness, and the pre-filled audit scope. Each block carries a confidence — `computed` is derived from this account's own data and needs ","read_only":false},{"name":"trace_unit","title":"Trace a unit","description":"The whole history of one serialized unit: every custody hop from commissioning to dispensing, whether the append-only log has been tampered with, and what each regulation makes of it. Use this to answer \"where has this been\", \"who handled it\", \"is its record trustworthy\" and \"does this unit pass DSCSA / the EU passport rules\". Every failing check cites the clause it enforces — quote the clause, no","read_only":true},{"name":"find_unit","title":"Find a unit","description":"Resolve anything a scanner or a person can produce — a chip UID, a GS1 Digital Link URI, or a GTIN plus serial — to a unit, and return its history and verdicts. This is the tool for \"what is this thing in front of me\". An identifier that resolves to nothing is NOT the same as one that fails verification: the first means we have never seen it, the second means we have and it did not check out. Repo","read_only":true},{"name":"chain_readiness","title":"Chain readiness","description":"Sweep this organisation's units and report which regulatory checks are failing across the portfolio, how many units each affects, and examples to open. This is the tool for \"which of my units have a broken custody chain\", \"what is failing right now\", \"what will not pass on 18 February\" and \"how are we doing overall\". Counts are exact for the units swept; the response says when it hit its cap rathe","read_only":true},{"name":"get_passport","title":"Read a product passport","description":"Read the PUBLIC view of a published Digital Product Passport hosted by Aeroz, by its GS1 Digital Link (e.g. https://id.aeroz.io/01/09506000134352/21/ABC123) or its passport id (dpp_...). Returns the signed passport fields everyone may see, the version and its date, recall status and the item's links. Fields restricted to legitimate-interest roles (repairers, recyclers, purchasers and others, per t","read_only":true},{"name":"verify_passport_credential","title":"Verify a passport credential","description":"Check a passport credential (a vc+jwt issued by Aeroz) against Aeroz's published signing keys. Returns valid:true with the issuer, product id, passportVersion and validFrom when the signature checks out and the credential is an Aeroz Digital Product Passport, or valid:false with the reason (including \"revoked by the issuer\" and \"not an Aeroz passport credential\"). A valid result means Aeroz issued","read_only":true},{"name":"list_connectors","title":"List connectors","description":"The systems Aeroz can connect to (WMS, ERP, commerce, EPCIS). Each has a tier and `tier_means` in words: `live` moves data today, `credentials` only checks your sign-in, `bridge` needs an on-site agent, `guided` means an Aeroz engineer finishes the hookup. Do not describe a guided connector as automatic.","read_only":true},{"name":"list_integrations","title":"List integrations","description":"This company's connected systems, each with its `status` and `status_means`. Only `connected` is proven; `unverified` means stored but not yet proven, which is not the same as working.","read_only":true},{"name":"test_integration","title":"Test an integration","description":"Test one connected system now and return the real result, including the remote server's own error text. Changes its status to what the test proved. Pulls no data.","read_only":false},{"name":"list_webhook_endpoints","title":"List webhook endpoints","description":"This company's webhook endpoints: the address (query string hidden), the events each receives, and its health in words. Never shows a signing secret. Needs the `webhooks:read` scope.","read_only":true},{"name":"send_webhook_test","title":"Send a test webhook","description":"Send a signed `ping` to one webhook endpoint now and return the receiver's answer (HTTP status and body). A real request to the customer's address; it is not retried. Needs the `webhooks:write` scope.","read_only":false},{"name":"list_webhook_deliveries","title":"List webhook deliveries","description":"Recent webhook deliveries, newest first, each with every attempt and the receiver's answer. A `pending` delivery has a `next_attempt_at`: it is being retried, not lost. Needs the `webhooks:read` scope.","read_only":true},{"name":"list_webhook_events","title":"List webhook events","description":"Every event Aeroz can send to a webhook, with a description and an example payload (sample values from a fictional company, not real data), how deliveries are signed, and the retry schedule.","read_only":true},{"name":"list_products","title":"List products","description":"This company's registered products (archived ones left out). An empty list means recall watch has nothing to match against, not that all is clear.","read_only":true},{"name":"create_product","title":"Create a product","description":"Register one product, by the same rules as POST /v1/products. Recall watch needs a GTIN, NDC or UPC. Returns the passport gap for its category when there is one; that is a readiness signal, not a legal determination.","read_only":false},{"name":"import_products","title":"Import products","description":"Add or update many products at once, by the same rules as POST /v1/products/import: at most 5,000 rows, each row the fields of create_product. Send `dry_run: true` first: it checks every row and writes nothing. A real import writes nothing while any row has a problem. Each row comes back as create, update, unchanged or conflict.","read_only":false},{"name":"get_import_template_columns","title":"Import template columns","description":"The columns import_products reads, in the template's order, with the template's sample rows (a fictional company's products, not real data), the row limit and the rule for matching rows to existing products.","read_only":true},{"name":"search","title":"Search records and help","description":"Search this company's records the way the dashboard search bar does: products (name, SKU, GTIN, NDC), lots, units (chip ID, serial), tags (UID, EPC), shipments (reference, carrier, places), holds and cases, partners (name, GLN), locations, recalls, integrations and webhooks by name, plus Aeroz help topics. Paste an identifier as-is — a GTIN, NDC, GLN, lot, chip ID, GS1 Digital Link, element string","read_only":true},{"name":"list_ai_systems","title":"list_ai_systems","description":"This company's register of AI systems: each one's purpose, role under the EU AI Act, risk class (the company's own assessment), how a person can override it, and how many decisions are on record. Use it to find the system_id to log against.","read_only":false},{"name":"register_ai_system","title":"register_ai_system","description":"Register an AI system, by the rules of POST /v1/ai/systems. Name and purpose are fixed once registered. A high-risk system with no `oversight` is accepted with a warning (AI Act Art. 14). Classifying the system is the company's call; do not choose a risk class the user has not given you: leave it unassessed.","read_only":false},{"name":"record_ai_decision","title":"record_ai_decision","description":"Append a decision (or an incident) to an AI system's signed, append-only record, by the rules of POST /v1/ai/systems/{id}/records. Send the input and output text or their SHA-256: only the hash is kept, never the text. Nothing recorded can be edited or removed, so record what actually happened, not a guess.","read_only":false},{"name":"review_ai_decision","title":"review_ai_decision","description":"Record a person's review of an AI decision (approved, overridden or rejected; overriding or rejecting needs a `note`), by the rules of POST /v1/ai/records/{id}/review. Only call this with the decision a person actually made: never approve on your own judgement, because the record says a human reviewed it.","read_only":false},{"name":"where_is","title":"Where are these units","description":"Where a product's or a lot's units are, by last known place: sites, partners, scans and shipments in transit, each with how the place is known. Units with no recorded place are counted and listed, never placed. Give `product` (a product id), `lot`, or both.","read_only":true}],"server_info":{"name":"aeroz","version":"0.2.0","mode":"unauthenticated"},"category":"automation","tags":["ecommerce","agents","cloud"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-15","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/io-aeroz-aeroz/"}