Install Jentic One Beta

Connect the AI Stupid Level Smart Router API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AI Stupid Level Smart Router API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faistupidlevel.info%2Faistupidlevel" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faistupidlevel.info%2Faistupidlevel" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AI Stupid Level Smart Router API.

Route an OpenAI-format chat completion to the best-measuring model by passing an auto-* routing mode as model to POST /v1/chat/completions

Preview which model a request would go to, plus its fallback chain, with POST /v1/route/preview without calling a provider

Rate a routed answer up or down by its completion id through POST /v1/router/feedback to feed the routing signals

List the available routing modes and routable model ids with GET /v1/models before pinning a model

GET STARTED

Start building with AI Stupid Level Smart Router API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AI Stupid Level Smart Router API for, with concrete tasks.

★ Benchmark-routed completions for your agent through Jentic

An agent that writes code or reasons over documents does better on whichever model currently measures best, and the AI Stupid Level Smart Router picks that model per request. Through Jentic the agent finds the routed chat completion operation by intent, sends an OpenAI-format body with an auto-* routing mode as model, and the router forwards it using your own provider keys. The router key is injected at call time, so the agent never holds it.

Call POST /v1/chat/completions with model set to an auto-* routing mode from GET /v1/models and messages containing one user turn asking to refactor a Python function, then return the routed answer

Dry-run routing decisions before spending

Before committing a large batch of prompts, a developer wants to know which model each would land on and what the fallback chain looks like. POST /v1/route/preview accepts the same body as the chat completions call and returns the strategy, the target model, and the fallback chain; nothing is called or counted. Adding X-ASL-Sandbox set to true answers as if you held a key for every provider.

Call POST /v1/route/preview with header X-ASL-Sandbox set to true, model set to an auto-* routing mode, and a single user message, then report the chosen model and its fallback chain

Closing the loop with answer ratings

Routing improves when answers are rated. After a routed completion returns, an agent or reviewer posts the completion id with a rating of up or down to POST /v1/router/feedback, and those ratings feed the production signals that adjust routing. The id is the response id, also returned as X-AISM-Request-Id.

After a chat completion returns, call POST /v1/router/feedback with id set to the response id and rating set to 'down' because the answer failed its unit test

Budget checks before long agent runs

A long-running agent should check it has room to keep working. GET /v1/usage returns the monthly allowance, remaining credits, and the router key's budget, so a scheduler can pause a batch or switch to sandbox testing when credits run low instead of failing mid-run.

Call GET /v1/usage and, if remaining credits are below the amount needed for the queued batch, stop and report the allowance and key budget

Key Endpoints

8 endpoints — the ai stupid level smart router api routes each chat completion to the model that currently measures best for it on ai stupid level's continuously re-run coding, reasoning, and tool-use benchmarks, using your own provider keys.

METHOD

PATH

DESCRIPTION

POST

/v1/chat/completions

Create a routed chat completion

POST

/v1/route/preview

Preview the routing decision

GET

/v1/models

List routing modes and routable models

POST

/v1/router/feedback

Rate an answer

GET

/v1/usage

Get allowance, credits, and key budget

POST

/v1/embeddings

Create embeddings

POST

/v1/messages

Anthropic Messages pass-through

POST

/v1/chat/completions

Create a routed chat completion

POST

/v1/route/preview

Preview the routing decision

GET

/v1/models

List routing modes and routable models

POST

/v1/router/feedback

Rate an answer

GET

/v1/usage

Get allowance, credits, and key budget

POST

/v1/embeddings

Create embeddings

POST

/v1/messages

Anthropic Messages pass-through

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the router by hand means minting an aism_ router key, pointing an OpenAI client at the /v1 base URL, and handling the separate x-api-key form for the Anthropic pass-through. Through Jentic you install once, import the AI Stupid Level Smart Router API from the API Directory, store the router key once, and your agent calls it.

Permission scoping

The router takes the model and messages in the request body, so rules bound which operations your agent may call, not which model it picks. You choose the operations it may call, so paid ones like chat completions or embeddings are not included unless you add them.

Credential isolation

Your router key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'route a chat completion to the best model' or 'preview the routing decision', and Jentic returns the matching router operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using AI Stupid Level Smart Router API through Jentic.

Is there an AI Stupid Level Smart Router MCP server?

You don't need an MCP server to give your agent the AI Stupid Level Smart Router. Jentic connects it directly from the API Directory: import it, store your router key once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

What authentication does the AI Stupid Level Smart Router API use?

Per its OpenAPI spec, the API uses a router key (prefixed aism_) sent as a bearer token in the Authorization header. The Anthropic Messages pass-through at POST /v1/messages also accepts the router key in the x-api-key header, which suits Anthropic SDKs and Claude Code. GET /v1/openapi.json is open and needs no key. Through Jentic, the router key is stored encrypted by your own Jentic One instance and injected at call time.

Can I see which model the router will pick before I spend anything?

Yes. POST /v1/route/preview takes the same body as POST /v1/chat/completions and returns the strategy, the model the request would go to, and the fallback chain. Nothing is called or counted. Add the X-ASL-Sandbox header set to true to get an answer as if you held a key for every provider.

Can I limit what my agent is allowed to do with the AI Stupid Level Smart Router API?

Yes. For example, write a rule that allows only POST /v1/route/preview, GET /v1/models, and GET /v1/usage. Your agent can then plan routes, list models, and check credits, but it cannot send paid completions or embeddings, and every call it makes is logged.

What are the rate limits for the AI Stupid Level Smart Router API?

The OpenAPI spec does not specify rate limits. GET /v1/usage reports your monthly allowance, credits, and key budget; check https://aistupidlevel.info/contact for current limits.

How do I send a routed chat completion through Jentic?

Search Jentic for 'route a chat completion to the best model', load the createChatCompletion operation, and call POST /v1/chat/completions with model set to an auto-* routing mode from GET /v1/models and your messages. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Do I need my own provider keys to use the router?

Yes. The router forwards requests using your own provider keys. POST /v1/embeddings requires an OpenAI provider key, and POST /v1/messages sends requests to Anthropic with your Anthropic key, with no routing or fallbacks, so model must be a Claude model id.

AI Stupid Level Smart Router API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsbearer, apiKey8 EndpointsREST

For Agents

Send OpenAI-format chat completions that AI Stupid Level routes to the best-measuring model, preview the routing decision and fallback chain first, rate answers, and check monthly allowance and credits.

Use for: I need to send a chat completion to whichever model is benchmarking best for coding right now, Preview which model the router would pick for this prompt before spending anything, List all routing modes and models the router can send requests to, Check whether my router key still has credits left this month

Not supported: Does not host or train models, store provider billing, or run its own benchmarks on demand. Use for routing OpenAI-format requests to the best-measuring model on your own provider keys only.

The AI Stupid Level Smart Router API routes each chat completion to the model that currently measures best for it on AI Stupid Level's continuously re-run coding, reasoning, and tool-use benchmarks, using your own provider keys. It speaks the OpenAI Chat Completions format, so any OpenAI client pointed at the /v1 base URL works, and it adds a route preview that returns the chosen model and fallback chain without calling a provider. It also exposes OpenAI embeddings, a native Anthropic Messages pass-through, answer ratings that feed routing signals, and a usage report covering allowance, credits, and key budget. Sending the X-ASL-Sandbox header set to true tests requests without calling a provider or spending anything.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

30%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

23%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

47%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C+Signals: 1

58%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AI Stupid Level Smart Router API to your agent

Capabilities

Start building with AI Stupid Level Smart Router API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AI Stupid Level Smart Router API

Jentic AI Readiness Score

AI Stupid Level Smart Router API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness