---
name: api.aurelianflo.com
description: api.aurelianflo.com provides OFAC SDN wallet screening and structured DOCX report generation. It checks individual crypto wallet addresses against the U.S. Treasury SDN list and can produce formatted Word documents from structured compliance data. The host is oriented toward compliance workflows in crypto payment and onboarding contexts.
host: api.aurelianflo.com
---

# api.aurelianflo.com

This host serves compliance-focused agents and workflows that need to verify whether a crypto wallet address is sanctioned under OFAC programs and optionally produce audit-ready documentation. It offers two overlapping OFAC screening endpoints (one returning a screening memo with source freshness metadata, one returning match/clear status with entity metadata) and a DOCX generation endpoint for turning structured results into client-ready reports. It does not perform behavioral analysis, transaction graph analysis, or bulk screening.

## When to use this host

Use this host when an agent needs to perform per-address OFAC SDN screening before processing a crypto payment, onboarding a counterparty, or releasing funds — especially when an audit trail or formatted report is required. The two screening skills are functionally similar; prefer screen-ofac-wallet-address when an audit-ready memo with source freshness metadata is needed, and screen-ofac-sdn-wallet for lighter-weight status checks. Do not use this host for bulk address screening (no batch endpoint exists), fuzzy-name entity matching, transaction graph analysis, or PDF generation. For PDF output, a separate document generation service would be required. For behavioral or on-chain analytics, route to a dedicated blockchain intelligence provider.

## Capabilities

### OFAC SDN Wallet Screening

Checks a single crypto wallet address against the OFAC SDN list and returns hit/clear status, match count, sanctioned entity metadata, and sanctions program details. Two endpoints cover this function with slightly different output formats and audit metadata.

- **`screen-ofac-sdn-wallet`** — Checks a single crypto wallet address against the U.S. Treasury OFAC SDN list and returns match/clear status, sanctioned entity metadata, programs, and source freshness.
- **`screen-ofac-wallet-address`** — Screens a single wallet address against the OFAC SDN Advanced XML list and returns hit/clear status, match count, sanctioned entity metadata, and sanctions program details.

### Compliance Document Generation

Converts structured compliance data — such as screening results, headline metrics, and decision summaries — into a styled, editable DOCX artifact suitable for audit files, client delivery, or board review.

- **`generate-docx-report`** — Generates a styled, editable DOCX document from a structured report model including executive summary, headline metrics, tables, and metadata.

## Workflows

### OFAC Screening to Audit Report

*Use when an agent needs to screen a wallet address for OFAC sanctions and produce a formatted, audit-ready Word document capturing the screening result, entity metadata, and decision memo.*

1. **`screen-ofac-wallet-address`** — Screen the target wallet address against the OFAC SDN Advanced XML list to obtain hit/clear status, match count, sanctioned entity metadata, sanctions program details, and source freshness metadata.
2. **`generate-docx-report`** — Pass the screening result, entity metadata, and summary fields into the DOCX generator to produce a styled Word document suitable for compliance files or client delivery.

## Skill reference

### `screen-ofac-sdn-wallet`

**OFAC SDN Wallet Screening** — Checks a single crypto wallet address against the U.S. Treasury OFAC SDN list and returns match/clear status, sanctioned entity metadata, programs, and source freshness.

*Use when:* Use when an agent needs to determine whether a specific crypto wallet address appears on the OFAC SDN list before processing a transaction, onboarding a user, or releasing funds.

*Not for:* Do not use for bulk screening of many addresses in a single call; this endpoint screens one address at a time. Not a substitute for full compliance review — hits require human review before blocking or releasing funds.

**Inputs:**

- `address` (string, required) — The crypto wallet address to screen, embedded in the URL path (e.g. /api/ofac-wallet-screen/{address}).
- `asset` (string) — Optional asset or network ticker filter to narrow results. Accepted values include ETH, USDC, XBT, TRX, ARB, BSC, SOL, XRP, etc.

**Returns:** Returns success=true with a summary (status, matchCount, exactAddressMatch, manualReviewRecommended), an array of SDN match objects with entity name, aliases, programs, and listing date, source freshness metadata, and a structured compliance report object.

**Example:** `GET https://api.aurelianflo.com/api/ofac-wallet-screen/0x098B716B8Aaf21512996dC57EB0615e2383E2f96?asset=ETH`

---

### `screen-ofac-wallet-address`

**OFAC Wallet Screen** — Screens a single wallet address against the OFAC SDN Advanced XML list and returns hit/clear status, match count, sanctioned entity metadata, and sanctions program details.

*Use when:* Use when an agent needs to check whether a wallet address appears on the OFAC SDN list before processing a payment, onboarding a counterparty, or releasing funds — and requires an audit-ready screening memo with source freshness metadata.

*Not for:* Do not use for behavioral analysis, transaction graph clustering, or fuzzy-name entity screening; this performs exact-match address lookup only against OFAC-published digital currency designations.

**Inputs:**

- `address` (string, required) — The wallet address to screen, supplied as a path parameter in the URL. Accepts any digital currency address format (e.g., EVM hex, Bitcoin bech32).
- `asset` (string) — Optional asset or network ticker filter to narrow results. Supported values include ETH, USDC, XBT, TRX, ARB, BSC, SOL, XRP, and others covered by the SDN list.

**Returns:** Returns success=true with a summary (status, matchCount, exactAddressMatch, manualReviewRecommended), an array of SDN match objects with entity and program metadata, source freshness details, and a structured audit report.

**Example:** `GET https://api.aurelianflo.com/api/ofac-wallet-screen/0x098B716B8Aaf21512996dC57EB0615e2383E2f96?asset=ETH`

---

### `generate-docx-report`

**DOCX Report Generator** — Generates a styled, editable DOCX document from a structured report model including executive summary, headline metrics, tables, and metadata.

*Use when:* Use when an agent needs to produce a client-ready or board-facing Word document from structured report data such as decision memos, diligence reports, or board updates with formatted tables and section headings.

*Not for:* Do not use for read-only data retrieval or PDF generation; this endpoint produces a DOCX binary artifact only.

**Inputs:**

- `report_meta` (object, required) — Metadata for the report including title, author, language, report_type, and company_name.
- `result` (object) — Arbitrary result data object to include in the report body.
- `tables` (object) — Named table objects each with rows, columns, and an optional caption to render as formatted tables in the document.
- `chart_hints` (array) — Array of hints describing charts to include in the document.
- `export_artifacts` (object) — DOCX export options including filename, page layout, styling preset, TOC inclusion, and brand color usage.
- `headline_metrics` (array) — Array of headline metric objects to render prominently in the document.
- `executive_summary` (array) — Array of bullet strings or objects forming the executive summary section.

**Returns:** Returns success=true with a data object containing the DOCX fileName, MIME type, and an artifact with sizeBytes and a base64-encoded DOCX binary ready for download.

**Example:** `{"report_meta":{"title":"Board Update","author":"AurelianFlo","language":"en","report_type":"board-update","company_name":"AurelianFlo"},"tables":{"pipeline":{"rows":[{"stage":"Draft","status":"complete"}],"caption":"Pipeline Status (Current Snapshot)","columns":["stage","status"]}},"chart_hints":[],"headline_metrics":[],"executive_summary":[],"export_artifacts":{"docx_options":{"filename":"board-update-docx.docx","include_toc":false,"page_layout":{"margins_mm":{"top":20,"left":18,"right":18,"bottom":20},"orientation":"portrait"},"styling_preset":"board_branded","use_brand_colors":true}}}`

---
