/**
 * What an unauthenticated caller is told.
 *
 * MCP clients relay a tool error straight to the model and on to the user, so
 * this text IS the product's authentication UX. It must always carry: the
 * browser path, the manual API-key path with a real URL, and where the key goes.
 */
/** Where a user goes to authorise or manage keys, by environment. */
export declare const AUTH_URLS: {
    /** Consent screen used by the `login` tool's browser handshake. */
    readonly authorize: "https://www.misar.blog/authorize";
    /** Dashboard page where a key is created by hand. */
    readonly apiKeys: "https://www.misar.blog/dashboard/settings/api-keys";
    readonly docs: "https://docs.misar.io/blog";
};
/**
 * Whether this product ships the browser sign-in flow.
 *
 * When false the guidance offers ONLY the manual key path: advertising a
 * `login` tool that is not registered, or an /authorize page that 404s,
 * strands the user worse than saying nothing at all. Flip this in the same
 * change that ships the consent page and the auth tools.
 */
export declare const HAS_BROWSER_LOGIN = true;
/** Prefix every Misar.Blog API key carries, used to validate pasted input. */
export declare const KEY_PREFIX = "mbk_";
/** Environment variable the stdio server reads its API key from. */
export declare const ENV_KEY = "MISARBLOG_API_KEY";
/** Where `login` writes the key it receives. */
export declare const CONFIG_PATH = "~/.misarblog/config.json";
/**
 * The full guidance block.
 *
 * `reason` distinguishes "you never authenticated" from "your key was
 * rejected" — the remedies differ, and telling someone with an expired key to
 * create their first one wastes their time.
 */
export declare function authGuidance(reason?: "missing" | "rejected"): string;
//# sourceMappingURL=auth-guidance.d.ts.map