How do you do OOD detection on a closed LLM API with no latent access?
Summary
Discusses methods for out-of-distribution detection on closed LLM APIs without latent access, highlighting techniques like SelfCheckGPT, token-level entropy, proxy embeddings, and verifier models, and notes the collapse of OOD and hallucination detection.
Similar Articles
Hallucination Detection via Activations of Open-Weight Proxy Analyzers
This paper introduces a proxy-analyzer framework that detects hallucinations in large language models by analyzing internal activations of small, open-weight models rather than the generator itself. The method achieves superior performance on benchmarks like RAGTruth compared to existing methods like ReDeEP, demonstrating that model size is less critical than the analysis approach.
OpenHalDet: A Unified Benchmark for Hallucination Detection across Diverse Generation Scenarios
OpenHalDet is a unified benchmark for hallucination detection in LLMs, standardizing evaluation across diverse generation scenarios and supporting black-box, gray-box, and white-box detection methods.
Shared Latent Structures Enable Unified Backdoor Detection and Mitigation in LLMs
This paper identifies a shared latent mechanism across diverse backdoor behaviors in LLMs, using sparse autoencoders to detect and causally suppress these features, enabling unified backdoor detection and mitigation across models and attack types.
Black-Box Inference of LLM Architectural Properties with Restrictive API Access
This paper presents NightVision, an attack that uses restrictive black-box API access to estimate hidden dimension, depth, and parameter count of large language models. It exploits a novel common-set prompting technique and spectral analysis, achieving high accuracy on open-source models.
Building independent LLM drift detection - sharing the methodology, looking for feedback on the approach
The author shares a methodology for building an external LLM drift detection system that continuously probes model behavior (schema adherence, instruction-following, refusal rates, etc.) to catch silent degradations in API performance, and invites feedback on the approach, pricing, and use cases.