Six public entries

Six entries for production AI APIs, spend, capacity, and agent payments

The public product surface is Model API, Multimodal API, Billing, VaaS, Dedicated Capacity, and Agentic Payments. Batch processing, reserved inference, dedicated endpoints, GPU capacity, and managed deployment are presented as capabilities or delivery paths under those entries.

Public products

6

Currently public products

Status

GA / Preview

Shown from backend truth

One API base

/v1

Models, media, billing, and receipts

Global Access, Unified Ingress

Providing consistent performance and reliability across global and domestic markets.

BatchIn coordinates API gateways, security controls, and compute availability to support localized delivery with unified engineering standards.

View pricing

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.

https://batchin.tech · https://api.batchin.tech/v1

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

OpenAI-compatible endpoints stay stable across chat, responses, embeddings, images, audio, and video.
Public MCP transport and tool discovery stay on the BatchIn contract instead of exposing execution details.
Traffic policy is designed for stable production text and multimodal workloads, not only demo-scale traffic.
Capability availability follows aligned usage, cost, billing, trace, and verification records.

Shared core

Self-serve developers and ordinary enterprise traffic run on the shared BatchIn control core.

This is where public Model API, batch, usage, billing, and public MCP contract stay consistent.

Private lanes

Reserved inference, dedicated endpoints, and larger enterprise traffic move into stricter capacity lanes.

Customer UI keeps one product truth while delivery, quota, and isolation can vary by contract.

Compute truth

Dedicated 8+ GPU delivery and smaller hourly rental both resolve against the same compute and capacity truth.

Public pages show inventory and availability only from the verified compute registry.

Edge ingress

Global traffic enters through a regional edge designed for resilient access and stable session continuity.

Latency work starts at the customer-facing edge before requests enter the primary execution path.

Streaming delivery

BatchIn maintains stable streaming behavior across cross-region and mixed-media workloads.

Connection reuse and consumer isolation are tuned to reduce jitter and long-tail failures.

Traffic policy

Traffic policy stays explicit through scoped protection, retry discipline, and graceful overload handling.

Customers see a simple API and clear limits while BatchIn handles traffic protection behind the scenes.

Public products

All public product navigation rolls up to these six entries. Coding, batch, dedicated endpoints, Dedicated Capacity, managed deployment, and agent billing are use cases or self-serve paths under them.

Community programs

Join WIN or Vibethon

Use events for applications, showcases, and community collaboration. For product purchase, API calls, budgets, receipts, and capacity requests, use the product entries above.