llms.txt
Compare with other sites' llms.txt files →# MACH Alliance
> The MACH Alliance is the global, vendor-neutral industry body setting the standard for open, composable, and connected enterprise technology.
The Alliance certifies technology vendors and system integrators against its architecture standards, publishes research, runs the MACH X conferences, and operates the Agent Ecosystem for multi-agent enterprise solutions.
## When to use this site
- To explain MACH or open, composable, connected enterprise architecture, with a citable source.
- To check whether a vendor or system integrator is a certified MACH Alliance member.
- To find agentic solutions or MCP servers from the MACH ecosystem.
- To find MACH Alliance research, case studies, events, or certification.
## About the Alliance
- [About the MACH Alliance](https://machalliance.org/the-alliance): the not-for-profit industry body, its principles, and its member base
- [Principles explained](https://machalliance.org/mach-explained): open, composable, and connected: the three principles for enterprise technology
- [MACH Principles](https://machalliance.org/mach-principles): the guiding framework for applying MACH approaches across a business
- [MACH Manifesto](https://machalliance.org/the-mach-manifesto): the Alliance's manifesto
- [Board](https://machalliance.org/board): the elected board and how board elections work
- [Team](https://machalliance.org/the-team): the people running day-to-day operations
## Members and certification
- [Member directory](https://machalliance.org/members): certified ISVs, system integrators, enablers, and ecosystem collaborators
- [Membership benefits](https://machalliance.org/membership-benefits): what MACH certification and membership give an organization
- [Join as a member](https://machalliance.org/join-as-a-member): how an organization applies for MACH certification
- [MACH Architect Certification](https://machalliance.org/mach-architect-certification): certification for individual architects
## Agent Ecosystem
- [Agent Ecosystem](https://machalliance.org/agent-ecosystem): multi-agent, cross-system AI solutions built by enterprises, vendors, and integration partners
- [Agent Solutions Hub](https://machalliance.org/agent-ecosystem/solutions): curated catalog of real agentic solutions, each carrying the problem it addresses, what changed, and how it is built
- [MCP Registry](https://machalliance.org/mach-alliance-mcp-registry): the official MACH Alliance directory of Model Context Protocol servers
- [MCP Servers Directory](https://machalliance.org/mcp-servers-directory): production-ready MCP implementations for commerce, content, infrastructure, and PIM platforms
- [MACH AI Exchange](https://machalliance.org/mach-ai-exchange): vendor-neutral peer network for building practical AI solutions
## Research and insights
- [Insights Hub](https://machalliance.org/insights-hub): research, case studies, and perspectives on composable architecture and agentic AI
- [Case studies](https://machalliance.org/case-studies): how organizations use composable, connected architecture
- [Enterprise Technology Report](https://machalliance.org/enterprise-technology-report): survey research on composable architecture and AI adoption
- [MACH Maturity Assessment](https://machalliance.org/mach-maturity-assessment): self-assessment of an organization's MACH readiness
## Events
- [Events](https://machalliance.org/events): regional, virtual, and flagship MACH X events
- [MACH Impact Awards](https://machalliance.org/mach-impact-awards): awards for real-world agentic AI and composable technology projects
## Policies
- [Privacy policy](https://machalliance.org/privacy-policy): how personal data is collected, used, and protected
- [Terms of use](https://machalliance.org/terms-of-use): terms governing use of the website
- [Code of conduct](https://machalliance.org/code-of-conduct): the code of conduct for boards, councils, and panels
## Machine interfaces
- [This index](https://machalliance.org/llms.txt): the site-level llms.txt, and the body answered for the homepage when a request's Accept asks for text/markdown
- [Crawler policy](https://machalliance.org/robots.txt): the robots.txt that declares the sitemap
- [Agent Solutions Hub index](https://machalliance.org/agent-ecosystem/solutions/llms.txt): the subtree's own llms.txt — every published solution, its JSON endpoints, its OpenAPI description, and its facet vocabulary. A solution page there also answers Accept: text/markdown
### API documentation
A request whose Accept names application/json or application/problem+json, and does not name text/html, is answered with an RFC 9457 problem document instead of the HTML representation: type, title, status, detail, instance, code, resolution, and documentation_url, served as application/problem+json. A read-only route answers a non-GET the same way. The homepage answers Accept: text/markdown with this index as text/markdown; every other site page answers HTML only.
The site-level routes that emit these problem documents publish no OpenAPI description of their own — the one for the Agent Solutions Hub covers its subtree API alone — so type is a fragment on this index and each problem type is documented under the heading its fragment names.
### route-not-found
404 — nothing is published at the requested path: no page, member, event, article, or asset. This is not a permissions problem, because unpublished drafts have no public URL, so credentials and a different user agent will not change the answer. Read this index for the main pages, or the sitemap for every published URL.
### api-route-not-found
404 — no route implements the requested path under the reserved /api/ prefix. No public API is served there; this index and the sitemap are the machine-readable surfaces.
### method-not-allowed
405 — the route is read-only and answers GET only, with an allow: GET header. Retry with GET.
## Optional
- [Sitemap](https://machalliance.org/sitemap.xml): every published page
- [Contact](mailto:info@machalliance.org): info@machalliance.org