The regional AI development movement connecting talent, data, capital, and policy across the Western Hemisphere.
Led by GENIA Americas · Network: RaceFor.AI · Platform: Glápagos
Most AI used across Latin America and the Caribbean today is built somewhere else, then shipped in. It works in a demo and underperforms in the field, because it was never trained on this hemisphere's languages, economies, or institutions.
The AI Corridor of the Americas is an attempt to fix the actual cause, not the symptom. Not by asking permission to participate in the AI economy, but by building the infrastructure — talent, data, and policy — that lets this hemisphere author AI instead of just consuming it.
This repository is the front door to that effort: the manifesto, the ecosystem map, and the working repositories behind it.
Talent that stays. AI literacy starting in K-12, not bolted on as an elective. Tools built to make teachers and operators more capable, not to replace them. Rooted in the work of Emerging Rule in AI-powered education.
Data that reflects the region it comes from. Glápagos is the technology backbone: an AI DevOps platform purpose-built for multi-jurisdiction deployment across North, Central, and South America, so models are trained and governed with regional data and regional consent, not imported wholesale. See docs/PLATFORM.md for the platform breakdown — what it does, how it's structured, and where the code lives.
Capital and policy that move together. AI infrastructure only compounds when public and private investment move in the same direction. This work has included formal engagement with the U.S. Congress:
- H.Res.649 — 118th Congress (introduced August 8, 2023, Rep. Adriano Espaillat)
- H.Res.836 — 119th Congress (reintroduced October 28, 2025, Rep. Adriano Espaillat)
Both call on the United States to champion a regional AI strategy across the Americas. Neither is enacted law — both are resolutions, referred to the House Committees on Foreign Affairs and on Science, Space, and Technology. That distinction matters and we say so plainly, here and everywhere else we talk about this work.
- Active across 12+ regions, built for 35 nations
- Technology backbone: Glápagos, an AI DevOps platform for multi-jurisdiction deployment
- Partners and collaborators include SingularityNET, Seguritech, and Intermestic
- Press coverage: El Heraldo de México, DPL News Colombia, and a sponsored feature with The Atlantic and Google on government AI adoption worldwide
(Figures as published by RaceFor.AI / GENIA Americas. If you're citing this externally, verify current numbers at racefor.ai — a live network's numbers move faster than any README can.)
| Repository | What it is | Stack | License |
|---|---|---|---|
Glapagos-Backend |
Backend for the Glápagos AI DevOps platform | Python | MIT |
multimodal-ai-americas |
Open research repository for federated, regionally-grounded AI development across the Western Hemisphere | — | Apache-2.0 |
ciudadania-backend |
Server-side code for the CiudadanIA project | — | AGPL-3.0 |
Sites:
- racefor.ai — the AI strategy and deployment network
- glapagos.com — the platform
- GENIA Americas on GitHub
- GENIA Americas on LinkedIn
Read docs/JOIN.md for the specific path for you — developers, educators, policymakers, investors, or press each have a direct route in, no introduction required.
Considering a partnership, investment, or formal engagement? Start with docs/DUE_DILIGENCE.md — it's built so you can verify every claim independently, on Congress.gov and GitHub, before you ever talk to us.
- Policymakers and institutions — see
docs/POLICY.mdfor the legislative record. - Developers and researchers — start with
docs/PLATFORM.mdfor the architecture overview, thenmultimodal-ai-americas; it's the open research repo. - Founders and investors — see
docs/ECOSYSTEM.mdfor the full network map. - Everyone else — read
docs/MANIFESTO.md. It's short.
Contact: admin@genia.ai · Press: prensa@genia.ai
Documentation in this repository is licensed under CC BY 4.0. Code in the linked repositories carries its own license as noted in the table above — check each repo before reuse.