Screen a vendor for OFAC sanctions and complete vendor due diligence and company verifi…
Screen a vendor for OFAC sanctions and complete vendor due diligence and company verification. This citation-first Vendor Risk Brief checks exact normalized names against current U.S. Treasury OFAC SDN and Consolidated primary-name and alias files, then adds…
by theartillerist.com · discovered, not yet claimed by its owner · updated 2026-10-06
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Screen a vendor for OFAC sanctions and complete vendor due diligence and company verification. This citation-first Vendor Risk Brief checks exact normalized names against current U.S. Treasury OFAC SDN and Consolidated primary-name and alias files, then adds GLEIF legal-entity records, SEC EDGAR company filings, and authoritative RDAP domain-registration evidence. It returns match status, vendor risk signals, identity gaps, domain-age signals, source URLs, evidence timestamps, confidence, and limitations for vendor onboarding, supplier risk, procurement, AML, and counterparty preflight. A name match requires human review; a no-match result is not sanctions clearance or a compliance determination.
Tags: vendor OFAC sanctions screening · vendor due diligence · company verification · OFAC primary and alias names · vendor risk assessment · bazaar
Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/26818.jsonfor the price and payment options. - Pay. Call
GET https://theartillerist.com/api/v1/intelligence/vendor-risk. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.025 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Calls (30d)
- 1 · 1 unique payers (third-party data from the public x402 Bazaar)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.025 | 0xf69586f5E0e5B3b105A1937364D8B299877c9735 | 60s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xf69586f5E0e5B3b105A1937364D8B299877c9735",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "25000",
"amountUsd": 0.025,
"maxTimeoutSeconds": 60
}
]Schemas
Output schema (JSON Schema)
{
"additionalProperties": false,
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://theartillerist.com/api/v1/intelligence/vendor-risk"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://theartillerist.com/api/v1/intelligence/vendor-risk");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://theartillerist.com/api/v1/intelligence/vendor-risk")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- theartillerist.com
- Endpoint
- https://theartillerist.com/api/v1/intelligence/vendor-risk
- Machine-readable
/resources/26818.json