Agent Readiness, Built With Agents: One Week on kondevs.com

In four days, 13 to 16 November 2026, we made 74 changes to kondevs.com, each reviewed, tested and checked on the live site. Most of the code was written by AI coding agents. Every merge and every release still waited for a person's yes. The result is a site that AI agents can find, read, cite and, with permission, publish to.

This is a short account of what that week taught us about three things our clients ask about: agentic readiness, AI-assisted development, and running it all on Cloudflare.

Agentic readiness: being useful to software, not only to people

A growing share of the questions people ask about suppliers no longer reaches a website through a browser. It reaches it through an AI assistant that searches, reads and summarises on someone's behalf. A site that only looks good to people is half finished.

Being ready for agents means three things. First, they can find you: clear, machine-readable descriptions of who you are and what you offer, in the open formats agents already use. Second, they can read you without guessing: every page also available as clean text, every interface described in a public contract. Third, they can act safely: when an agent may do more than read, the rules are explicit, the access is granted by a person, and there is a place to try things without consequences.

What an agent needsWhat we builtWhere to see it
To find youMachine-readable descriptions of the company, its services and its content, in open formats agents already usellms.txt
To read youEvery page also as clean text; every interface in a public contractDevelopers page
To act safelyPublishing with a key a person grants; a public sandbox; a developer kitSandbox

Our October articles covered the first two, the read side. See how we made kondevs.com usable by AI agents and AI agent readiness and LLM visibility. This week was about the third.

Partners and agents with a key from KONDEVS can now publish articles to the site in English and German. Anyone can read what is published, but writing needs that key, and we review every request for one. Next to the live site sits a public sandbox: the same interface on its own data, where anyone can get a short-lived test key and experiment without touching the real site. A small open-source developer kit makes both one command away. The developers page explains the rest in plain words.

One independent tool, Ora, now rates the site 97 out of 100 for agent readiness. We read that as a useful check, not a ranking. The more telling part is what we left out: signals we could not back with a real capability. An agent that trusts a promise a site cannot keep is worse off than one that was never promised anything.

AI-assisted development: agents write, people decide

The 74 changes were written by AI coding agents, working in several sessions at once: one per task, one coordinating the whole. They wrote the code, the tests and the change notes, and they ran the checks. What they did not do was decide. A person approved every merge and every release to the live site, and every change to live data was listed in full before anyone said yes.

AI coding agentsPeople
Write the code, the tests and the change notesDecide what gets built and in which order
Run the checks and compare each step with the live siteApprove every merge
Review each other's work and fix what outside retests findApprove every release to the live site
List every change to live data before it is madeSay yes to that list, or no

Three habits made this work. Small steps: moving the site onto a shared code base took 15 steps, not one big switch, and each could be undone. Proof before trust: every step was compared with the live site, page by page, before it shipped, and 573 automated tests had to pass. Independent review: other AI models were asked to find faults, and outside retests checked the result from the outside. They found real problems, and the same agents fixed them the same day.

The agents also made mistakes, and the process caught them. A generated date that did not match the article it described, a claim about a standard we do not use, a figure that was not ours: each was found by checking against the code and the live site, not by trusting the first answer. That is the lesson we take to client projects. AI agents make a small team fast. Governance keeps fast from becoming careless.

Cloudflare: the platform that makes small steps cheap

The site runs on Cloudflare: pages are rendered at the edge, close to the reader, with articles in Cloudflare's key-value store and images in its object storage. Three properties of the platform mattered this week.

Every change gets its own preview address before it goes live, so a step can be checked on a real copy of the site rather than on a developer's laptop. A release takes seconds, and so does a return to the previous one. And the edge does work we would otherwise build: once our feeds were sent in a form Cloudflare compresses, they became 70% smaller on the wire without a line of new code.

Measured on 15 and 16 November 2026ResultSource
Agent readiness97/100, grade A+Ora
Feeds on the wire after edge compression70% smaller (English and German)our own check
Web standards95%internet.nl
Automated tests573 passing, 0 failingthe site's test suite
Changes in four days74, each reviewed, tested and checked livethe site's code history

The same shared code base now serves several sites on Cloudflare. A fault found on one goes into the base once and reaches the others at their next update. During this week, fixes found on kondevs.com reached a second client site the same day, and fixes found there came back to us.

What this means for an enterprise

None of this is specific to a company website. The questions are the ones every enterprise faces as AI agents start to call its systems: what may an agent see, what may it change, who grants that, where can a partner test safely, and how do you prove the published rules match what actually runs?

The answers are integration work: clear contracts, safe test environments, access granted by people, and releases small enough to check. AI-assisted development makes that work faster; it does not make it optional. We practise it on our own site first, then bring it to enterprise integration and AI agent development projects.

Frequently asked questions

What does agentic readiness mean for a company website?

That AI agents can find it, read it without guessing and, where allowed, act on it safely. In practice: machine-readable descriptions in open formats, every page also as clean text, public contracts for every interface, and explicit rules with human-granted access for anything beyond reading.

Can anyone publish to kondevs.com through its API?

No. Anyone can read published articles, but writing needs a key that KONDEVS grants after a review. A public sandbox gives anyone a short-lived test key to experiment with, on separate data that never touches the live site.

How do you keep AI coding agents from shipping mistakes?

Agents write and check, people decide. Every change is small, compared with the live site before it ships and covered by automated tests; other AI models review the work; and a person approves every merge, every release and every change to live data.

Why run it on Cloudflare?

Because small steps are cheap there: every change gets its own preview address, a release or a rollback takes seconds, and the edge handles work such as compression that we would otherwise build ourselves.

What does this mean for enterprise systems?

The same questions apply when agents call ERP, BPM or partner systems: what an agent may see and change, who grants that, where partners test safely, and how to prove the published rules match what runs. The answers are integration work, made faster, not optional, by AI-assisted development.

Sources

  1. How we made kondevs.com usable by AI agents, kondevs.com
  2. 6. Structured Data That, kondevs.com

Related concepts & services

Key terms: AI Agent, Large Language Model (LLM)

Explore our service: Enterprise Integration & BPM

Related articles

EAI & Integration

Trace IDs everywhere: correlating APIs, queues, BPM and AI calls

A boundary-by-boundary walkthrough of trace context propagation: where traceparent breaks, why async messaging severs spans, how BPM process identity differs from trace identity, and what it takes to make AI calls visible in the same trace waterfall as everything else.

7 min read

Need help with EAI & integration?

Let's look at your integration landscape together, from webMethods and SEEBURGER to APIs and events.

The first conversation is free and without obligation.