export type TokenVerification = 'ok' | 'rejected' | 'blocked' | 'unreachable';
/**
 * Probe the dashboard with a bearer token to classify it before storing.
 * Hits the same endpoint `auden sync` pulls guides from, with a short
 * timeout so `auden init --token` stays fast even when the host is down.
 *
 * - 'ok'          — the server accepted the token
 * - 'rejected'    — the server answered 401: the token itself is bad
 * - 'blocked'     — something answered 403. The dashboard does not 403 this
 *                   endpoint for a bad credential (it answers 401), so a 403
 *                   here comes from an intermediary — typically a cloud
 *                   environment's egress proxy refusing a host outside its
 *                   allowlist. Says nothing about the token; treating it as
 *                   'rejected' sent people hunting for a credential problem
 *                   that did not exist.
 * - 'unreachable' — network failure, timeout, or a non-auth error (5xx);
 *                   says nothing about the token, so callers should store
 *                   it and let the next `auden sync` settle the question
 */
export declare function verifyDashboardToken(dashboardUrl: string, token: string, fetchFn?: typeof fetch): Promise<TokenVerification>;
//# sourceMappingURL=token-verify.d.ts.map