> For the complete documentation index, see [llms.txt](https://rwapact.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwapact.gitbook.io/whitepaper/protocol-economics/enterprise-risk-api.md). # Enterprise Risk API Explains the Enterprise Risk API model for providing RWAPACT risk scoring capabilities to third-party applications and services. ## Enterprise Risk API Not every application that needs RWA risk intelligence will integrate the complete RWAPACT execution middleware. A third party may instead need risk scoring information as a service. The current protocol economics include an Enterprise Risk API. It provides third parties with access to RWAPACT risk scoring capabilities through a subscription-based model. ### Risk assessment capability The Enterprise Risk API represents access to the type of RWA risk assessment performed by KRO. The underlying model evaluates relevant conditions including: * Oracle staleness * Price deviation * Liquidity depth * Slippage * Market hours * Compliance freeze status * Concentration * Volatility The API provides risk-scoring capability as an external service model. This page does not define endpoints, pricing tiers, service-level commitments, response times, or production availability. ### Two consumption models RWAPACT supports distinct ways to consume the underlying risk infrastructure. | Consumption model | Primary purpose | | ------------------- | ------------------------------------------ | | RWAPACT Middleware | Enforce the Pact before RWA execution. | | Enterprise Risk API | Consume RWAPACT risk scoring as a service. | The core middleware is used when an application needs the full Pact decision layer before execution. The Enterprise Risk API is used when a third party primarily needs risk intelligence or scoring. This distinction does not change KRO's core role. KRO evaluates RWA-specific risk conditions. The full middleware combines that result with KSO session validation, KPV policy enforcement, KGR gas evaluation, and KAR attestation. ### Conceptual example A third-party RWA application evaluates whether an asset is suitable for a strategy. Rather than implementing its own complete RWA risk model, it can consume RWAPACT's risk scoring service. The API provides the risk assessment. The third-party application remains responsible for how it uses that information unless it separately integrates the RWAPACT enforcement layer. Risk intelligence does not itself authorize execution. Enforceable trading decisions remain the responsibility of the complete Pact middleware. ### Risk Intelligence as a Service The Enterprise Risk API extends the utility of RWAPACT's risk infrastructure beyond applications that directly use the complete execution middleware. The subscription model connects this service capability to the protocol's economic design. *** --- # 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://rwapact.gitbook.io/whitepaper/protocol-economics/enterprise-risk-api.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.