Making ddq.nl agent-native
ddq.nl runs on infrastructure operated by DDQ. We rebuilt the site so its public information is consistent for people, crawlers and software agents.
What changed
One source of truth. The site's facts live in a canonical JSON file. A build script generates llms.txt, Markdown content, /api/company.json, the sitemap, security information and agent-discovery documents.
MCP endpoint. AI agents can query the site over the Model Context Protocol at /mcp/ using Streamable HTTP without authentication. The tools return the company profile, cloud services with live status, and contact information. The endpoint is implemented in plain PHP without application dependencies.
Live status. The cloud page now shows the actual up/down state of our self-hosted services, checked every five minutes from this machine. No third-party status service.
Discovery and security. The site publishes AGENTS.md, OpenAPI, WebMCP and MCP discovery, an API catalog, security.txt (RFC 9116), WebFinger, structured data and explicit crawler policy.
Why
DDQ develops on-premise and self-hosted systems. The website uses the same approach: machine-readable interfaces, observable service status and infrastructure operated by DDQ.