Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

Auditing Black-Box LLM APIs with a Rank-Based Uniformity Test

Xiaoyuan Zhu, Yaowen Ye, Tianyi Qiu, Hanlin Zhu +5 more

Published

Jun 8, 2025

Citations

0

Trust level

Low

Usefulness score

40/100 (Low)

Extraction confidence

45% (Low)

Derived from extracted protocol signals and abstract evidence.

Rater population

Not reported

Signals refreshed

Apr 9, 2026

Should you rely on this paper?

This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.

Use this as background context only. Do not make protocol decisions from this page alone.

Best use

Background context only

Use if you need

Background context only.

What to verify

Read the full paper before copying any benchmark, metric, or protocol choices.

Main weakness

The available metadata is too thin to trust this as a primary source.

Human feedback signal
Detected
From extracted signals
Evaluation signal
Weak or implicit
Validate from full paper
Usefulness for eval research
40/100
Adjacent candidate

Treat as adjacent context, not a core eval-method reference.

Abstract

As API access becomes a primary interface to large language models (LLMs), users often interact with black-box systems that offer little transparency into the deployed model. To reduce costs or maliciously alter model behaviors, API providers may discreetly serve quantized or fine-tuned variants, which can degrade performance and compromise safety. Detecting such substitutions is difficult, as users lack access to model weights and, in most cases, even output logits. To tackle this problem, we propose a rank-based uniformity test that can verify the behavioral equality of a black-box LLM to a locally deployed authentic model. Our method is accurate, query-efficient, and avoids detectable query patterns, making it robust to adversarial providers that reroute or mix responses upon the detection of testing attempts. We evaluate the approach across diverse threat scenarios, including quantization, harmful fine-tuning, jailbreak prompts, and full model substitution, showing that it consistently achieves superior statistical power over prior methods under constrained query budgets.

What we could verify

These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.

Human Feedback Types

partial

Red Team

Directly usable for protocol triage.

"As API access becomes a primary interface to large language models (LLMs), users often interact with black-box systems that offer little transparency into the deployed model."

Evaluation Modes

missing

None explicit

Validate eval design from full paper text.

"As API access becomes a primary interface to large language models (LLMs), users often interact with black-box systems that offer little transparency into the deployed model."

Quality Controls

missing

Not reported

No explicit QC controls found.

"As API access becomes a primary interface to large language models (LLMs), users often interact with black-box systems that offer little transparency into the deployed model."

Benchmarks / Datasets

missing

Not extracted

No benchmark anchors detected.

"As API access becomes a primary interface to large language models (LLMs), users often interact with black-box systems that offer little transparency into the deployed model."

Reported Metrics

missing

Not extracted

No metric anchors detected.

"As API access becomes a primary interface to large language models (LLMs), users often interact with black-box systems that offer little transparency into the deployed model."

Benchmarks and datasets

No benchmark or dataset names were extracted from the available abstract.

Reported metrics

No metric terms were extracted from the available abstract.

Human feedback details
Uses human feedback
Yes
Feedback types
Red Team
Rater population
Not reported
Expertise required
General
Evaluation details
Evaluation modes
None
Agentic eval
None
Quality controls
Not reported
Evidence quality
Low
Use this page as
Background context only

Research brief

Metadata summary

As API access becomes a primary interface to large language models (LLMs), users often interact with black-box systems that offer little transparency into the deployed model.

Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.

Key takeaways

  • As API access becomes a primary interface to large language models (LLMs), users often interact with black-box systems that offer little transparency into the deployed model.
  • To reduce costs or maliciously alter model behaviors, API providers may discreetly serve quantized or fine-tuned variants, which can degrade performance and compromise safety.
  • Detecting such substitutions is difficult, as users lack access to model weights and, in most cases, even output logits.

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Validate inferred eval signals (Tool-use evaluation) against the full paper.
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Recommended queries

Contribution summary

  • To reduce costs or maliciously alter model behaviors, API providers may discreetly serve quantized or fine-tuned variants, which can degrade performance and compromise safety.
  • To tackle this problem, we propose a rank-based uniformity test that can verify the behavioral equality of a black-box LLM to a locally deployed authentic model.
  • We evaluate the approach across diverse threat scenarios, including quantization, harmful fine-tuning, jailbreak prompts, and full model substitution, showing that it consistently achieves superior statistical power over prior methods under…

Why it matters for eval

  • To reduce costs or maliciously alter model behaviors, API providers may discreetly serve quantized or fine-tuned variants, which can degrade performance and compromise safety.

Researcher checklist

  • Human feedback protocol is explicit

    Detected: Red Team

  • Evaluation mode is explicit

    No clear evaluation mode extracted.

  • Quality control reporting appears

    No calibration/adjudication/IAA control explicitly detected.

  • Benchmark or dataset anchors are present

    No benchmark/dataset anchor extracted from abstract.

  • Metric reporting is present

    No metric terms extracted.