Smart Router · Frameworks
langchain-aistupidlevel adds ChatAISL, a LangChain chat model on the Smart Router: tools, structured output and streaming, your own provider keys, no token markup, and the model that answered and why in response_metadata.
1,000 routed requests a month free · your own provider keys · no card
Part of Smart Router integrations · About the Smart Router · Help centre
# pip install langchain-aistupidlevel from langchain_aistupidlevel import ChatAISL llm = ChatAISL(model="auto-coding", api_key="aism_your_key_here") msg = llm.invoke("Write a Python function") print(msg.content) print(msg.response_metadata["routed_model"]) # the model that answered print(msg.response_metadata["routing_reason"]) # why it was chosen
01
langchain-aistupidlevel adds ChatAISL, a LangChain chat model on the Smart Router: tools, structured output and streaming, your own provider keys, no token markup, and the model that answered and why in response_metadata.
X-AISM-Model and X-AISM-Reasoning: which model answered and why, including any fallback. If the chosen model fails before answering, the router tries your own fallback order, then up to 2 automatic fallbacks from different providers.02
Every value below is the one in the router documentation; paste it as shown.
Go to API keys, click Create key and copy it somewhere safe. The key starts with aism_ and is the one key for every tool you connect.
Under Providers, add keys for OpenAI, Anthropic, Google, DeepSeek, Kimi or GLM. The more providers you add, the better the routing. You pay them directly for tokens; the router adds nothing to token prices, and provider keys are encrypted at rest (AES-256-GCM) and never shown again.
The chat model is published on PyPI as langchain-aistupidlevel and listed in the LangChain documentation’s chat-model table.
pip install langchain-aistupidlevel
ChatAISL takes a routing mode as model and your aism_ key. The answer’s response_metadata carries routed_model, the model that answered, and routing_reason, why it was chosen.
from langchain_aistupidlevel import ChatAISL llm = ChatAISL(model="auto-coding", api_key="aism_your_key_here") msg = llm.invoke("Write a Python function") print(msg.content) print(msg.response_metadata["routed_model"]) # the model that answered print(msg.response_metadata["routing_reason"]) # why it was chosen
ChatAISL supports tools, structured output and streaming. For an agent that calls tools, use auto-tooling; for analysis, auto-reasoning; for general chains, auto-best.
03
A routing mode goes where the tool asks for a model name. The quality modes read the same scores the leaderboard shows; the value modes choose among models within 5 points of the best and take the lowest measured cost per run. Every mode is described in the Virtual models section of the docs.
auto-bestauto-toolingauto-reasoningauto-value24-hour boards as of 26 Oct 2026, 10:51 UTC · places follow the leaderboard’s statistical ties · the full leaderboard
Any real model id from GET /v1/models pins that model and bypasses routing; your plan allowance and key budgets still apply. Unknown auto-* names get a 400 model_not_found that lists the valid ones.
04
ChatAISL supports tools, structured output and streaming, plus the model that answered and why in response_metadata.response_format json_object and json_schema are supported for every provider; the schema is enforced natively by OpenAI, Gemini and the Claude models that support structured output, and sent as an instruction in JSON mode to DeepSeek, Kimi and GLM.400 unsupported_content.05
The errors a tool shows, with the fix from the docs’ error table and the help centre.
aism_ key. Check the key is correct and not revoked, and that the tool sends it as Authorization: Bearer aism_…. If a field insists on an sk- prefix, sk-aism_… is accepted: the prefix is stripped automatically. A key that had an expiry date and passed it gets 401 expired_api_key, and the message says when.auto-* name is a 400 that lists the valid routing modes. For a real model id, check the spelling: direct pin routing infers the provider from the model name prefix, and GET /v1/models lists every id you can use.GET /v1/models, which requires a valid aism_ key. Check that the key and the base URL https://aistupidlevel.info/v1 are both in place.stream: true. Text arrives as the model writes it (X-AISM-Streaming-Mode: native); tool calls arrive in one chunk each once the model has finished them, then the finish reason, then usage if you set stream_options.include_usage. If the chosen model fails before sending anything, or its provider sends nothing for 120 seconds, the next fallback is tried.06
Read msg.response_metadata["routed_model"] for the model and msg.response_metadata["routing_reason"] for why it was chosen, including any fallback. The same facts are in the X-AISM-Model and X-AISM-Reasoning response headers for any OpenAI client.
Yes: tools, structured output and streaming. JSON output through response_format is supported for every provider; OpenAI, Gemini and the Claude models that support structured output enforce the schema natively, and DeepSeek, Kimi and GLM receive it as an instruction in JSON mode.
No. You pay the providers directly for tokens, with your own keys; the router adds nothing to token prices. The Free plan includes 1,000 routed requests a month (Pro Intelligence 10,000, Developer 100,000, Teams 1,000,000), and prepaid credits cover any beyond that at $5 per 10,000. Only successful requests count. No card for the Free plan.
auto-tooling: the model best at calling tools correctly, scored on the tool-calling suite. auto-best picks the best combined score for general chains; auto-reasoning is best for complex analysis, math and logic.
Yes. Any OpenAI client works with base_url="https://aistupidlevel.info/v1" and your aism_ key; read the x-aism-model header from a raw response to see which model answered. The SDKs and ChatAISL add what an OpenAI client cannot see, such as the routing reason on every answer.
07
Every tool takes the same base URL and key. The integrations hub lists them all; the docs add samples for frameworks and SDKs.
A free account gives you a router key, the Providers page for your own keys, and the request allowance. No card.
1,000 routed requests a month free · your own provider keys · no card