Can I screen an organization and review its matches with the Screening and Monitoring API?

Yes. Open a screening case for the organization, attach it as an association, then read the matches endpoint for that case to see the sanctions, watchlist, and adverse-media hits. You can record feedback on each match individually or update a batch of matches at once.

What are the rate limits for the Screening and Monitoring API?

The OpenAPI spec for the Screening and Monitoring API does not define rate limits. Check Dow Jones Developer Platform documentation for the current limits before running high-volume screening jobs.

Is there a Screening and Monitoring API MCP server?

You don't need an MCP server to give your agent the Screening and Monitoring API. Jentic connects it directly from the API Directory: import it, store the bearer token once, and your agent calls the screening operations it needs without another server's tool definitions loaded into its context.

Can I limit what my agent is allowed to do with the Screening and Monitoring API?

Yes. Write a rule that allows only the case-open and match-read operations for one case id path, so the agent can screen and read results but cannot delete cases or decorrelate associations, and every call it makes is logged. You choose which operations are in scope, so destructive ones are left out unless you add them.

How do I run a sanctions screening with the Screening and Monitoring API through Jentic?

Search Jentic with an intent like 'screen an entity against sanctions', and it returns the case-open operation with its input schema so the agent submits the entity and reads back the matches. To run it on your own infrastructure, install Jentic One from its GitHub repo.