Trade compliance, logistics, and cross-border commerce teams
Private beta · Curate route
Trade and sanctions guidance
Help trade systems retrieve the right official context while keeping jurisdiction and date boundaries explicit. Access is manually approved and configured for a bounded source, jurisdiction, and workflow scope.
Intended retrieval contract
One request. Bounded evidence.
Private-beta interface preview. Access is manually configured for the approved source and workflow scope. Review the current developer contract.
Which current restrictions affect exporting dual-use software to this destination?
jurisdictionauthorityprogrammeNo live result is shown. An approved collection must return bounded passages with citations, source metadata, and one immutable version.
The bounded job
Built for a retrieval problem, not a document dump.
Policy lookup, workflow assistance, and change alerts
Jurisdiction-filtered retrieval with immutable source versions
Intended source scope
Official sanctions programmes
Export-control guidance
Authority notices and amendments
Explicitly outside scope
Entity-screening decisions
Transaction approval
Non-public watchlists
United StatesEuropean UnionUnited KingdomUnited Nations
English first
ProgrammesGuidanceAmendments
Coverage and operations
Know what the private beta includes.
Evidence, coverage boundaries, and update targets define this private beta. They are not completeness or service-level promises.
The private-beta source map covers OFAC, EU, OFSI, and UN authority families, with a documented boundary between guidance retrieval and entity screening.
Access is configured for a guidance-focused workflow with source rights confirmed; sanctions screening and transaction decisions remain outside scope.
Official sanctions policy, guidance, legal acts, and amendments. Deterministic entity screening remains outside scope.
Research target: daily monitoring plus event-driven checks for authority notices. No screening service level is approved.
Named authorities
Rights status
Official-source terms and redistribution boundaries require individual review. Commercial list data is excluded without an agreement.
Provenance gate
Authority, regime, binding status, publication and effective dates, amendment chain, checksum, and official URL are required.
Shape the roadmap
Would this source boundary remove real work for your team?
Tell us the workflow, required sources, freshness, filters, and rights that would make it useful.