We Built the Missing Layer for AI Agents
Introducing the Autonomous Company Interface (ACI)
An AI agent can call thousands of APIs, write code, query databases, and invoke language models. But until now, there's been one thing it couldn't do reliably:
Determine what an organization is, what it offers, and how to trust it — without scraping or bespoke integration.
🎬 The Launch Video
2-minute explainer — built with AI-generated script, voiceover, and visuals
(replace URL with your browser player if it doesn't auto-embed)
What Is ACI?
ACI (Autonomous Company Interface) is an open specification that lets organizations describe themselves in machine-readable format — designed specifically for autonomous agents.
It's a five-manifest system that any organization can publish alongside their website:
| Manifest | What it tells an agent |
|---|---|
| Identity | Who you are — name, jurisdiction, verifiable identifiers |
| Capability | What you offer — products, services, documentation |
| Knowledge | What your domain is — concepts, terminology, relationships |
| Trust | Why you're trustworthy — certifications, attestations, linked evidence |
| Agent | How to interact — endpoints, auth requirements, interaction methods |
An agent discovers your first manifest via /llms.txt and follows links to the rest. No scraping. No guessing.
Why This Exists
OpenAPI describes interfaces — how to call an endpoint. But agents need organizational context first:
- Who owns this API?
- What business is this company in?
- Are they certified or regulated?
- Can I trust their claims?
- Do they even want autonomous agents interacting with them?
ACI bridges that gap. It's the layer between "I found a website" and "I can safely do business here."
🚀 How You Can Adopt ACI Today
The fastest path — fork the template (it takes 5 minutes):
👉 GitHub: narko4u/aci-pages-template
This GitHub Pages template includes everything: identity.json, capabilities.json, /llms.txt, and a landing page. Replace the placeholders, enable Pages, and you're live. Zero build tools required.
Or explore a live example:
python3 -c "$(curl -s https://raw.githubusercontent.com/narko4u/aci-spec/main/demo/aci-explorer.py)" empirelabs.com.au
This zero-dependency script discovers all five manifests at empirelabs.com.au — our own Level 3 implementation.
The Path Forward
ACI is currently Draft v0.9 — published as an open specification under CC BY 4.0, with MIT-licensed tools. Empire Labs Pty Ltd is the initial steward, with a governance path to transition to a neutral foundation.
The spec repository: github.com/narko4u/aci-spec
The v1.0 milestone requires three independent implementations. I'm actively seeking organizations to implement ACI, validate the draft, and help shape the standard. If that sounds like you, jump in.
ACI agents don't scrape. They read.
🙏 If this resonates: Fork the template. Deploy it. Open an issue with feedback. And if you know someone building in the agentic space — tag them. The standard only matters if we build it together.
Top comments (0)