Run OilFlow's Pre-Deal Compliance check on a proposed physical-commodity deal and get a clearance probability (0-100) and verdict tier (clear/review/heavy_friction/block) with named blockers and a restructure suggestion. NO API KEY REQUIRED: this is the full verdict, not a teaser. QUOTA: 5 verdicts per caller per 24 hours; on exhaustion the error is demo_limit_reached, which means the free allowance is used up and NOT that OilFlow is down. Returns receipt_id and verify_url, so the user can hand anyone a signed record of the check, and verdict_source ("claude" = full synthesis, "rule_based" = deterministic fallback) plus evidence_gaps: relay both, because a score without them overstates its own confidence. REQUIRED INPUTS: counterparty_name, counterparty_role (buyer or seller), product and origin_country; the verdict endpoint rejects a call missing any of them, so ask the user for the missing one rather than guessing a side. Decision-support estimating how a compliance desk is likely to treat the deal. Not a clearance and not legal advice; the response carries a disclaimer, pass it on. For the keyed version with no daily cap and the full input set, use predeal_check.

Independently verify an OilFlow screening receipt. NO API KEY REQUIRED. Given a receipt id (a UUID, from receipt_id/verify_url on a verdict, or from a receipt the user was handed), returns the receipt, its canonical payload string and an HMAC-SHA256 signature, so the user's own auditor can check it without trusting OilFlow's server at audit time. receipt_type says which kind of record it is: a sanctions_screen carries the list set it checked, a predeal_verdict carries the pre-deal tier plus the depth at which it consulted sanctions data. Read coverage back to the user: sanctions-only means PEP screening is not shipped, so a politically exposed person who is not also designated will not be flagged. Use this whenever a user has been HANDED a compliance receipt and wants to know whether it is genuine and what it actually covered.

Mint a free 30-day OilFlow sandbox API key (100 calls/day) scoped to the regulatory matrix and cluster endpoints, emailed to the address supplied. NO API KEY REQUIRED, which is the point: this is how an agent running keyless gets its user onto the keyed tools. CONSENT: requires the END USER'S email address and must only be called with their knowledge and agreement, because OilFlow emails the key and may send product follow-ups. Do not supply an address the user has not asked you to use. Limits: 3 keys per IP/hour, 5 per email/day. The sandbox scope does NOT cover kyc, ubo, lc or the keyed predeal endpoint; use predeal_preview for a free verdict, or https://oilflow.us/pricing for production access. Once the key arrives, set OILFLOW_API_KEY in this server's environment and restart it.

Run an OilFlow counterparty KYC screen: cluster-blocklist match, regulatory tradability, and the 7-step registration pipeline with 8-list sanctions screening (OFAC SDN, OFAC Consolidated, UN, EU, UK HMT, Canada SEMA, AU DFAT, Swiss SECO). PEP screening is NOT shipped — coverage is sanctions-only, so a politically exposed person who is not also designated will not be flagged; tell the user this. Sanctions/registration/asset/footprint steps run out-of-band and return as 'queued' with a poll_url. Returns a verdict (pass/review/fail) with per-check evidence. Decision-support for a compliance analyst, not a legal determination. Requires a production API key.

Check whether a given commodity can be supplied/bought from a given jurisdiction under OilFlow's 235-jurisdiction regulatory matrix. Returns allowed:true/false plus any blockers. Compiled regulatory guidance, not legal advice — confirm with the relevant national regulator before acting.

List every jurisdiction covered by the OilFlow regulatory matrix (235 jurisdictions). Returns a count and the country list with slugs for use in regulatory_check.

List the commodity/product categories the regulatory matrix recognizes (with their canonical labels), for use as the product argument to regulatory_check.

Look up a counterparty name against OilFlow's first-party-investigated Scam Cluster Intelligence Feed. Returns any matches with a severity: 'confirmed' (OilFlow-verified fraud), 'likely', or 'suspected' (publicly reported but NOT first-party confirmed — treat as a lead, verify the cited source). matched:false means no hit, which is not by itself an exoneration.

List entries from the Scam Cluster Intelligence Feed, optionally filtered by severity, country, or date. Useful for browsing known fraud clusters. Severity 'suspected' rows are publicly reported leads, not OilFlow-confirmed.

Validate a Letter of Credit presentation (LC + commercial invoice + bill of lading) against UCP 600 rules. Returns discrepancies with severity, an overall recommendation (honor/inquiry/refuse), and the UCP 600 articles cited. Requires a production API key (sandbox keys get 403). Output is DRAFT decision-support for a documentary-credit examiner — not a legal opinion.

Start a beneficial-ownership (UBO) graph traversal for an entity: walks ownership across registries, flags shell-company patterns, and screens nodes for sanctions exposure (8 lists; PEP is NOT screened). Applies the OFAC 50%-rule to derived ownership. Returns the cached graph immediately when available, otherwise a graph_id to poll with ubo_graph. Coverage caveat to pass on: there is no functioning US domestic UBO registry post-March-2025, so beneficial-ownership coverage is partial and every result says so. Flagged patterns are structural signals to review, not a verdict on any individual. Requires a production API key.

Fetch the status/result of a UBO graph build started by ubo_screen. Pass the graph_id returned when the screen was queued. Returns the graph nodes, ownership edges, aggregate risk, and flagged patterns once status is 'ready'.

Run a Pre-Deal Compliance Copilot check for a front-office originator: a sub-30s clearance probability (0-100) and verdict tier (clear/review/heavy_friction/block) for a proposed physical-commodity deal, with blockers, a restructure suggestion, and an estimated post-restructure clearance. Runs cluster, regulatory, adverse-media, sanctions, and verified-profile primitives. The response is self-describing about its own reliability: verdict_source is "claude" for a full synthesis or "rule_based" when the deterministic fallback ran, and evidence_gaps lists evidence sources that could not be consulted for this verdict — surface both to the user rather than presenting the score bare. Decision-support that estimates how compliance is likely to treat the deal — not a clearance itself and not legal advice; carries a disclaimer in the response. Requires a production API key; use predeal_preview for a free verdict without one.