Seed 2.0 Pro API

Built for the Agent era, it delivers stable performance in complex reasoning and long-horizon tasks, including multi-step planning, visual-text reasoning, video understanding, and advanced analysis.

Model IDbytedance/seed-2-0-pro-260328
Input pricing
$0.500 / 1M tokens
Output pricing
$2.000 / 1M tokens
Context
256K tokens
Regions
US / LK
US-EAST and Colombo, Sri Lanka
Data handling
Retention not verified
Prompts and outputs are not used for training
API
OpenAI-compatible
Last verified:

Verification checks the published Geodd catalogs, not a live inference request. Prices and availability come from the backend.

Playground

Seed 2.0 Pro model logo

Seed 2.0 Pro

Free public preview

Start a conversation with Seed 2.0 Pro

Send a message to test tone, reasoning, and instruction following in real time.

Endpoint support

Seed 2.0 Pro capabilities on Geodd

These values describe Geodd's published endpoint capabilities, not capabilities inherited from the base model. Features listed as supported show Yes; otherwise they show No. Independent test results are not supplied by the catalog.

Streaming
No
Tool calling
Yes
Structured outputs
No
Reasoning
Yes
OpenAI-compatible chat completions
Yes
JSON responses
Yes
Batch API
No
Fine-tuning
No
Dedicated deployment
No

Catalog precision: bf16. Maximum output: 128K tokens.

From model ID to request

Use Seed 2.0 Pro with the OpenAI SDK

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.

TypeScript
import OpenAI from "openai";

const client = new OpenAI({
  apiKey: process.env.GEODD_API_KEY,
  baseURL: "https://api.geodd.io/inference/v1",
});

const response = await client.chat.completions.create({
  model: "bytedance/seed-2-0-pro-260328",
  messages: [
    { role: "user", content: "Explain speculative decoding." }
  ],
});

console.log(response.choices[0].message.content);
Python
import os
from openai import OpenAI

client = OpenAI(
    api_key=os.environ["GEODD_API_KEY"],
    base_url="https://api.geodd.io/inference/v1",
)

response = client.chat.completions.create(
    model="bytedance/seed-2-0-pro-260328",
    messages=[
        {"role": "user", "content": "Explain speculative decoding."}
    ],
)

print(response.choices[0].message.content)
cURL
curl --fail-with-body "https://api.geodd.io/inference/v1/chat/completions" \
  --header "Authorization: Bearer $GEODD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "model": "bytedance/seed-2-0-pro-260328",
    "messages": [
      { "role": "user", "content": "Explain speculative decoding." }
    ]
  }'

All examples use bytedance/seed-2-0-pro-260328. To select another available region, replace baseURL, base_url, or the cURL URL with its base URL below. A real request consumes billable usage.

OpenAI-compatible API quick start

Usage-based billing / USD

Seed 2.0 Pro pricing

Seed 2.0 Pro serverless token pricing in USD
UsagePrice
Input tokens$0.500 / 1M tokens
Output tokens$2.000 / 1M tokens
Cached input reads$0.100 / 1M tokens
Serverless billing unit
Per token; prices shown per 1 million tokens
Per-request fee
No per-request fee listed ($0)
View all inference pricing

Model-specific availability

Available regions

US-EAST

Available

United States

Base URL
https://api.geodd.io/inference/v1

Colombo, Sri Lanka

Available

Colombo, Sri Lanka

Base URL

Not published

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

Data handling

GDPR Ready
GDPR
Ready
SOC 2 Type II
Pending
DPA
Available
  • A model-specific zero-retention flag is not available in the current catalog. Confirm applicability before sending sensitive data.
  • Geodd does not use customer prompts or model outputs to train models.
  • Limited operational metadata, such as usage, billing, and security events, may be retained. Zero payload retention does not mean zero metadata.
  • Requests use the selected serving region where applicable. API credentials should only be used server-side.

Integrate in your existing stack

Add Seed 2.0 Pro with your coding agent

Sign in from your terminal, then give the prompt below to Claude Code, Codex, Cursor, or your preferred coding agent. Requires Node.js 22+ and npm; no global install needed.

Sign in with Geodd CLI
npx @geodd/cli@latest auth login

Complete Google sign-in and any two-factor verification in the browser on the same computer. New to Geodd? Use auth signup instead of auth login.

Your agent uses the CLI to find the model's key-command ID and create a key with your approval, then configures your app. New keys use PostPaid billing with a default monthly capacity of 3 billion tokens, not a spending cap. Keep key secrets out of chat and shared logs.

Coding-agent prompt
Add Seed 2.0 Pro to this application using Geodd.

Use model: bytedance/seed-2-0-pro-260328
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://api.geodd.io/inference/v1
Geodd documentation: https://geodd.io/docs/llm-api/getting-started
Model facts: https://geodd.io/models/bytedance/seed-2-0-pro-260328.json

CLI setup (Node.js 22+ and npm; no global install needed):
- Read https://geodd.io/docs/llm-api/cli-quick-start before using the CLI.
- Check the session with npx @geodd/cli@latest auth status. If needed, ask me to run npx @geodd/cli@latest auth login (or auth signup for a new account) and complete browser sign-in and two-factor verification on the same computer.
- Reuse an authorized GEODD_API_KEY if already configured. Otherwise, run npx @geodd/cli@latest models list --for-keys --json and identify the entry for bytedance/seed-2-0-pro-260328. Use that entry's id for key commands, not the public inference ID or display name. If the match is unclear, stop and ask.
- Before creating a key, get my approval for PostPaid billing and monthly capacity. The default is 3,000,000,000 tokens, not a spending cap; use --monthly-volume for an approved override.
- Choose a globally unique key name of 1-32 letters, numbers, or dashes. Run npx @geodd/cli@latest keys create --name KEY_NAME --model MODEL_ID --json with the chosen name and discovered key-command ID. Add --yes only after explicit approval for a non-interactive operation.
- Capture secret-bearing output privately, never in shared logs or the conversation. Store data.data.apiKey securely as server-side GEODD_API_KEY and retain data.data.keyId for updates. The CLI does not save the key secret. If private capture is unavailable, ask me to provision the secret outside the agent session. Do not blindly retry creation after a timeout.
- There is no keys list command. If updating a saved keyId, keys update replaces the entire model set; include every model to retain and get approval first.
- Keep bytedance/seed-2-0-pro-260328 as the model ID in inference requests. The coding agent, not the CLI, must configure the application and run the approved test request.
CLI Guide

Traceable facts

Model data and sources

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.

Model name
Seed 2.0 Pro
Model ID
bytedance/seed-2-0-pro-260328
Model developer
bytedance
API provider
Geodd
Last verified (catalog)
Page data updated
Model released
Not supplied by the Geodd catalog
Available on Geodd since

Direct answers

Frequently asked questions

Does Geodd offer Seed 2.0 Pro?

Yes. Use the Geodd model ID bytedance/seed-2-0-pro-260328. The model developer is bytedance; the API provider is Geodd.

Is Geodd's Seed 2.0 Pro API OpenAI compatible?

Yes. Use the supported OpenAI SDK chat completions interface with a Geodd API base URL and model ID bytedance/seed-2-0-pro-260328.

How much does Seed 2.0 Pro cost on Geodd?

Input: $0.500 / 1M tokens. Output: $2.000 / 1M tokens. Prices are in USD. See the pricing section for published fees and unverified billing details.

Where is Seed 2.0 Pro hosted?

Currently listed serving regions: US-EAST and Colombo, Sri Lanka. Use the regional base URLs above.

Does Geodd retain Seed 2.0 Pro prompts?

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.

Can I use Seed 2.0 Pro for tool calling?

Yes, tool calling is listed in Geodd's model capability catalog. This page does not represent an independent live capability test.

Can my coding agent add Seed 2.0 Pro automatically?

Sign in with npx @geodd/cli@latest auth login, then give your coding agent the integration prompt above. The CLI handles authentication and API key operations; your agent configures the application. Key creation and real test requests require your billing approval.