/**
 * Picks the api key a fire / recurring run RUNS AS. Shared by every fire-path form
 * (hooks, trigger links, schedules). Presentational and prop-driven — the host
 * feature owns the api-key list query and hands it in, so this component (and the
 * SDK) stay free of a data-fetching library, exactly as {@link ToolPicker} does.
 *
 * The server decides authorization; this only lists the pickable keys and renders
 * the read's loading / empty / error states. The host form renders the server's
 * refusal verbatim elsewhere.
 */
import type { TokensPayload } from '@tai42/api-client';
import type { ReactNode } from 'react';
/**
 * The subset of the api-key list query this picker reads. A caller's TanStack
 * `UseQueryResult<TokensPayload>` satisfies it structurally, so the SDK names no
 * query library.
 */
export interface ExecutionKeyQuery {
    readonly data: TokensPayload | undefined;
    readonly isPending: boolean;
    readonly isError: boolean;
    readonly isSuccess: boolean;
    readonly error: unknown;
    readonly refetch: () => void;
}
/** Resolved, and holding no key at all. */
export declare function isExecutionKeyListEmpty(query: ExecutionKeyQuery): boolean;
export interface ExecutionKeyPickerProps {
    /** The api-key list read the host feature owns and hands in. */
    readonly query: ExecutionKeyQuery;
    readonly value: string;
    readonly onValueChange: (value: string) => void;
    /** The host form's required-field error, shown under the control. */
    readonly error?: string | undefined;
}
export declare function ExecutionKeyPicker({ query, value, onValueChange, error, }: ExecutionKeyPickerProps): ReactNode;
//# sourceMappingURL=execution-key-picker.d.ts.map