Europe (Norway)
Available
Stavanger, Norway
Base URLhttps://eu.api.geodd.io/inference/v1Dola-Seed-2.1 is a next-generation model tailored for the coding and agent era. Compared with its prior generation, it brings comprehensive upgrades across three core dimensions: engineering-grade code delivery, long-horizon agent execution, and multimodal understanding, paired with enhanced autonomous planning and dynamic self-repair capabilities. It has crossed the "production-grade" threshold, enabling it to handle real enterprise R&D workflows and high-value production tasks.
bytedance/dola-seed-2-1-turbo-260628Verification checks the published Geodd catalogs, not a live inference request. Prices and availability come from the backend.
Endpoint support
These values describe Geodd's published endpoint capabilities, not capabilities inherited from the base model. An unreported feature is marked Not verified, not assumed unsupported. Independent test results are not supplied by the catalog.
Catalog precision: bf16. Maximum output: 262,144 tokens.
From model ID to request
Install the SDK with npm install openai or pip install openai. Set GEODD_API_KEY in your server environment or secret manager. Never put it in browser code or a public environment variable.
import OpenAI from "openai";
const client = new OpenAI({
apiKey: process.env.GEODD_API_KEY,
baseURL: "https://eu.api.geodd.io/inference/v1",
});
const response = await client.chat.completions.create({
model: "bytedance/dola-seed-2-1-turbo-260628",
messages: [
{ role: "user", content: "Explain speculative decoding." }
],
});
console.log(response.choices[0].message.content);import os
from openai import OpenAI
client = OpenAI(
api_key=os.environ["GEODD_API_KEY"],
base_url="https://eu.api.geodd.io/inference/v1",
)
response = client.chat.completions.create(
model="bytedance/dola-seed-2-1-turbo-260628",
messages=[
{"role": "user", "content": "Explain speculative decoding."}
],
)
print(response.choices[0].message.content)curl --fail-with-body "https://eu.api.geodd.io/inference/v1/chat/completions" \
--header "Authorization: Bearer $GEODD_API_KEY" \
--header "Content-Type: application/json" \
--data '{
"model": "bytedance/dola-seed-2-1-turbo-260628",
"messages": [
{ "role": "user", "content": "Explain speculative decoding." }
]
}'All examples use bytedance/dola-seed-2-1-turbo-260628. To select another available region, replace baseURL, base_url, or the cURL URL with its base URL below. A real request consumes billable usage.
Usage-based billing / USD
| Usage | Price |
|---|---|
| Input tokens | $0.500 / 1M tokens |
| Output tokens | $3.000 / 1M tokens |
| Cached input reads | $0.000 / 1M tokens |
| Cache writes | $0.000 / 1M tokens |
Cache rates are catalog fields; a zero rate does not establish that caching is available. Cache support and reasoning-token accounting have not been verified. Confirm unlisted billing conditions before production use.
View all inference pricingModel-specific availability
Available
Stavanger, Norway
Base URLhttps://eu.api.geodd.io/inference/v1Available
apac-lk-colombo
Base URLNot published
The EU API route is the European serving route. Its listed location is Norway (EEA), not an EU member state. Do not assume EU-only residency from the endpoint name.
Use the selected serving region for inference processing. Residency commitments and administrative or support access remain subject to Geodd's data handling policy and your agreement.
Payloads and operational metadata
Integrate in your existing stack
Using Claude Code, Codex, Cursor, Windsurf, or another terminal-based coding agent? Give it the prompt below to configure Geodd in your application.
No install or setup command is published here until the CLI is available. Today, use an authorized server-side credential from the Geodd console and the SDK examples above.
The intended CLI flow is to authenticate with Geodd, create or select a project, select an inference region, create a scoped credential, safely configure the environment, detect the project's language and framework, install the appropriate SDK, and test an actual request.
The goal is human approval only for authentication, billing authorization, and spending limits, without manually copying credentials when an authorization flow is available. This is a planned workflow, not a currently available feature.
Add Seed 2.1 Turbo to this application using Geodd.
Use model: bytedance/dola-seed-2-1-turbo-260628
Use Geodd's OpenAI-compatible API.
Requirements:
- Inspect the existing application first and use its existing integration patterns.
- Keep Geodd credentials server-side and use environment variables.
- Never expose the API credential to browser code, logs, or source control.
- Use GEODD_API_KEY; do not ask me to paste a credential into the conversation.
- Implement streaming where supported and appropriate.
- Preserve conversation history if the application includes chat.
- Add error handling for authentication, rate limits, and upstream failures.
- Install the required SDK using the project's package manager.
- Run a real test request when authorized credentials and billing are available.
- Ask for approval before incurring charges or changing a spending limit.
- If credentials are unavailable, explain the blocker; do not claim the test passed.
- Do not rewrite the application architecture when the existing stack supports this integration.
Geodd API base URL: https://eu.api.geodd.io/inference/v1
Geodd documentation: https://geodd.io/docs/llm-api/getting-started
Model facts: https://geodd.io/models/bytedance/dola-seed-2-1-turbo-260628.jsonTraceable facts
This page and its JSON representation use the same backend snapshot. Unknown values remain null in JSON; they are not interpreted as supported or unsupported. The availability date uses the backend's model creation timestamp.
bytedance/dola-seed-2-1-turbo-260628Direct answers
Yes. Use the Geodd model ID bytedance/dola-seed-2-1-turbo-260628. The model developer is bytedance; the API provider is Geodd.
Yes. Use the supported OpenAI SDK chat completions interface with a Geodd API base URL and model ID bytedance/dola-seed-2-1-turbo-260628.
Input: $0.500 / 1M tokens. Output: $3.000 / 1M tokens. Prices are in USD. See the pricing section for published fees and unverified billing details.
Currently listed serving regions: Europe (Norway) and apac-lk-colombo. Use the regional base URLs above. The listed EU API route serves Norway, which is in the EEA, not the European Union.
A model-specific zero-retention flag has not been verified. Geodd publishes its default payload and operational-metadata handling in the data handling policy linked above.
Yes, tool calling is listed in Geodd's model capability catalog. This page does not represent an independent live capability test.
The Geodd CLI workflow is coming soon. Today, copy the integration prompt above into Claude Code, Codex, Cursor, Windsurf, or another coding agent. An authorized server-side credential and billing approval are needed for a real test request.