> For the complete documentation index, see [llms.txt](https://developers.shredpay.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.shredpay.xyz/agent-wallet/concepts/address-screening.md).

# Address Screening

Every write call has its counterparties screened against OFAC and risk lists before signing. This page explains what's checked, when, and how to interpret the result.

## What gets screened

Outline:

* The `to` address on every `send_transaction`.
* Beneficiaries decoded from calldata for known function selectors (e.g. ERC-20 `transfer`, swap router recipients).
* Counterparties on `execute_swap`, `defi_deposit`, `defi_withdraw`.

## When it happens

* Before any signature is produced.
* Both for `send_transaction` and `simulate_transaction` — simulate is a safe way to pre-flight a screening check.

## Failure modes and codes

* `403 ADDRESS_BLOCKED` — counterparty is on a blocked list. The transaction is refused; funds remain in the sub-wallet.
* `403 SUB_WALLET_FROZEN` — the sub-wallet itself was frozen following a screening alert on an inbound transfer. Reach out to support to begin manual review.

## What to do on a hit

Outline:

* Read the response body for the offending address and category.
* Surface the message back to the agent / end-user — agents should treat blocks as terminal.
* Contact `support@shredpay.xyz` if you believe the block is a false positive.

## Inbound transfers

Outline:

* Funds arriving from a flagged source freeze only the receiving sub-wallet, not the user's main account.
* Resolution is manual.

This page will be expanded with concrete examples once the public screening response schema is finalized.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.shredpay.xyz/agent-wallet/concepts/address-screening.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.