ASIN IP Risk

What this Actor does

Run deterministic Amazon ASIN trademark, patent, image-origin, VeRO, and dropship risk triage from an Apify Actor and push the explainable risk envelope to the default dataset.

Input example

{
  "asins": [
    "B0DCPN3VKW"
  ],
  "mode": "simple",
  "fulfillmentModel": "wholesale_supplier",
  "listingAssetPermission": "own_content"
}

Input fields

Provide one or more Amazon ASINs plus optional fulfillment model and listing asset permission.

• asins (array, user input): One or more Amazon Standard Identification Numbers.
• mode (string, user input): full returns the complete evidence envelope, simple returns only the dropship verdict.
• fulfillmentModel (string, user input): How the seller intends to source and ship.
• listingAssetPermission (string, user input): Whether the caller will use their own assets or has supplier or brand authorization.
• apiBaseUrl (string, optional override): Override of the upstream API base URL. Defaults to runtime.baseUrl from service.json.

Output dataset

Each dataset item is one ASIN risk verdict.

• asin: Amazon Standard Identification Number checked.
• validToDropship: True only when the deterministic verdict cleared every block rule.
• verdict: VALID or BLOCK.
• riskStatus: Deterministic risk tier.
• confidence: Confidence from 0 to 1.
• reasonCodes: Machine-readable rule identifiers.
• summary: One-sentence operator-facing explanation.
• blockingReasons: Human-readable reasons the listing was blocked.
• warnings: Non-blocking caveats about coverage or weak signals.
• providerCoverage: Per-provider coverage status.
• fullEvidenceAvailable: True when every required provider returned complete coverage.
• checkedAt: Timestamp the check was performed.

Developer notes

Set ASIN_IP_RISK_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API. Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json. For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.

Run locally

$apify run

Deploy

$apify push