If you're building AI agents that need to comply with the EU AI Act or verify jurisdictional boundaries, this server routes tasks through a four-gate compliance layer: Ed25519 signature verification, H3-based jurisdiction resolution (mapping hexagonal cells to regulatory frameworks like GDPR and FINMA), delegation chain validation, and GEOS-backed geometry checks. It's built on the GNS Protocol and exposes endpoints for agent registry lookup, H3 cell jurisdiction queries, and compliance-aware task routing. Reach for this when you need cryptographic proof that an AI operation occurred within approved territorial boundaries, or when you're orchestrating geospatial agents that must leave an auditable breadcrumb trail for regulators.
Geo-Identity Agent Navigation & Tasking
The first AI orchestrator that knows where it is.
GEIANT is a geospatial AI agent orchestration runtime built on the GNS Protocol. It is a direct competitor to LangChain, CrewAI, and AutoGen — with one structural difference: every agent has a cryptographic identity bound to an H3 territory, and every task is routed through a compliance enforcement layer before dispatch.
LangChain doesn't know where it is. GEIANT does.
In GEIANT, agents are ants. Ants are the canonical model of emergent collective intelligence from simple agents following spatial rules. Ant Colony Optimization (ACO) is a real algorithm used in routing and pathfinding. The colony is the orchestrated workflow. The territory is the H3 grid.
AntIdentity) is an agent with a GNS Ed25519 keypair + H3 territory + facet scope + trust tierL6 Multi-Agent Orchestration — task graph, delegation chain enforcement
L5 IDUP Settlement Layer — Stellar payment routing per operation
L4 MCP GIS Switchboard — GDAL / PostGIS / ArcGIS / QGIS / EO models
L3 Perception Layer — IBM Prithvi, Microsoft Clay (EO Foundation Models)
L2 Geometry Validation Layer — GEOS-backed guardrails, self-intersection detection
L1 Geospatial Router — H3 jurisdiction matching, TierGate enforcement
L0 Agent Identity & Registry — Ed25519 + H3 + GNS-AIP (LIVE in gns-node)
Phase 0 (this repo): L0 + L1 + L2 core logic, tests, and API scaffold.
geiant/
├── packages/
│ ├── core/ @geiant/core — types, router, validation, registry, jurisdiction
│ └── sdk/ @geiant/sdk — developer-facing SDK (Phase 1)
├── apps/
│ └── api/ @geiant/api — Express REST API
└── docs/ Architecture docs, ADRs
Every task passes through four gates before any ant is selected:
Only tasks that pass all four are dispatched. The router is a compliance enforcement point, not a load balancer.
# Install dependencies
pnpm install
# Run tests
pnpm test
# Start dev API
pnpm dev
# Test routing endpoint
curl http://localhost:3100/health
curl http://localhost:3100/registry
curl http://localhost:3100/jurisdiction/8728d55ffffffff # Rome H3 cell
curl http://localhost:3100/route/test
| Feature | LangChain | CrewAI | GEIANT |
|---|---|---|---|
| Agent identity | API key | API key | Ed25519 GNS keypair |
| Task routing | Capability + cost | Capability + cost | H3 jurisdiction + compliance |
| Audit trail | Logs | Logs | Virtual breadcrumbs (crypto) |
| Geometry validation | None | None | Built-in guardrails |
| Human accountability | None | None | Delegation chain |
| Regulatory compliance | Manual | Manual | Proof-of-Jurisdiction |
GNS Protocol Provisional Patent #63/948,788 (Proof-of-Trajectory).
GEIANT's Proof-of-Jurisdiction is a second patentable claim extending this.
Protocol spec: CC-BY
Core library: Apache 2.0
Managed runtime: Proprietary
GNS Foundation | Globe Crumbs Inc. | ULISSY s.r.l.
Via Gaetano Sacchi 16, 00153 Roma | ulissy@pec.it | gcrumbs.com