MCP
For AI assistants
MCP lets AI assistants such as Claude, Cursor and others fetch hvilkenAI data directly inside the conversation. Ask about model choice and get answers based on updated benchmark data.
Connect MCP →Integrations
hvilkenAI data is available through API and MCP. Connect independent benchmark signals directly to AI assistants, internal systems and analysis workflows. Over 350 AI models are evaluated daily for Nordic-language use.
MCP
MCP lets AI assistants such as Claude, Cursor and others fetch hvilkenAI data directly inside the conversation. Ask about model choice and get answers based on updated benchmark data.
Connect MCP →API
REST API for integrating benchmark data into applications, dashboards, routing logic or internal analysis. Free access works without an API key.
View endpoints →MCP
Add hvilkenAI to Claude Desktop, Cursor or another MCP client to fetch benchmark data directly in the conversation.
Add this server URL in the MCP settings or as a Custom Connector:
https://mcp.hvilkenai.no/mcpOnce connected, ask Claude naturally. Here are examples you can type directly into the conversation.
API
REST API for integrating benchmark data into your own applications, dashboards or analysis workflows.
https://api.hvilkenai.no| Endpoint | Description |
|---|---|
/v1/today | Today’s benchmark results |
/v1/history | Historical results |
/v1/report/latest | Latest weekly report |
/v1/recommend | Recommended model for a use case |
/v1/orchestrator | Orchestrator ranking |
/v1/models | Model overview |
These examples work without an API key. Add a bearer token for Pro access.
curl https://api.hvilkenai.no/v1/today?lang=nocurl "https://api.hvilkenai.no/v1/recommend?use_case=writing&lang=no&budget=any"curl "https://api.hvilkenai.no/v1/history?model=Claude+Sonnet&lang=no&days=7"curl https://api.hvilkenai.no/v1/orchestrator?lang=nocurl --oauth2-bearer API_KEY https://api.hvilkenai.no/v1/today?lang=noPro access
| Feature | Free | Pro |
|---|---|---|
| Data | Delayed | Real time |
| Models | Short selection | More models from the daily selection |
| History | Short history | Full history |
| Languages | Norwegian, Swedish, Danish | Norwegian, Swedish, Danish |
| Weekly report | Yes | Yes, with more detail |
| MCP | Yes | Yes |
| API | Yes | Yes |
Pro access
We offer extended access for consultants, developers and companies that need real-time data, history and reliable integrations — through both MCP and API.
Contact us to discuss what you need:
erik@hvilkenai.nohvilkenAI is independent and is not funded by the AI companies we test.
Use this data basis as a practical decision aid, not as an advertising list. HvilkenAI is built to make AI selection easier when the market changes quickly and model names alone say little about real quality.
Start with the task you actually need to solve. A model that is good at short chat is not automatically best for long documents, code, customer-facing text, research or work involving sensitive information. Consider language quality, price, speed, stability and how much editing the answer requires before choosing a subscription or API.
We evaluate over 350 AI models and present the most useful signals in a format that works for everyday users, students, businesses and developers. The exact calculation is proprietary, but the assessment is based on standardised tasks, updated benchmark data and editorial review of whether the recommendations make sense in practical use.
For important decisions, run a small test of your own: use the same prompt, language and expected format in two or three relevant models. Look at precision, source handling, tone, speed and how easy the answer is to verify. That makes the benchmark a time-saving starting point, not a final answer you must follow blindly.
Use the links on the page as well. One page rarely gives the whole picture: the benchmark shows today’s numbers, the AI test translates your need into concrete recommendations, and the privacy/terms pages explain which data and limitations you should consider. Used together, these sources make the choice more robust than following a model name from social media.
If the result will be used at work, document why the tool was chosen: which task it solves, which alternatives were considered, which data should not be shared and how the answer will be quality-checked. That makes it easier to switch model later if price, quality or provider terms change.
When a page is included in the sitemap, it should also stand on its own as a useful explanation. That is why we emphasise practical choices, concrete control questions and clear limits for how data can be used.
The goal is that the reader can move on with a safer choice after a few minutes, without already knowing every model or provider.
Pay particular attention to whether the recommendation fits the language, price and risk in your own situation.
In short: choose what you can verify.
Choose free or low-cost first when the task is simple, risk is low and you can verify the answer yourself.
Paid models can be worth the cost when documents are long, precision matters or you save real working time.
If the need is unclear, start with the test and benchmark before committing to a provider.