# Research & Browser

_{This page means}

| This page is | This page is not | | ----------------------------------------- | ------------------------------------------------------- | | _{A boundary story for operators} | _{A lecture on Content Security Policy headers} |

_{The idea}

_{Your research keys fund queries and crawls. They are} _**not** _{public embed tokens. The product is shaped so integration secrets are handled where your deployment already enforces server trust, not inside every visitor's browser tab.}

_{Why the boundary matters}

{% stepper %} {% step %} _**Exposure** _{Anything that reaches the browser can be extracted by determined users, extensions, or mistakes in logging.} {% endstep %} {% step %} _**Billing** _{Vendor meters often charge per call. Centralizing calls helps you reason about cost and abuse.} {% endstep %} {% step %} _{**Consistency**} _**Test** _{in Settings exercises the same path the app prefers for proof, not a one-off curl from a laptop that bypasses your real controls.} {% endstep %} {% endstepper %}

_{Ask a question}

_{Where does your “allowed to touch production keys” lives?}
_{If it is only in someone’s head, write three bullets once.}

--- # 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://docs.ariaagi.com/security-and-privacy/research-and-browser.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.