export interface AnswerEvaluationPOSTParams {
    question: string;
    helpful: boolean;
    answer: {
        responseId: string;
        text: string;
        format: string;
    };
    details: {
        readable: boolean | null;
        documented: boolean | null;
        correctTopic: boolean | null;
        hallucinationFree: boolean | null;
    };
    correctAnswerUrl: string | null;
    additionalNotes: string | null;
}
export declare const answerEvaluation: import("@reduxjs/toolkit/query").Api<import("@reduxjs/toolkit/query").BaseQueryFn<string | import("@reduxjs/toolkit/query").FetchArgs, unknown, import("@reduxjs/toolkit/query").FetchBaseQueryError, {} & import("@reduxjs/toolkit/query").RetryOptions, {}>, {
    /**
     * Based on the RTKQuery documentation, the `query` method is typically utilized for GET requests,
     * while the `mutation` method is designed for POST requests.
     * However, in this instance,
     * we hypothesize that the use of `mutation` is incompatible when paired with an empty response body and an 'application/json' content-type response header.
     * This should be updated as soon as we can remove the content-type header from the response.
     * @see https://redux-toolkit.js.org/rtk-query/usage/mutations#mutations
     */
    post: import("@reduxjs/toolkit/query").QueryDefinition<AnswerEvaluationPOSTParams, import("@reduxjs/toolkit/query").BaseQueryFn<string | import("@reduxjs/toolkit/query").FetchArgs, unknown, import("@reduxjs/toolkit/query").FetchBaseQueryError, {} & import("@reduxjs/toolkit/query").RetryOptions, {}>, never, void, "answer", unknown>;
}, "answer", never, typeof import("@reduxjs/toolkit/query").coreModuleName>;
