What input does Jev Listing Policy-Risk Monitor — Marketplace Rules require?

records and policy are required. A further 2 inputs are optional. The full input schema, with types and defaults, is below.

Does Jev Listing Policy-Risk Monitor — Marketplace Rules need an API key or login?

Yes — typesafeApiKey is marked secret and must be supplied by you. Nothing else in the input schema needs credentials.

How do I run Jev Listing Policy-Risk Monitor — Marketplace Rules?

It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.

Jev Listing Policy-Risk Monitor — Marketplace Rules

Flag unsupported or policy-risk claims in supplied listing text using a buyer-defined policy and TypeSafe Jev.

Jev Listing Policy-Risk Monitor — Marketplace Rules returns 8 documented output fields, including index, sourceId, listing, violationProbability and severity. Every field carries a declared type, a written description and an example value. 21 runs are recorded on Apify.

Run it on ApifyPay per result · no subscription

8: Output fields
4: Inputs
21: Runs
2026-10-16: Last run

01 — output

What it returns

Every field the extractor writes to its dataset, with its type, a written description and an example value.

Field	Type	What it holds	Example
index	string \| number \| boolean \| array \| objectnull	Position of this row within the run.	1
sourceId	string \| number \| boolean \| array \| objectnull	Identifier of the input record this row came from.	rec_01
listing	string \| number \| boolean \| array \| objectnull	Listing as recorded for this row.	[]
violationProbability	string \| number \| boolean \| array \| objectnull	Violation Probability as recorded for this row.	[]
severity	string \| number \| boolean \| array \| objectnull	How severe this row is judged to be.	2
reviewRequired	string \| number \| boolean \| array \| objectnull	Review Required as recorded for this row.	[]
judgments	string \| number \| boolean \| array \| objectnull	The full structured judgement returned by the model.	{"stance":{"choice":"recommended"}}
model	string \| number \| boolean \| array \| objectnull	Identifier of the model that produced the judgement.	jev-latest

02 — sample

One record

Assembled from the example values declared on the schema above, not invented at render time.

{
  "index": 1,
  "sourceId": "rec_01",
  "listing": "[]",
  "violationProbability": "[]",
  "severity": 2,
  "reviewRequired": "[]",
  "judgments": "{\"stance\":{\"choice\":\"recommended\"}}",
  "model": "jev-latest"
}

03 — input

What you give it

Input	Type	Description
records	arrayrequired	Rows containing listing text.
policy	stringrequired	The explicit policy to assess against.
typesafeApiKey	stringoptional	Secret — supply your own value.
maxItems	integeroptional	Hard cap on enriched rows.

04 — run

Run Jev Listing Policy-Risk Monitor on your own input

It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.

Open on Apify ↗

Also in ai, ecommerce

05 — questions

Asked before running it

8 of 8 fields described

What does Jev Listing Policy-Risk Monitor — Marketplace Rules return?: It returns 8 documented output fields: index, sourceId, listing, violationProbability, severity, reviewRequired, judgments and model. Each field declares its type, a description of what it holds, and an example value.
What input does Jev Listing Policy-Risk Monitor — Marketplace Rules require?: records and policy are required. A further 2 inputs are optional. The full input schema, with types and defaults, is below.
Does Jev Listing Policy-Risk Monitor — Marketplace Rules need an API key or login?: Yes — typesafeApiKey is marked secret and must be supplied by you. Nothing else in the input schema needs credentials.
How do I run Jev Listing Policy-Risk Monitor — Marketplace Rules?: It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.