Revor Company Research

Produce a practical company background report. Anchor it in the company's official public identity, then add customs and contact evidence when they can be matched reliably.

Keep research narration out of the final answer. Reply directly in chat with the findings; do not create a report file or artifact.

Critical customs-routing rule: a request for a company's export activity normally establishes company-role=exporter; it does not establish that the provider exports catalog is the right coverage directory. Keep the subject role fixed and apply the user's HS/product/origin/destination filters during candidate verification. Company-candidate lookup compares both catalogs by default when company-role is supplied. Set --compare-catalogs false only for a deliberate single-catalog probe. Never silently switch the paid report route.

Choose one execution route

If Revor MCP tools are available, use revor_research_public_web, revor_customs_company_candidates, revor_customs_full_report, revor_find_contacts, and revor_get_job. Generate one stable idempotency_key for each new executing call, reuse it only for an exact retry, and poll returned jobs to a terminal state. Skip the local configuration preflight on this route.

Otherwise run the sibling script scripts/revor-api.mjs for every Revor data call. Resolve its path relative to this SKILL.md; do not rewrite its HTTP logic with inline JavaScript or curl. The bundled client requires Node.js 18 or newer. The investigation flow below applies to both routes; its command examples show the bundled-client form.

Mandatory configuration preflight

When using the bundled-client route, run the following command exactly once at the start of every research task, before public-web or any other data command: