Model choice without rewrites
Evaluate quality and unit economics across coding models while your client contract stays consistent.
Give your developer product the model choice, tool interface and production controls it needs—without rebuilding the integration every time a stronger coding model arrives.
POST /v1/chat/completionsAIx keeps identity, integration and measured billing consistent while your workload uses the model best suited to the job.
Evaluate quality and unit economics across coding models while your client contract stays consistent.
Send function schemas, parse tool calls and return execution results using familiar OpenAI-compatible types.
Stream partial output to terminals, editors and web interfaces while the model continues reasoning.
Use these as practical starting points, then evaluate quality, latency and unit economics against your own traffic.
Search the repository, rank relevant files and keep the prompt inside the selected context window.
Expose safe functions for file reads, tests, diffs and targeted edits.
Run tests and policy checks, then present or apply the final patch through your own permission layer.
POST /v1/chat/completionsfrom openai import OpenAI
client = OpenAI(
base_url="https://api.aix.theaimart.co/v1",
api_key="$AIX_KEY",
)
stream = client.chat.completions.create(
model="deepseek-ai/DeepSeek-V3.2",
messages=[{"role": "user", "content": "Review this patch"}],
tools=tools,
stream=True,
)Read the coding-agent guide →Start with a quality-focused coding model for difficult repository work, then test an efficient open model for high-volume background tasks. AIx keeps both behind the same client contract.
Yes. Eligible models accept OpenAI-compatible tools and tool_choice fields and return standard tool_calls.
Yes. Set stream to true and consume standard server-sent events until the final DONE event.
One key. One API contract. The AIx model network behind it.