Machine-Readable by Design

IIO provides product information in a structured, open way — for AI agents and technical reviewers.

What's available here

This page explains IIO's machine-readable interfaces. Product information from Intelego GmbH — — commercial, no open license under the OCC model.

JSON Data Endpoints

Fetch the real architecture data from the live system:

curl https://iio.space/data/stats.json
curl https://iio.space/data/capabilities.json
curl https://iio.space/data/flows.json
curl https://iio.space/data/solutions.json

Example Response: stats.json

{
  "blocks": 524,
  "layers": 259,
  "modules": 274,
  "flows": 683,
  "flows_running": 147,
  "domains": 19,
  "tenants": 35,
  "iso_42001_score": 82,
  "eu_ai_act_class": "Limited Risk (Art. 52)"
}

llms.txt — Agent Context

Machine-readable context file for AI models (standard: llmstxt.org)

curl https://iio.space/llms.txt

Integration for Coding Agents

For agents working within IIO, extended channels are available:

• MCP (Model Context Protocol) — 64 governance tools, Anthropic Claude, OpenCode, Cursor
• A2A (Agent-to-Agent) — Google A2A Protocol 2025

Data Protection

✓ No internal secrets: Public files under /data/ are filtered:

• Hostnames, IPs, server IDs: removed
• Tenant names (except public ones under stats.tenants): removed
• Architecture, technology, building blocks, flows: public

Commercial product information — not an open dataset.

Further Integration

Cooperation and API documentation: see /en/kooperation