universalagentprotocol.io is built with Next.js, hosted on AWS.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| 15.5.20 | 9 Nov 2026 | |
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| – | 9 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| CDN & Hosting2 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts2 | ||
| – | 9 Nov 2026 | |
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
ns1.vercel-dns.comns2.vercel-dns.comns57.domaincontrol.comns58.domaincontrol.comv=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;User-Agent: * Allow: / Sitemap: https://universalagentprotocol.io/sitemap.xml
# UAP — Universal Agent Protocol > One declarative agent format. Define an AI agent once — instructions, > commands, subagents, skills, MCP servers, hooks, permissions — in > agent.uap.yaml, and pack/unpack it into any harness: Claude Code, Codex, > OpenCode, Cursor, Factory, or Devin. Hub-and-spoke adapters, honest > per-component fidelity reports, secrets never stored in bundles. ## Docs - [Introduction](/docs/): why UAP exists — the N×M agent-portability problem - [The agent format](/docs/format/): the canonical agent.uap.yaml, component by component - [Harness support matrix](/docs/harnesses/): native/emulated/planned per component per harness - [CLI](/docs/cli/): uap pack, unpack, convert, validate ## Source - Spec: https://github.com/BrainbaseHQ/uap/blob/main/spec/SPEC.md - JSON Schema: https://github.com/BrainbaseHQ/uap/blob/main/spec/uap.schema.json - Repository: https://github.com/BrainbaseHQ/uap
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |