> For the complete documentation index, see [llms.txt](https://sahamati.gitbook.io/aa-common-service/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sahamati.gitbook.io/aa-common-service/reference/cr-fiu-schema.md). # CR FIU Schema | Field | Definition | Example | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | entityinfo-name | Name of the entity as submitted while listing itself in the CR. | “Bank Ltd” | | entityinfo-id | ID, as issued by the CR, to the entity | FIU00020001 | | entityinfo-code | ID, as issued by the financial sector regulator, regulating that entity. | BBL2 | | baseurl | The URL of the FIU service that hosts all ReBIT-compliant API endpoints | “ | | inboundports | The ports of the FIU that the AA can connect to. | \["5678","0002"] | | outboundports | The ports of the FIU that the AA can expect to receive requests from. | \["1234","7785"] | | ips | The IP addresses of the FIU that the AA can send and receive requests to. | \["222.333.444.555","012.345.678.901"] | | certificate | The public key of Digital Certificate issued to the FIU by a Certificate Authority (JSON Web Key format) |

"alg": "RS256",
"e": "DCAE",
"kid": "2t674a",
"kty": "RSA",
"n": "3LUQ92bubV321n6oS-qM77w9yqQAV0DXLreOf7iC\_-sgapjYPhHYyI3jc6gsnYL3wp73H7qDsPUGh2iF7oVmyrUec80p8NQvjqYIMOp6iK0Cz9Ouq\_CVbYZPdEDXaWO7Zrlxf8ZjkDzh9KumjSJ67a9lvRSs7ZEEwlC7gLKjgsKq8pei9Y2mGxWUTM1Od2xes1DpSZgoCRKu3BgJ2ZfjslUo6kFr7ItmHBlpEL5sIrI2DpRHao2dJwbawdA5nGXheR3qv5I6OIF0\_mX0PjRasEBvkLTe8Muc4HMTLx\_zmg1LzKwb6khXLCTe6ET-bxtFpPK821e3AKNo7vOIG6p0UQ",
"use": "sig"

| | tokeninfo – url | The URL of the Token Issuance Service of the entity that other entities can connect to, to get API tokens. This can be ignored for now. | “ | | tokeninfo – maxcalls | Ignore for now | 1 | | tokeninfo – desc | Ignore for now | "string" | | signature – signValue | Ignore for now | “7dYbsr4iJmG0Qu2j8DsVyT1azpJC\_NG84Ty5KKthuCaPod7iI7w0LKmX0PjRasEBvkLTe8Muc4“ | --- # 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://sahamati.gitbook.io/aa-common-service/reference/cr-fiu-schema.md?ask=&goal= ``` `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.