> For the complete documentation index, see [llms.txt](https://even-financial.gitbook.io/developer-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://even-financial.gitbook.io/developer-center/compliance/engine-compliance-overview.md).

# Engine Compliance Overview

{% hint style="info" icon="scale-balanced" %}
Engine operates in a highly regulated environment. To manage regulatory and reputational risk, all entities that partner with Engine to market services must comply with all applicable financial services laws.
{% endhint %}

Use this guide to prepare a successful Engine integration. Submit your proposed flow to Engine’s Legal & Compliance Department through your Engine point of contact.

<table><thead><tr><th width="180.5">Integration</th><th>What to submit</th></tr></thead><tbody><tr><td>Partner Page</td><td>The consumer entry point experience leading up to the Partner Page with the call to action (CTA)</td></tr><tr><td>Web Embed</td><td>The consumer experience surrounding the Embed</td></tr><tr><td>Mobile SDK</td><td>In-app experience with the Engine journey</td></tr><tr><td>Offer Wall</td><td>The consumer flow up to the CTA</td></tr><tr><td>Second Party Pre-fill</td><td>The consumer experience and CTA leading up to the Engine experience,</td></tr><tr><td>Native API</td><td>Full experience from start to offer wall display.</td></tr></tbody></table>

### What we review during approval

When you submit an integration for compliance review, we assess:

<table data-view="cards"><thead><tr><th></th><th>What we assess</th></tr></thead><tbody><tr><td>🖥️ <strong>Partner Page</strong></td><td><ul><li>The partner experience and entry point to Engine’s Partner Page.</li><li>Page content for legal and regulatory compliance.</li><li>Page content for branding and reputational review.</li></ul></td></tr><tr><td>🧩 <strong>Embed and SDK</strong></td><td><ul><li>Placement of the Engine tool in the partner experience.</li><li>Surrounding content for legal and regulatory compliance.</li><li>Surrounding content for branding and reputational review.</li></ul></td></tr><tr><td>⚙️ <strong>API</strong></td><td><ul><li>The full flow, including Consumer Information Fields.</li><li>Consumer disclosures and consent language.</li><li>Offer displays for Native APIs.</li><li>Ask your Engine contact for detailed instructions.</li></ul></td></tr></tbody></table>

{% hint style="info" icon="circle-exclamation" %}
For more information on the compliance process, contact your representative to get started!
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://even-financial.gitbook.io/developer-center/compliance/engine-compliance-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.