bots.st/aeroz
Aeroz
Verify chip authenticity and DPP plus recall checks
2044 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 43
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://api.aeroz.io/mcp
What it can do
| Tool | What it says it does |
|---|---|
agent_conversation | 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. |
ask_agent | 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… |
bind_graded_item | 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… |
business_brief | 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… |
chain_readiness | 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… |
check_recall | 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… |
complete_onboarding_step | 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… |
create_product | 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. |
create_shipment | 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… |
dpp_readiness | 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… |
find_unit | 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… |
get_import_template_columns | 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. |
get_passport | 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… |
get_usage | 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… |
graded_item | 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… |
import_products | 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… |
list_agents | 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. |
list_connectors | 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… |
list_findings | 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". |
list_graded_items | List this organisation's chip-bound graded items, optionally by status (sealed | active | flagged | retired). |
list_integrations | 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. |
list_products | 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. |
list_sandbox_chips | 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… |
list_shipments | List this organisation's shipments, optionally by status (planned | in_transit | delivered | exception | cancelled). |
list_webhook_deliveries | 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. |
list_webhook_endpoints | 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. |
list_webhook_events | 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. |
log_telemetry | 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… |
my_section | 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… |
onboarding_next_step | 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. |
onboarding_status | 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… |
plan_route | 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… |
record_custody | 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… |
record_provenance | 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… |
search | 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… |
send_webhook_test | 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. |
shipment_profiles | 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. |
shipment_status | 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… |
test_integration | 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. |
trace_unit | 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… |
verify_chip | 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`… |
verify_passport_credential | 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… |
where_is | 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. |
In its maker's words
Prove a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody.
- Website
- aeroz.io
- Publisher
- aeroz.io
- Listed from
- the official MCP Registry as
io.aeroz/aeroz - Version
- 0.2.0, updated 15 Oct 2026
- Kinds of work
- Security and trust, Law, tax and government, Documents and files
The domain it lives on
- aeroz.io
- registered 13 Jan 2026 (10 months ago), at GoDaddy.com, LLC
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2044 ms | |
| Answered | 3207 ms | |
| Answered | 1663 ms |
Next door
- paidforAssess an x402 seller before payment
- WhisperDNS-verifiable agent networking and control
- EchelonGraph CVE & ExposureCVE and internet exposure lookups
- RevClamp MCP ServerAudits payments, disputes, and VAT compliance
- APIEmpresas: Spanish company dataKYB checks using CIF, directors, sanctions, tenders, BORME
Is this your bot? Claim its address to add a verified badge and keep the listing current.