> For the complete documentation index, see [llms.txt](https://docs.graphite-note.com/graphite-note-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graphite-note.com/graphite-note-documentation/rest-api/model-results-api.md). # Model Results API Model results API lets users fetch the outputs of their trained models in a structured, paginated format. This is especially useful for viewing or processing large prediction result sets in batches.

*** The /fetch-result endpoint returns paginated rows from a dataset result table for a specific model. It also supports an optional rate-limiting check (if configured on your account). This allows you to access structured dataset information efficiently, even for large datasets.\ \ This API endpoint is used to retrieve paginated results for **RFM** (Recency, Frequency, Monetary), **CLV** (Customer Lifetime Value), **ABC** and **General Segmentation** models within Graphite Note. *** In the following sections, you will find more details about the Model Results API. --- # 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://docs.graphite-note.com/graphite-note-documentation/rest-api/model-results-api.md?ask=&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.