Skip to content

Add Sakana Fugu as a paid audit engine - #57

Merged
ralyodio merged 1 commit into
masterfrom
feat/sakana-fugu-engine
Jun 23, 2026
Merged

ralyodio merged 1 commit into
masterfrom
feat/sakana-fugu-engine

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

Summary

Wires Sakana AI's Fugu orchestration model in as a new paid scan engine (20 credits), following the same OpenAI-compatible oaCompatAudit path (chat-completions + streaming JSON) as Qwen / DeepSeek / Kimi.

  • lib/audit/fugu-engine.ts (new) — fuguAudit() via oaCompatAudit
  • lib/env.ts — FUGU_API_KEY, FUGU_BASE_URL (default https://api.sakana.ai/v1), FUGU_MODEL (default fugu)
  • lib/credits.ts — "fugu" engine + catalog entry
  • worker/index.ts — import, type cast, dispatch map
  • app/actions/runAudit.ts — ALL_ENGINES
  • components/engines-panel.tsx — selector order
  • components/charts/engine-trend.tsx — trend color

Validation

  • tsc --noEmit clean for both app and worker
  • Live curl to https://api.sakana.ai/v1/chat/completions with model fugu → HTTP 200

Deploy requirement

Set FUGU_API_KEY on the Railway web and worker services, or the engine throws "API key is not set" at runtime. Base URL/model default correctly.

🤖 Generated with Claude Code

Wires Sakana AI's Fugu orchestration model in as a new paid scan engine,
following the same oa-compat (chat-completions + streaming JSON) pattern as
Qwen/DeepSeek/Kimi. Base URL, model, and API key are env-driven
(FUGU_BASE_URL defaults to https://api.sakana.ai/v1, FUGU_MODEL to "fugu").

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@ralyodio
ralyodio merged commit f341c77 into master Jun 23, 2026
5 of 6 checks passed
@ralyodio
ralyodio deleted the feat/sakana-fugu-engine branch June 23, 2026 11:04
@github-actions

Copy link
Copy Markdown

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant