How itsmerockyfiles/argusapi works
Argus is an OFAC sanctions-list screening API. Clients submit entity details; the HTTP server applies optional RapidAPI proxy authentication, screens the in-memory SDN records, and returns ranked matches. Separate API branches expose record lookup, health and dataset statistics, while an authenticated rebuild operation refreshes the feed and reloads the store. The README documents XML-to-JSON dataset generation, but the generated data directory is absent from the supplied tree; its artifact is shown without a source path. The rebuild and dataset-generation behavior is supported by the sampled builder and server code.
Main entry points: server.js Express API · store.js Memory Store · screen.js Screening Engine · build-sdn.js Feed Builder
Components 11
HTTP API
- Express API
src/server.js - Proxy Auth
src/middleware/rapidApiAuth.js - API Entry
api/index.js - Structured Logger
src/logger.js
Screening
- Screening Engine
src/screen.js - Input Errors
src/errors.js
SDN Data
- Memory Store
src/store.js - SDN Dataset
- Feed Builder
scripts/build-sdn.js
Other components
- API Client
- OFAC Feed
Connections 13
- API Client → Express API: sends requests
- API Entry → Express API: exports app
- Express API → Proxy Auth: guards routes
- Express API → Screening Engine: screens query
- Screening Engine → Input Errors: throws errors
- Screening Engine → Memory Store: reads entries
- Express API → Memory Store: reads stats and records
- Express API → Feed Builder: triggers rebuild
- Express API → Memory Store: reloads data
- Feed Builder → OFAC Feed: downloads XML
- Feed Builder → SDN Dataset: writes dataset
- Memory Store → SDN Dataset: loads dataset
- Express API → Structured Logger: logs requests and errors