Sanctions Screening API
Trademo Technologies Inc · Software Development
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 8 captures on record
What the publisher says
As described on Microsoft Marketplace.
Introduction
Trademo Sanctions Screener API uses advanced data engineering, AI-powered Machine Learning and the latest NLP technologies to track 500+ sources including government websites, federal authorities, international watchlists, and trade authorities from around the world to offer accurate sanctions data through our API. The objective of this API document is to explain the structure and features of the Sanctions Screening API. The goal is to allow screening of the trading partners, vendors, suppliers, customers or employees which could be a person, company or a vessel.
Show the rest of the publisher’s description (12 more lines)
Sanctions Screening API allows screening against the several Sanctions Lists published by different authorities and bodies globally to prevent risk and ensure compliance.
Name matching in sanctions screening is quite difficult. Our algorithms check for translation & transliteration challenges to ensure that the sanctions data you receive is accurate, authentic, and up-to-date. With over 500+ sources, Trademo Sanctions Screening API is one of the best sources for global sanctions screening including everything from US OFAC sanctions to global maritime sanctions, all in one place. Further Our sanctions data is updated every hour using our smart data sourcing algorithms to ensure that your sanctions screening process is sound.
Denied Party Screening Lists Provided by Trademo Sanctions Screener
- OFAC Sanctions
- Civil Penalties & Enforcements
- Anti-Bribery and Corruption
- Banking & Investment Sanctions
- Health & Human Service Sanctions
- Maritime Sanctions
- End User Sanctions
Link to Documentation
https://docs.google.com/document/d/1XoQYUrmi3JcTFTMptcEmz6eMfRLJSgAUq2pHaQTVi9o/edit#heading=h.vscaccjoqqs7
Preview
2 images
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Vendor
External enrichment · as of 2026-08-29
Sources
Publisher resources
2 linksLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.