import { z } from "zod"; export declare const acerRemitSchema: z.ZodObject<{ message_type: z.ZodEnum<{ urgent_market_messages: "urgent_market_messages"; outage_events: "outage_events"; }>; country: z.ZodOptional; fuel_type: z.ZodOptional; limit: z.ZodOptional; }, z.core.$strip>; interface UmmRecord { message_id: string; event_type: string; market_participant: string; asset_name: string; fuel_type: string; country: string; unavailable_mw: number; available_mw: number; installed_mw: number; event_start: string; event_end: string; publication_date: string; reason: string; } interface UmmResult { message_type: "urgent_market_messages"; source: string; description: string; count: number; records: UmmRecord[]; } interface OutageEvent { asset_name: string; fuel_type: string; country: string; unavailable_mw: number; installed_mw: number; event_start: string; expected_return: string; status: string; } interface OutageResult { message_type: "outage_events"; source: string; description: string; count: number; events: OutageEvent[]; } type AcerRemitResult = UmmResult | OutageResult; /** * ACER REMIT data is available from multiple Inside Information Platforms (IIPs). * We use a combination of ENTSO-E REMIT (already available via get_remit_messages) * and supplement with aggregated ACER data where available. * * Since the centralized ACER REMIT Data Reference Centre launched in May 2025, * this tool provides a unified view across multiple IIPs. */ export declare function getAcerRemit(params: z.infer): Promise; export {};