Global entry
BatchIn serves global developers and enterprise buyers through the English storefront and global API.
Use this path for USD pricing, public MCP discovery, OpenAI-compatible access, and global-facing sales delivery.
Developer Hub
Bring quickstart, public docs, the live model catalog, playground, pricing, and machine-readable agent resources together in one developer entry.
Global Access, Unified Ingress
BatchIn coordinates API gateways, security controls, and compute availability to guarantee localized delivery with unified engineering standards.
Review live contractGlobal entry
Use this path for USD pricing, public MCP discovery, OpenAI-compatible access, and global-facing sales delivery.
China entry
Use this path for RMB-facing onboarding, domestic support posture, and China-specific commercial delivery without changing the BatchIn product experience.
Production posture
Built for stable production-scale traffic.
Traffic mix
Text plus vision, audio, image, and video workloads.
Streaming path
Regional ingress, stable streaming, and request continuity.
Control guardrails
Scoped limits, request isolation, and backpressure controls.
Public contract and readiness
Shared core
This is where public Model API, batch, usage, billing, and public MCP contract stay consistent.
Private lanes
Customer UI keeps one product truth while delivery, quota, and isolation can vary by contract.
Compute truth
Public pages show inventory and availability only from the verified compute registry.
Edge ingress
Latency work starts at the customer-facing edge before requests enter the primary execution path.
Streaming delivery
Connection reuse and consumer isolation are tuned to reduce jitter and long-tail failures.
Traffic policy
Customers see a simple API and clear limits while BatchIn handles traffic protection behind the scenes.
Unified Model API
One API surface for text, reasoning, vision input, image generation, audio, and video jobs.
Chat and streaming
Use the familiar chat path for low-friction migration, streaming responses, and production request telemetry.
Structured responses
Move tool-oriented and structured application flows onto the newer responses surface without splitting billing or traces.
Embeddings and media
Vector, image, audio, and video endpoints share the same routing, usage, cost, and error format.
MCP and agent discovery
Expose MCP, llms.txt, agents.md, and machine-readable discovery links from one developer entry.
Create a key, send the first request, and move from playground traffic to production usage.
StartBrowse the public OpenAPI contract, request examples, error codes, and compatibility surfaces.
Open docsCompare live models, context windows, and public pricing without leaving the public site.
Browse modelsValidate prompts, streaming behavior, and response formats before wiring your application.
Try requestsReview public pricing, dedicated products, and the right path for larger production workloads.
See pricingFind public repository links, developer-facing resources, and agent-related work under the BatchIn organization.
Open GitHubOpen the agent-facing entry for MCP, llms.txt, agents.md, payment protocol posture, and machine-readable discovery links.
Open agent entry