01✳
AgentStudio
CREATE
Describe an agent in natural language. Vibe-code its behavior, workflows and skills, then export a portable package.
Web analogy Page builder / CMS
Towards an agent-native web
The web was built to share pages.
What if it could share agents?
WebAgentica is a proposed open architecture for agents that anyone can create, publish, discover, download and run — with their own model, memory, tools and budget.
A NEW UNIT OF THE WEB
Thenwebpage.htmlRender information
↓
Nextagent.pkgExecute delegated behavior
Created by one party. Hosted by another. Run by you.
THE CORE PRINCIPLECreate anywhere.Host anywhere.Run anywhere.
01 / THE IDEA
Unbundle the agentic web.
Today's agent platforms frequently combine the tool that creates an agent, the infrastructure that hosts it, and the compute that executes it. The Web took a different path: page builders, hosts and browsers evolved independently.
WebAgentica proposes the same separation for portable AI agents. A creator publishes a signed, versioned agent.pkg. A visitor's AgentSurfer retrieves the package, verifies its provenance, requests appropriate permissions and runs it with a chosen model and runtime. The publisher need not pay for every visitor's inference.
02 / THE ARCHITECTURE
Three independent roles. One shared artifact.
As HTML connects editors, hosts and browsers, agent.pkg is the proposed interoperable artifact connecting studios, hosting providers and surfers.
→
02⬡
AgentHosting
PUBLISH & DISTRIBUTE
Sign, version, host and make agent.pkg reachable. APTP is the proposed package transport contract.
Web analogy Web hosting / HTTP
→
03▶
AgentSurfer
EXPERIENCE & EXECUTE
Open an agent, grant limited authority, and execute it with your own model, memory, harness, tools and budget.
Web analogy Browser + runtime
THE PORTABLE CONTRACTagent.pkgInstructions · workflow · skills · dependencies · requirements · signatures
INSIDE AGENTSURFER
AgentVM conceptual runtime layer
A portable execution environment that supplies model access and mediates capabilities without letting a downloaded package inherit the visitor's authority automatically.
Chosen modelPersonal memoryApproved toolsPermissionsBudgetAudit
03 / WHY THIS IS DIFFERENT
Not just an agent that clicks websites.
Conventional agentic browsing automates existing human-facing pages. AgentSurfer would instead execute behavior deliberately published as an agent package. Browser automation can remain a tool, not the defining architecture.
AGENTIC BROWSER TODAY
Agent drives a webpage
Visiting AI→ clicks →Existing website
The visiting agent infers actions from rendered pages and interfaces.
WEBAGENTICA PROPOSAL
Browser runs an agent
Published agent.pkg→ executes →AgentSurfer
The publisher provides portable behavior; the visitor chooses the intelligence and grants bounded authority.
HISTORICAL PRECEDENT
Java / JVMPortable bytecode
JavaScript / AJAXInteractive Web applications
WebAssemblySandboxed portable computation
WebAgenticaPortable agent behavior + user-controlled execution
Local execution is not new. The proposed distinction is separating the agent publisher from the provider of its intelligence, memory and execution resources.
04 / DESIGN PRINCIPLES
Openness depends on the boundaries.
Independent choice
Any conforming Studio, Hosting service and Surfer should be interchangeable.
Cheap publishing
Serving a package is distinct from paying for inference. Compute happens where an agent is run.
Visitor control
Choose local or remote models, memory, tools and execution limits.
Verified, not blindly trusted
Signatures verify provenance, not safety. Sandboxing and capability grants remain essential.
Open discovery
Agents can be resolved and discovered across independent registries and naming systems.
Composable agents
Agents and skills can be reused and combined without requiring a single vendor's stack.
05 / RESEARCH DEMONSTRATION
See an early browser-based prototype.
The existing WebAgents research prototype illustrates a signed agent package opened in a browser extension. This is not a demonstration that all proposed WebAgentica or APTP capabilities are implemented.
WebAir is a fictional demonstration airline. Flight results, prices and bookings shown in the demo are simulated.
06 / RESEARCH & OPEN DEVELOPMENT
Read the work. Help shape the contracts.
PAPER · PDFWebAgents: Unbundling Agent Creation, Hosting, and ExecutionRead the underlying research →TALK · PDFA Browser for Agents: Toward the Agent-Native WebView the research talk →OPEN SOURCE · GITHUBWebAgentica source codeExplore code and specifications ↗ECOSYSTEM · DISCOVERYNANDA IndexExplore agent discovery infrastructure ↗
Architecture status. WebAgentica is the proposed umbrella name and architecture described on this page. AgentStudio, AgentHosting/APTP and AgentSurfer/AgentVM describe intended roles and interfaces; conformance across independently built implementations remains a research goal.
THE OPEN QUESTION
What would the web look like if publishing an agent were as ordinary as publishing a page?
Not a single vendor's platform. A shared foundation for independently created, hosted and executed agents.
View the code on GitHub ↗