> For the complete documentation index, see [llms.txt](https://wikiedoc.guru-soft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wikiedoc.guru-soft.com/gt/integraciones-y-servicios/catalogo-de-codigos-1/sat/tipos-de-personeria.md). # Tipos de personería
ValorDescripción
719ASOCIACIÓN CIVIL
720ASOCIACIÓN COMUNITARIA Y DE DESARROLLO
721OTRO TIPO DE ASOCIACIÓN
723ASOCIACIÓN DE TRANSPORTE
724ASOCIACIÓN DE VECINOS
725ASOCIACIÓN EDUCATIVA, CULTURAL O DEPORTIVA
726ASOCIACIÓN EMPRESARIAL, AGRÍCOLA, ARTESANAL, INDUSTRIAL Y OTRAS
727ASOCIACIÓN MÉDICA Y DE SALUD
728ASOCIACIÓN SOLIDARISTA DE EMPLEADOS
729CÁMARA
730GREMIAL
731COMITÉ
732SINDICATO
733ORGANIZACIÓN NO GUBERNAMENTAL
734PARTIDO POLÍTICO
735IGLESIA CATÓLICA
736OTRA ENTIDAD RELIGIOSA
737COLEGIO DE PROFESIONALES
739CENTRO EDUCATIVO POR COOPERATIVA
740UNIVERSIDADES
715ENTIDAD DEL ESTADO
738CENTRO EDUCATIVO PÚBLICO
716MUNICIPALIDAD Y SUS EMPRESAS
718DIPLOMÁTICO, ORGANISMO INTERNACIONAL O MISIÓN DIPLOMÁTICA
2635FUNDACIÓN
2719COMITÉ CÍVICO
2744UNIVERSIDAD PRIVADA
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wikiedoc.guru-soft.com/gt/integraciones-y-servicios/catalogo-de-codigos-1/sat/tipos-de-personeria.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.