You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
GCG: Investigate which models have APIs that expose logprobs #991
Supported on OpenAI side; Azure may lag behind and some deployments still reject logprobs. Check your region/API version.
Anthropic
Messages API
❌ No
Claude (all versions)
Not supported. Frequently requested. No workaround except estimation hacks via openlogprobs library.
Google Gemini
Vertex AI only
✅ Yes
Gemini 1.5, 2.5
response_logprobs=true, logprobs=N. Not available on the standard Google GenAI API — only via Vertex AI.
DeepSeek
Chat Completions (OpenAI-compat)
❌ Broken
DeepSeek V3.2, R1
API accepts the param but returns 0 or -9999. Effectively non-functional as of late 2025.
Mistral
Native API
❌ Not documented
Mistral models
Not prominently documented. Works via self-hosted (vLLM) or Amazon Bedrock.
Cohere
Generate / Chat
❌ No
Command models
Not supported natively.
Meta Llama (via Together AI)
Chat Completions (OpenAI-compat)
✅ Yes
Llama 3.x
logprobs param, well-documented.
Meta Llama (via Fireworks AI)
Chat Completions (OpenAI-compat)
✅ Yes
Llama 3.2, 3.3
OpenAI-compatible schema with logprobs.
Self-hosted (vLLM)
OpenAI-compatible
✅ Yes
Any supported model
Full logprobs + prompt logprobs. Works with Llama, Mistral, Qwen, etc. Best option for guaranteed access.
Amazon Bedrock
Custom model import
✅ Yes
Llama, Mistral, Qwen, etc.
return_logprobs: true. Added 2025.
Key Takeaways for Attacks
Best bets for logprobs-based attacks: OpenAI models (Chat Completions or Responses API), Gemini via Vertex AI, and open-weight models served through Together AI, Fireworks AI, or self-hosted vLLM.
Anthropic is a blocker: Claude has no logprobs support at all — any attack requiring token probabilities (e.g., membership inference, calibration-based jailbreak detection, perplexity analysis) simply cannot target Claude.
DeepSeek is unreliable: Despite OpenAI-compatible API surface, logprobs values are meaningless placeholders.
Self-hosted via vLLM is the most reliable path: Full control, works with any HuggingFace model, guaranteed logprobs access including prompt logprobs (useful for prefix attacks).
Azure OpenAI has friction: Feature rollout lags behind OpenAI proper — verify per-deployment before building attack pipelines against Azure endpoints.
Activity
romanlutz commentedon Mar 4, 2026
Logprobs Support Across LLM Providers
Summary Table
logprobs=true,top_logprobs(1–20). Not available for image/multimodal inputs.top_logprobsparam +include: ["message.output_text.logprobs"]. Added mid-2025.logprobs. Check your region/API version.openlogprobslibrary.response_logprobs=true,logprobs=N. Not available on the standard Google GenAI API — only via Vertex AI.0or-9999. Effectively non-functional as of late 2025.logprobsparam, well-documented.return_logprobs: true. Added 2025.Key Takeaways for Attacks
Best bets for logprobs-based attacks: OpenAI models (Chat Completions or Responses API), Gemini via Vertex AI, and open-weight models served through Together AI, Fireworks AI, or self-hosted vLLM.
Anthropic is a blocker: Claude has no logprobs support at all — any attack requiring token probabilities (e.g., membership inference, calibration-based jailbreak detection, perplexity analysis) simply cannot target Claude.
DeepSeek is unreliable: Despite OpenAI-compatible API surface, logprobs values are meaningless placeholders.
Self-hosted via vLLM is the most reliable path: Full control, works with any HuggingFace model, guaranteed logprobs access including prompt logprobs (useful for prefix attacks).
Azure OpenAI has friction: Feature rollout lags behind OpenAI proper — verify per-deployment before building attack pipelines against Azure endpoints.