# Recommended Deployment Shape AML screening should be backend-first in production. API credentials (such as `ELLIPTIC_API_KEY`) must stay server-side and should never be bundled into client code. Analysis results may contain sensitive customer context, including risk scores, exposure breakdowns, and entity attributions, that should not be surfaced raw to end users. **Decisioning (e.g., blocking a deposit or flagging a user for review) belongs in your own risk controls, downstream of the raw analysis response.** --- # Agent Instructions: 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: ``` GET https://city-protocol.gitbook.io/docs/software-development-kit/aml/recommended-deployment-shape.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.