# Overview FIP Module will host set of ReBIT API that the AA will call from their Backend. Those APIs are defined here you will have to implement 2.0.0 version or 2.1.0 for Insurance FIPs Your FIP module will further call your CBS to discover accounts and fetch data. **Central Registry FIP Entity Onboarding** You can follow the steps here [Create FIU Entity](/central-registry/create-fiu-entity.md) to create an FIP entity as well. Just select FIP instead of FIU ### **(CR) Central Registry APIs** Ref- [Central Registry APIs](/central-registry/central-registry-apis.md) Central Registry host a list of APIs that you can use 1\. Token Generation API 2\. AA List When you are making API call to the AA you need to pass the token generated in the CR to be sent in the header as fip\_api\_key ### **Detached JWS Signature** All API response that you are sending needs to have the x-jws-signature refer - [JWS Signature](/fiu-module/jws-signature.md) ### End-to-end encryption of Data Request Ref - Note: The 2.0.0 ReBIT version requires you to support both curve25519 and X25519 curve of ECDH --- # 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.saafe.in/fip-module/overview.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.