Agent-net , the team building an agent-to-agent marketplace where AI agents discover, trust, and pay each other, has released Webagent , an open source harness for standing up public-facing business agents. So, basically you give it your website, get an agent, and let it talk to other agents. Instead of writing orchestration code, a business fills in a declarative JSON spec, picks 1 provider for each of 9 pluggable slots, and runs webagent serve . Is it deployable? Yes, with caveats. The repo ships under Apache 2.0, builds green, and runs live Slack, WhatsApp, and HTTP agents backed by MCP tools today. It is still labeled v0, and the browser action provider, OAuth-gated MCP, OTel export, and the AgentNet identity and billing layer are listed as not yet built. Slots, providers, picks Webagent is written in Go. An agent is 1 Brain (an LLM plus instruction) over a set of slots defined in core/ . Each slot is a Service Provider Interface with a registry of providers in spi/ and a designated default: Slot Built-in providers Default Retrieval live, keyword, hybrid live Memory session session Guardrail basic, off basic Channel a2a, web, slack, whatsapp (telegram stub) a2a Secrets env, file, static env Presenter text, terminal (QR), web text Model echo, openrouter, gateway echo Action none, demo, mcp none Observability none, log, memory none The design serves 3 audiences on 1 contract: businesses that configure by picking from the menu, businesses that extend by registering a custom provider, and partner companies that ship adapters. Nobody forks the core. Every provider must pass
Source: MarkTechPost