Build and deploy AI agents with tool use capabilities.
An agent is a loop: a model reasons, your code acts, results flow back into the next prompt. The framework running that loop, whether LangChain, LlamaIndex or your own code, needs one thing from a hosting provider: a reliable OpenAI-compatible endpoint. HostYourAI provides exactly that, serving open models like Llama, Qwen and DeepSeek with vLLM on European GPUs, so pointing your framework's base_url at hostyourai.com is the entire integration.
Agents are unusually data-hungry. To be useful they read your CRM records, internal wikis, codebases and inboxes, and all of that context lands in prompts. That makes the jurisdiction of the inference endpoint a bigger deal for agents than for most other LLM workloads.
A chatbot sees what a user types; an agent sees what your systems contain. Tool results, database rows and document contents all pass through the model. Processing that traffic in European datacenters under a Data Processing Agreement, with no training on customer data, keeps your internal data governed the way your DPO expects.
When an agent touches production systems, someone will ask where the intelligence runs. With a US provider the honest answer involves the CLOUD Act and transfer frameworks. With HostYourAI the answer is short: a Dutch company, inference in multiple European regions, a public subprocessor list. Sectors like legal and healthcare often cannot accept anything less.
Many European organizations have purchasing rules that require EU data processing before a pilot can even start. An EU endpoint with a DPA, AES-256 encryption at rest and a 99.9% uptime SLA answers the standard security questionnaire directly, which shortens the path from prototype to approved project.
To be clear about the division of labor: HostYourAI does not sell an agent product. You bring the framework; the platform serves the model. Your orchestration loop sends messages to /v1/chat/completions on the shared EU Inference Router or a dedicated instance, parses the response, executes tools in your own runtime, and feeds results back. Tool execution and decision logic live entirely in your code, which is where you want them: your credentials never leave your environment. One managed piece helps: link a knowledge base to the Router or instance and relevant context from your documents is injected into completions automatically, so your agent grounds its answers without you building retrieval first.
| Agent building block | Who provides it |
|---|---|
| Model inference, streaming, uptime | HostYourAI |
| Agent framework and orchestration loop | You (LangChain, LlamaIndex, own code) |
| Tools and their execution | You, in your own runtime |
| Document grounding | HostYourAI, via the knowledge base link |
| Memory and state between steps | You, in your own storage |
Any framework that accepts an OpenAI base URL works unchanged. Here is the plain SDK in JavaScript running one reasoning step on Mistral 7B, the same call your framework makes under the hood:
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://hostyourai.com/api/v1",
apiKey: "hyai-...",
});
const step = await client.chat.completions.create({
model: "mistral-7b",
messages: [
{ role: "system", content: "You plan the next action. Reply with one action name and its input as JSON." },
{ role: "user", content: "Find open invoices for customer 8841 and draft a reminder." },
],
});
console.log(step.choices[0].message.content);from openai import OpenAI client = OpenAI( base_url="https://hostyourai.com/api/v1", api_key="hyai-...") client.chat.completions.create( model="llama-3.3-70b", messages=[{"role":"user","content":"Hallo!"}])
No. You run open models on EU GPU infrastructure and build agents on top with your own framework. The OpenAI-compatible API is the integration point.
Yes. Both accept a custom base URL for OpenAI-compatible endpoints, so existing chains and agents run against EU-hosted models unchanged. The migration guide covers the details.
In your own environment. The model returns text; your code decides what to execute. API keys for your internal systems never pass through HostYourAI.
Larger instruction-tuned models follow multi-step instructions more reliably; smaller ones handle simple routing cheaply. Compare options in the Model Garden and test them in the Playground.
Yes, link a knowledge base to the Router or your instance and relevant context is injected into completions automatically. Non-streaming responses include the sources used.
Agents make many calls per task, so start on the per-token Router. Move to a per-hour dedicated instance when you need isolated, predictable capacity.
From model hosting to a customer-facing API, it is built for developers and businesses who want their AI running on infrastructure they actually control, inside the EU.
Your data and your models stay on European GPUs. GDPR-friendly by design.
Llama, Qwen, DeepSeek, Mistral, FLUX and plenty more. Pick one and it is warm in minutes, with no DevOps on your end.
Point your existing client at the Router and keep your tools. No rewrite, no lock-in.
No infra to manage. Pick a model, get an OpenAI-compatible URL, ship.
Choose from the Model Garden or paste any HuggingFace ID. Set the VRAM and pick an EU GPU.
We deploy vLLM, run readiness probes, and hand you a warm OpenAI- and Anthropic-compatible URL plus an API key.
Point your client at the Router. It auto-routes to a warm instance, idles GPUs when nobody is online, and logs every request.
The Router speaks the OpenAI and Anthropic APIs, so it drops straight into the clients and SDKs your team already runs. Just change the base URL.
Try HostYourAI for freeIf a US cloud is off the table, HostYourAI gives you the same developer experience on European infrastructure.
Citizen data that legally has to stay in the EU, with full auditability.
Finance, healthcare and legal teams under GDPR, DORA and the AI Act.
Ship AI features your customers trust, without a US sub-processor.
Deliver private AI for clients on infrastructure you can stand behind.
Yes. HostYourAI runs open models on GPUs in European datacenters via vLLM. Your prompts and outputs never leave the EU and there is no US cloud provider in the chain.
Yes. All processing happens inside the EU, a Data Processing Agreement (DPA) is available and the subprocessor list is public. Open weights also mean no training on your data.
Yes. Point your existing OpenAI or Anthropic client at our Router (https://hostyourai.com/api/v1), change only the base URL and API key. No rewrite, no lock-in.
Pay-as-you-go on one prepaid credit balance: the shared router per token or a dedicated GPU per hour. Free to start, no minimum, no fixed monthly fee.
Text and image models on dedicated EU GPUs. Every model tested on our own hardware.
Explore more about EU-hosted AI on HostYourAI.
Host AI chatbots on European infrastructure. Customer service, internal assistants, and more with GDPR compliance.
Read more →Fine-tune LLMs for your specific use case. LoRA, QLoRA, full fine-tuning on dedicated GPUs.
Read more →Point your Anthropic client at our Router through a /v1/messages shim and run open models on European GPUs. Drop-in, EU-hosted, no rewrite.
Read more →Chat with dedicated instances and Router models in the Playground. Test prompts, compare models and then see per-request usage and latency.
Read more →A drop-in OpenAI-compatible API on European GPUs. Change only the base URL and run open models, GDPR-friendly, without rewriting your code.
Read more →Deploy any open model on a dedicated European GPU with vLLM. Your own endpoint, encrypted upstream keys, idle when nobody is online.
Read more →