Baseten Integration

Use Baseten-backed models from PorkiCoder

PorkiCoder uses Baseten-backed paths for Kimi K2.7 Code, Kimi K2.6, and GLM-5.2 across consult tools, agent workflows, opencode, and model selection. Inside PorkiCoder, signed-in users get proxy-first access for consults and server-backed models; users with their own Baseten key can keep using direct Baseten fallback paths.

Download PorkiCoder Read Consult MCP docs

Quick Start

The Baseten-backed paths are already wired into PorkiCoder. A signed-in user can open a PorkiCoder terminal and use the bundled consult tools from Claude Code, Codex, or opencode. PorkiCoder starts those tools with authenticated proxy URLs, and when a user has pasted a Baseten key in Settings, it also exposes the key as a BYOK fallback.

1
Install PorkiCoder
Download PorkiCoder, sign in, and open a project. The bundled MCP server registers itself for supported terminal agents.
2
Open a terminal agent
Start Claude Code, Codex, or opencode from a PorkiCoder-managed terminal tab.
3
Ask for a consult
Use plain English or call consult_kimi27, consult_kimi27_fast, consult_kimi, or consult_glm52.
4
Review the answer
PorkiCoder streams the response, tracks usage, and keeps the agent in the same workflow.

Baseten-Backed Models

PorkiCoder uses Baseten for the open-model paths where low setup friction matters most: code consults, independent second opinions, long-context reasoning, and opencode model routing.

Model path Transport Typical use
Kimi K2.7 Code
consult_kimi27, consult_kimi27_fast		 Proxy-first through PorkiCoder when signed in; direct Baseten fallback with BASETEN_API_KEY or KIMI_API_KEY. The fast path can fall back to Kimi K2.6. Code review, implementation judgment, refactor sanity checks, and fast Kimi-lineage second opinions.
Kimi K2.6
consult_kimi		 Consults prefer the PorkiCoder proxy when available and fall back to direct Baseten with KIMI_API_KEY. In-app Kimi K2.6 model calls can use direct Baseten with the user's key. Fast code assistance, quick second opinions, and low-friction coding help.
GLM-5.2
consult_glm52		 Proxy-first through PorkiCoder when signed in; direct Baseten fallback with BASETEN_API_KEY or KIMI_API_KEY. GLM reasoning is enabled with chat_template_args.enable_thinking. Large-context reviews, architecture tradeoffs, and deep reasoning with a long context window.

How PorkiCoder Uses Baseten

  • The bundled porkicoder-consult MCP server auto-registers with Claude Code and Codex, and opencode also gets native consult tool definitions.
  • For signed-in PorkiCoder users, consult tools prefer authenticated PorkiCoder proxy URLs; the PorkiCoder backend then supplies the Baseten credentials and calls Baseten's OpenAI-compatible chat completions endpoint.
  • For standalone or BYOK use, Kimi K2.7 Code and GLM-5.2 read BASETEN_API_KEY or KIMI_API_KEY; Kimi K2.6 reads KIMI_API_KEY.
  • In-app chat and agent routing use Kimi K2.6 directly through Baseten when the user has a key, while Kimi K2.7 Code and GLM-5.2 use PorkiCoder's authenticated server proxy.
  • PorkiCoder records usage, applies quota checks on server-backed paths, retries transient Baseten failures, and staggers Baseten-backed fan-out workers to avoid synchronized rate-limit retries.
No separate Baseten setup required for first use
The default consult path is designed for zero-setup developer tooling. PorkiCoder handles MCP registration, proxy credentials, server-side Baseten calls, streaming response parsing, usage metering, and BYOK fallback behavior so users can try Baseten-backed models inside their normal coding agent session.

Example Prompts

Users do not need to memorize tool schemas. These plain-English requests are enough for an agent with PorkiCoder's consult tools available:

  • Ask Kimi K2.7 Code to review this refactor before we apply it.
  • Use GLM-5.2 on the full diff and look for architectural risks.
  • Consult Kimi on why this test is still failing after the last patch.
  • Run a fan-out with Kimi and GLM candidates, then compare the diffs.

Suggested Baseten Listing

If Baseten adds PorkiCoder to its integrations page, this short listing matches the current implementation:

PorkiCoder

Run Claude Code, Codex, and opencode with Baseten-backed Kimi K2.7 Code, Kimi K2.6, and GLM-5.2 consult tools. PorkiCoder handles MCP setup, proxy-first access for signed-in users, direct Baseten fallback for BYOK users, streaming, retries, and usage tracking inside the developer workflow.

Docs: https://porkicoder.com/integrations/baseten.html

FAQ

Do users need a Baseten account?
Not for first use of the included PorkiCoder consult proxy. Users who want BYOK fallback or standalone use can bring their own Baseten API key.
Is this limited to one agent?
No. PorkiCoder exposes Baseten-backed consult paths to supported terminal agents including Claude Code, Codex, and opencode, and also uses the same backed model routes in supported in-app workflows.
Where can I read the general docs?
See the Consult MCP section and the model support section in the PorkiCoder docs.