TACO
The A2A Construction Open-standard
One ontology. Every construction AI agent. Interoperable by default.
The Construction AI Fragmentation Problem
AI agents are entering the construction ecosystem fast — but they're being built in isolation. Different formats, different APIs, no shared vocabulary.
A2A Is the Protocol. TACO Is the Language.
The A2A protocol lets agents talk. TACO gives them something meaningful to say — typed construction workflows, schemas, and discovery that A2A doesn't define.
Task types · Typed schemas · Registry · Scopes
Agent Cards · Tasks · Messages · SSE · Auth
Every TACO agent is a valid A2A agent.
Non-TACO clients ignore the extensions gracefully. Zero lock-in — just richer context for construction.
Deep dive into the A2A protocolWhat TACO Standardizes
Click each layer to explore
Watch the Pipeline
BOM → Estimating Agent → Supplier Quote → Enriched Estimate
Click "Run Pipeline" to watch typed schemas flow between agents
Get Started in Minutes
from taco import ConstructionAgentCard, ConstructionSkill
card = ConstructionAgentCard(
name="My Electrical Estimating Agent",
trade="electrical",
csi_divisions=["26"],
skills=[
ConstructionSkill(
id="generate-estimate",
task_type="estimate",
input_schema="bom-v1",
output_schema="estimate-v1",
)
],
)
card.serve(host="0.0.0.0", port=8080)Design Principles
Ontology, not protocol
TACO builds on A2A using its native extension points. Every TACO agent is a standard A2A agent. Zero lock-in.
Agents are opaque
Collaborate without exposing internals. Pricing models, proprietary logic, and trade secrets stay private.
Open and composable
Apache 2.0. The spec, schemas, and SDK are open source. The registry is a shared resource.
Construction-native
Designed for how construction works — by trade, CSI division, project phase, and platform.
Shape the Standard
TACO is early stage and open source. We're looking for construction technology companies, trade contractors, and platform vendors to help define the schemas.
Deep Dive: The A2A Protocol