import { type Operation } from "effection";
/**
 * Implement `tufa oobi generate` from locally accepted endpoint/location state.
 *
 * Source of truth:
 * - controller URLs come from `locs.`
 * - mailbox/agent URLs come from `ends.` + `locs.`
 * - witness URLs come from the current key-state witness set plus `locs.`
 *
 * The command is intentionally readonly; it does not attempt to heal or fetch
 * missing state.
 */
export declare function oobiGenerateCommand(args: Record<string, unknown>): Operation<void>;
/**
 * Implement `tufa oobi resolve` using a command-local shared runtime host.
 *
 * The command queues one OOBI job, runs one runtime turn, and succeeds only if
 * the URL lands in `roobi.`. Any reply/event material fetched from the OOBI is
 * forced through the same parser/routing path used by the long-lived host.
 */
export declare function oobiResolveCommand(args: Record<string, unknown>): Operation<void>;
/**
 * Implement `tufa oobi request` through the mailbox-first EXN transport path.
 *
 * This mirrors KERIpy's `"/oobis"` route while keeping the CLI and transport
 * ownership aligned with other outbound messaging commands.
 */
export declare function oobiRequestCommand(args: Record<string, unknown>): Operation<void>;
//# sourceMappingURL=oobi.d.ts.map