PG1

PG1 reference

Sanctions screening

Before PG1 takes any payment, quotes against a named wallet, or runs a paid job, it checks the paying wallet against two public sanctions lists. This covers per-call x402 payments, A2A jobs, Tool Foundry builds and tool calls, and watchlists.

Sources

ListOfficial sourceLicenceUpdate cadence
OFAC Specially Designated Nationals and Blocked Persons (SDN) list, digital currency addresseshttps://sanctionslist.ofac.treas.gov/Home/SdnListUS government work (public domain)Synced into PG1's sanctions table by the existing sanctions sync
EU consolidated list of persons, groups and entities subject to EU financial sanctionshttps://webgate.ec.europa.eu/fsd/fsf/public/files/xmlFullSanctionsList_1_1/content?token=dG9rZW4tMjAxNw (dataset: https://data.europa.eu/data/datasets/consolidated-list-of-persons-groups-and-entities-subject-to-eu-financial-sanctions)Free reuse, including commercial, with attribution (Commission Decision 2011/833/EU)Daily; delisted entries are removed at the next sync

What happens

Wrong matches and appeals

PG1 matches the exact wallet address, after normalising its format, against the addresses the lists publish. A match therefore means the list names that address.

PG1 serves agents and people everywhere. Screening is the one wallet-level restriction, and it applies only to the paying wallet.