One API for approved model deployments.
Use familiar API contracts across proprietary and open-source models, with local billing and customer-managed provider credentials.
Explore modelsManaged model access · Enterprise traffic control · Migration assurance
Manage proprietary and open-source model access through one API, enforce spend and privacy policy before dispatch, and move workloads with evidence-backed rollout controls.
Model families represented across access, BYOK, and evaluation workflows
Managed access. Runtime control. Migration evidence. Enterprise Traffic Control is the operating layer beneath every Arc.AI product.
Use familiar API contracts across proprietary and open-source models, with local billing and customer-managed provider credentials.
Explore modelsAttribute every request, authorize spend before dispatch, enforce routing and privacy constraints, and preserve the complete runtime trace.
Explore traffic controlsReplay representative workflows against locked variants, review outcomes blind, and produce a decision memo with rollout and rollback thresholds.
Discuss an assessmentReserve eligible cost before dispatch, then settle actual usage and release the remainder.
Evaluate region, retention, and provider evidence before dispatch—and fail closed when a requirement is unmet.
Replay representative cases against pinned variants and compare quality, tool use, latency, cost, and failures.
* Hard limits apply to eligible Arc.AI-billed calls after configuration and validation. BYOK, tools, taxes, and contracted fees are metered separately.
Arc.AI reserves the maximum eligible cost against applicable budgets before dispatch, then settles actual usage and releases the remainder.
ENFORCEMENT BEFORE PROVIDER DISPATCHRoutes fail over only across administrator-approved endpoints and never relax region, retention, or model constraints.
Fund organizations with Arc.AI Credits where available, or use existing provider contracts. Legal sellers, currencies, refunds, and invoice sequences remain separate while each charge is attributed to the workspace, principal, application, key, model, and provider.
* Payment rails, currencies, and tax documents vary by market, contracting entity, and approval. Arc.AI Credits are non-cash and non-redeemable.
Evaluate a customer source manifest and pinned harness across separate GLM-5.2, Kimi K3, and Tencent Hy3 deployments. Representative cases and historical incidents are reviewed before rollout approval.
Open Claude Migration LabThe provider registry versions privacy evidence and expires it on schedule. If no endpoint meets policy, the request fails closed instead of relaxing the requirement.
Review privacy controlsArc.AI supports familiar OpenAI and Anthropic interfaces. Each provider deployment passes capability and compatibility checks before production admission.
const client = new OpenAI({
apiKey: process.env.ARC_API_KEY,
baseURL: "https://api.arc-ai.example/v1"
});
const response = await client.responses.create({
model: "arc/auto",
input: "Resolve this support case",
metadata: {
workflow_id: "support_resolution_v3",
cost_center: "APAC-CS"
}
});Reserved demonstration endpoint. It cannot receive production traffic, credentials, or customer data.
Employees receive approved models, allowances, and setup guides while administrators manage workspace, model, budget, and expiry policies.
Open Access CenterStart where risk is highest