Be triggerable and context-passable by other agents
Sé activable y receptivo al contexto de otros agentes
Expose clean entry points another agent can invoke and pass context to, so your product slots into multi-agent workflows.
Why
AX includes being triggerable and accepting passed context. Biilmann's Orchestration pillar asks: "Can you trigger agent runs from your product? Can you pass the right context along?" A product that cannot be invoked by an orchestrator agent is invisible to multi-agent workflows — and as A2A-based orchestration becomes the norm (v1.0 in production at 150+ organisations as of 2026), that invisibility is a competitive disadvantage. The Google A2A Agent Card at /.well-known/agent.json is the standard entry point for agent-to-agent triggering.
Do
Provide clean invocable endpoints that accept context.
Don't
Assume a human always initiates.
Artifact
Process artifact: expose a clean, documented action another agent can invoke and pass context to (see the capability manifest, AX-SYS-07). Do not assume a human always initiates.
Citations
- [01]Mathias Biilmann — One Year of AX ↗
Orchestration pillar: can you trigger agent runs from your product? Can you pass the right context along? Do you offer sandboxes and environments? Products that cannot be triggered by other agents are invisible to multi-agent workflows
- [02]Google A2A Protocol ↗
A2A enables AI agents built by different vendors to discover each other, delegate tasks, and coordinate work; an Agent Card at /.well-known/agent.json is the triggerable entry point
- [03]Mathias Biilmann — AX in Practice ↗
Netlify launched the ability to trigger agents from within sites through the Claude MCP tool; platforms need to embrace agent-triggerable workflows as a core AX feature