The Hosted Platform is live today. FenxLabs operates FenxARC™. Connect applications and agents through one OpenAI-compatible endpoint, then enforce which models and tools they may use, which policies apply and what they may spend.
Whether you are one developer or a platform team, if you are already calling more than one model, ARC is for you. Free tier, no card required. Nothing to deploy.
Keep the OpenAI client your application or agent already uses. A new base URL and ARC key put access, privacy and routing policy into every request.
from openai import OpenAI
client = OpenAI(
base_url="https://api.askarc.app/api/v1",
api_key="fxk_your_api_key_here",
)
messages = [{"role": "user", "content": "Summarize this contract..."}]
# No model named, so ARC applies policy and selects the route.
routed = client.chat.completions.create(
messages=messages,
)
# Named model, so the request goes there instead.
pinned = client.chat.completions.create(
model="one-of-your-assigned-models",
messages=messages,
)Three requirements the Hosted Platform does not meet. If your deployment depends on any of them, read the Self-hosted Licence instead.
Give each key access to approved lists of models, tools and rules. Each application or agent request runs inside one list, while administrators change access, privacy and spend policy without redeploying it.
Any OpenAI-compatible endpoint becomes a destination. Your URL, your key, your headers.
Capability ratings
Model flags
Categories and test bench
A test bench sits beside the rules. Run sample requests through a category and see how it classifies before it touches live traffic.
ARC can prefer less expensive resources among those already allowed and enforce budgets at request time. Access, privacy and required capability remain ahead of cost.
Set budgets that ARC enforces while each request is routed. As a budget fills, ARC can prefer less expensive resources that already meet access, privacy and capability requirements.
ARC is billed per routing call, with a free tier and no card. Inference remains a direct relationship with your providers, at their rates. FenxLabs takes no margin.
Both deployments run the same privacy workflow, and they do not draw the same residency boundary.
ARC does not retain or log request data beyond what you configure. On the Hosted Platform the router holds the operational metadata it needs to make a routing decision and to bill the call.
On the Self-hosted Licence, ARC request handling runs inside infrastructure you control.
ARC controls what each provider is sent. What a provider then retains or trains on is set by that endpoint and its terms, not by the router.
This supports your compliance position. It does not deliver compliance on its own.A bounded workload with its own key lets you confirm access, route selection, consumption and configured fallback before production traffic moves.
If access policy, data boundaries or deployment need to be settled before production, bring the workload to an ARC engineer while it is still bounded.
Start free with one OpenAI-compatible integration. Talk to an engineer if access policy, data boundaries or deployment need to be settled first.