Bolt.new AI and Kentico integration: Step-by-Step Guide 2025

To integrate Bolt.new AI with Kentico, you do not connect “Bolt to Kentico” directly. Instead, inside Bolt.new you build a normal front‑end or backend service (Node.js) that talks to Kentico’s real APIs. Kentico exposes content via its Delivery API (REST or GraphQL depending on Kentico version) and requires you to authenticate using an API key. Bolt.new simply runs your code, so the integration is done exactly like any external API integration: store the API key as an environment variable, call the API over HTTPS, parse the JSON, and use it inside your AI workflows or UI.

 

What Integration Really Means

 

There is no special “Bolt–Kentico connector.” What you build is a small service or script inside Bolt.new that:

• Makes HTTP calls to Kentico’s Delivery API (REST or GraphQL)
• Authenticates using a Delivery API key stored in Bolt.new environment variables
• Fetches published content from Kentico
• Optionally posts data back to Kentico (only if your Kentico instance is configured to allow management API access)
• Uses the data in your AI agent, UI, or full-stack app

 

Step‑by‑Step: How to Integrate Kentico with Bolt.new

 

This works for both Kentico Xperience (on-prem) and Xperience by Kentico (SaaS). The exact URL differs, but the integration pattern is identical.

• Create a Delivery API Key in Kentico. In Kentico Admin, go to the Delivery API settings and generate a key. This key lets an external system (your Bolt app) read your published content.
• Add the API key to Bolt.new as an environment variable. Example name: KENTICO_API_KEY. Never hardcode it inside your code.
• Get your Kentico Delivery API endpoint. Examples: Xperience by Kentico (SaaS): https://your-project.kenticocloud.com/delivery Xperience 13/14: often /api/delivery on your site’s domain.
• Inside Bolt.new, write a simple fetch wrapper to pull content.

 

// Example: Node.js route inside Bolt.new to fetch content from Kentico Delivery API

import express from "express";
import fetch from "node-fetch";

const router = express.Router();

router.get("/kentico/articles", async (req, res) => {
  try {
    const apiKey = process.env.KENTICO_API_KEY; // stored securely in Bolt.new env vars

    const response = await fetch(
      "https://your-project.kenticocloud.com/delivery/items?system.type=article",
      {
        headers: {
          Authorization: `Bearer ${apiKey}` // Delivery API requires this
        }
      }
    );

    if (!response.ok) {
      return res.status(500).json({ error: "Kentico API request failed" });
    }

    const data = await response.json(); // Kentico returns standard JSON
    res.json(data);
  } catch (err) {
    res.status(500).json({ error: err.message });
  }
});

export default router;

 

How This Connects to Bolt.new AI Agents

 

Bolt.new’s AI agents can call any route you define. So after creating the endpoint above (/kentico/articles), your AI agent can request fresh Kentico content at runtime. You’re not integrating “AI directly into Kentico”; you’re building a small backend in Bolt.new that fetches Kentico content and exposes it to the agent.

• The agent calls your route.
• Your route calls Kentico’s Delivery API.
• The agent receives clean structured JSON content.

This is the robust and real way to integrate them.

 

Important Real‑World Notes

 

• Kentico Delivery API is read‑only. If you want to update content, you must use Kentico’s management API or custom endpoints (depends on your Kentico version and security settings).
• Keep all API keys in Bolt.new environment variables. Never commit or hardcode keys.
• Your Bolt.new runtime is sandboxed. It can call external APIs, but it cannot open direct database connections to Kentico.
• If you need webhooks, Kentico can send them to publicly reachable Bolt.new endpoints if you expose them with a tunnel (Bolt’s preview URLs usually work for this).

 

Summary

 

Integrating Bolt.new with Kentico means building a small backend within Bolt that uses HTTPS calls to Kentico’s Delivery API with an API key stored as an environment variable. From there, your AI agents and UIs inside Bolt can consume, transform, and use Kentico content in real time. It’s a clean, standard API integration — nothing proprietary, nothing magical.