ByteDance’s current family is Seed2.0, and its code-focused route appears in Requesty’s live catalog as bseed-2.0-code. The older Doubao Seed Code name and guessed Volcengine model ID previously shown at this URL are no longer used in this guide.
Configure Claude Code through Requesty
Create a Requesty key and make sure bseed-2.0-code is allowed by the key’s access list. Then set these variables in PowerShell:
$env:ANTHROPIC_BASE_URL = "https://router.requesty.ai/v1"
$env:ANTHROPIC_AUTH_TOKEN = "your-requesty-key"
$env:ANTHROPIC_MODEL = "bseed-2.0-code"
claude
In WSL, use export NAME="value". Requesty documents an Anthropic Messages endpoint at /v1/messages and converts requests for non-Anthropic models.
Test before editing
Ask Claude Code to read one source file and explain it without making changes. Then request a small edit and inspect the diff. The model route can change behind a managed gateway, so repeat this test after a model-version or provider update.
Direct Volcano Engine use
ByteDance says the Seed2.0 API family is available through Volcano Engine. Direct endpoint names and deployment IDs depend on the account and region. Copy them from the Volcano Engine console instead of using the old illustrative doubao-seed-code ID.
BSeed 2.0 Code checklist
- Requesty key created
- bseed-2.0-code allowed for the key
- Anthropic-compatible base URL configured
- Read-only test completed
- API key kept outside source control
For the current DeepSeek comparison, see ByteDance Seed2.0 vs DeepSeek V4.