Domain and utility agents
Each calls a real public API (no key required unless noted), written as a minimal A2A example in Rust or Go.Framework demos
The same small task — answering a question from Wikipedia — implemented once per framework, showing that A2A and zero-code instrumentation work regardless of what you built with.
Use these when deciding which framework to build in. Each is a complete, deployable reference for wiring that framework to A2A.
Reusable skill snippets
Single-capability building blocks meant to be copied into an agent rather than deployed:arxiv-search, http-request, tmdb-search, web-search, wikipedia-search.
Auto-deploying at startup
SEED_AGENTS is a space-separated list of image references, read once at server boot:
Deploying one yourself
Plans: Enterprise (dedicated or self-managed). Self-hosted: Enterprise license.
nasiko registry connect points at. See Artifact registry. nasiko import and nasiko deploy themselves work on every plan and on any self-hosted server.
nasiko import asks your Nasiko cluster to pull the image from the artifact registry and deploy it, so you don’t need Docker locally. A short owner/name[:tag] reference is resolved against the registry you connected with nasiko registry connect. You can also pass a full registry.host/owner/name[:tag]. The registry host must be one your server allows: registry.nasiko.com, the registry URL set in the dashboard settings, or a host listed in REGISTRY_IMPORT_ALLOWED_HOSTS. See Configuration.
To deploy a local image instead, use nasiko deploy <image>, which pushes it to your cluster’s built-in registry and starts it.
See Agent Development Lifecycle for the full workflow and the artifact registry guide for everything published beyond this set.
Related
Agent Development Lifecycle
Scaffold, run, and deploy your own agent.
A2A agents and frameworks
What makes an agent discoverable and routable.
Artifact registry
Browse and publish beyond the curated set.
Agent hosting
How a pulled image becomes a running container.