Team
Talk to a person

Ask How it works AI

Explains how customers, you and other AI agents work with your WebAgents, and the ADK-Rust kernel behind them.

How do customers talk to my WebAgents?Can other AI agents buy from my site?What is the ADK-Rust kernel?

You're talking to AI. It answers only from this site and never guesses.

How it works

How we move your site, and what runs it after.

The detail behind the home page: every step of the Move, the sealed rooms, going live, the new site and its WebAgents, and the machines on Vultr.

Live numbers

Read from receipts and the database at Sun 8 Nov, 19:49 EAT. Nothing here is typed in.

How your WebAgents work

Three kinds of conversation, one team.

Your customers and your WebAgents

Visitors ask your site's desks anything, at any hour. Each desk says it's AI, answers from your own pages, shows the page it used, and passes anything that needs a person to you.

You and your WebAgents

Your Chief WebAgent briefs you each morning. The others ask before anything that costs money or makes a promise, and you answer with one tap on your phone. You can read any conversation and take it over.

Other AI agents and your WebAgents

A customer's AI assistant or agent comes in through the agent door. Your site says what agents may do, over AWP and MCP, and an order from an agent waits for your OK.

The Agentic Web Protocol

One website, two interfaces.

More of the web is now read by AI assistants acting for people. An Agentrix Website serves both: pages for people, and a structured interface for AI agents, built on ADK-Rust's Agentic Web Protocol (AWP).

For people

A clear website, conversations with your WebAgent desks, forms and approvals, as people expect.

For AI agents

A manifest at /.well-known/awp that says what your business offers, what's current, what an agent may do and when it must ask you.

One set of facts

Both read the same published facts, prices and policies, so an agent never has to guess what a person would see.

Inspect this site's agent manifest · How AWP works, on adk-rust.com

The technology

Built on the ADK-Rust kernel.

Agentrix is written in Rust on ADK-Rust, Zavora's open-source agent development kit. Its kernel lets each WebAgent work on its own while you stay in charge.

One job each

Every WebAgent has one job, its own tools and a list of things it never does without you.

Dials, not blind trust

Each job has a dial for how much it may do alone. Only you turn a dial up, and money and promises always ask first.

A record you can check

Every decision you approve is signed and kept as a receipt you can open and verify.

Open doors for agents

Other agents reach your site over AWP and MCP, so it works with the assistants your customers already use.

The problem

Small-business websites sit still, and many are quietly hacked.

39.4%

of all websites run on WordPress.

Source: W3Techs, 7 Nov 2026

  • Nobody answers at night.

    Questions arrive through forms nobody watches. Whoever answers first wins the customer.

  • Its infections are invisible to the owner.

    Injected scripts, spam links and webshells hide in plain sight. A normal migration copies them across.

  • AI agents can't use it.

    Customers now send AI agents to ask and to order. A brochure site leaves them reading screenshots.

The Move

Your site, moved through sealed rooms, step by step.

Seven steps. The four in dashed boxes run in sealed rooms on a separate Vultr machine that holds no keys. Every step ends in a signed receipt.

  1. 01

    Assess

    A sealed crawl, and a report with evidence for each finding

  2. 02

    Claim

    Prove you own the site, by DNS or a file

  3. 03 · sealed

    Replay

    The old WordPress runs in a room with no route out

  4. 04 · sealed

    Clean

    Infections set aside and explained in plain words

  5. 05 · sealed

    Rebuild

    A model writes the new site; a room builds it

  6. 06 · sealed

    Prove

    At least 95% parity, page by page

  7. 07 · you

    Go live

    Only on your passkey, with undo for 30 days

The first live Move: fixture.agentrix.website

Live since Sun 8 Nov 2026
  • Replay14.3 sRead 50 pages and 8 files in a sealed replay · receipt
  • Clean37.9 s50 pages clean; 67 items left behind · receipt
  • Rebuild27.9 sRebuilt 50 pages · receipt
  • Prove14.7 sParity 98.8%; release 1 is ready for you · receipt

In sealed rooms for 1 min 35 s in all. The target is your go-live card within 10 minutes for a 50-page WordPress site. Model cost of the whole Move: $0.23, on Anthropic's Claude. Times come from the step records; each step's receipt opens and verifies in your browser.

The model writes code

A model writes each page of the new site. A sealed room builds and renders it with no network. Errors go back to the model, up to three tries.

A browser in a room

A browser reads the old site inside a room, and a vision model compares old and new page by page. A page below 95% waits for a person.

Containment

Nothing the old site tries gets out.

  • Process isolation

    A separate VX1 machine. Each job runs in a gVisor room: read-only, not root, with no capabilities.

  • No secrets in the sandbox

    No keys on the sandbox machine. The proxy refuses the cloud's metadata address.

  • Hard limits

    Caps on CPU, memory, processes and time for every job.

  • Rooms are destroyed

    Every room is destroyed after its job, and the signed receipt says so.

The gauntlet

9/10

attacks contained on the last run, Sun 8 Nov, 19:10 EAT. Computed from receipts, never typed in. Open the receipt

  1. Redirect to Vultr instance metadataContained
  2. Link into the platform's loopback consoleContained
  3. Hidden text aimed at AI agentsContained
  4. Hidden SEO spam linksContained
  5. Cloaking mu-pluginContained
  6. Webshell in uploads with a MIME mismatchContained
  7. Obfuscated miner-style footer scriptContained
  8. Replayed PHP phones homeContained
  9. Build hook fork-bombs and allocates 8 GBGot through
  10. Visitor prompt to the ConciergeContained

Go live

Live only on the owner's say-so.

The go-live card for fixture.agentrix.website

Go live: your new site

Parity
98.8%, target 95%
Left behind
67 items, with reasons
Without asking
Only work that can be undone
Old site
Kept as a fallback
Undo
One tap, for 30 days

The passkey signs this card.

Its challenge commits to the card's fingerprint: the release's digest and the site's charter. Without a passkey, an authenticator code is bound to the same fingerprint.

Only then is the release signed.

The edge serves signed releases only. A release that fails its check is refused, and the last good one stays up.

Live 0.0 s after approval.

Measured on the first live Move, from the approval with a passkey to the switch. WebAgents never go live by themselves.

The new site

It answers people and their AI agents.

Ask this site

Sample · Kilele Bakery

  • Answers come from the site's own pages, and cite the page.
  • When the site doesn't say, it says so and passes the question to the owner.
  • It can't be talked into a discount, and the owner sees the attempt.

The agent door

GET  /.well-known/awp
POST /mcp  request_custom_order
→ held, waiting for the owner
  • The site declares what agents may do, over AWP and MCP.
  • An order from an agent raises the owner's approval card.
  • The agent checks back for the owner's answer.

The agent race

One custom order, placed by a customer's AI agent twice: on the old site by reading screenshots, and on the new site through the door.

The owner console

What needs you, on your phone.

Today
The brief, questions visitors passed to you, and model spend against your daily limit.
Decisions
One card each. Approve with a passkey, or decline.
The Move
Every step live, with its time and receipt, and undo in one step.
Trust
Every receipt opens and verifies in the browser, beside the gauntlet score.
WebAgents
A dial per job for how much each may do without asking. Only you turn it up.
The owner console: the Chief WebAgent's brief, two decisions waiting and the day's AI spend, on the Kilele Bakery sample
The same console on a laptop, on the Kilele Bakery sample. Screenshot, Sun 8 Nov.

The WebAgents

Nine WebAgents, each with one job.

Each WebAgent has one job, a budget, and a dial for what it may do without asking. Each wears a living mark in its site's own colours, which moves only while it works. Visitors always see when they're talking to one.

  • Chief WebAgentBriefs you and routes decisions
  • ConciergeThe front desk, day and night
  • SalesLeads, quotes and bookings
  • EditorKeeps every page up to date
  • ReputationDrafts replies to reviews for you to approve
  • CashierOrders and payments
  • GuardianWatches the site and can roll it back
  • CaretakerDomains, backups and costs
  • MoverThe Move, then hands over

Built on Vultr

Hostile code runs where no keys live.

  • Owner's phone
  • Visitors
  • Customers' AI agents

HTTPS

Vultr Cloud Compute

Control VM

  • Caddy and TLS. In: ports 80 and 443 only
  • agentrix-node: sites, console, the Move
  • Model Gateway: the only holder of model keys
  • SQLite and the content store

VPC, signed jobs

Vultr Cloud Compute VX1

Sandbox VM, sealed

  • A runner that answers control only
  • Rooms: Docker and gVisor, capped
  • One egress proxy per room
  • No secrets. No public inbound.

Proxy only

Vultr Cloud Compute

Fixture VM

Zavora's infected WordPress, for the gauntlet

Vultr Serverless Inference

Model calls go through the gateway by purpose. Now on Vultr Serverless Inference, since Sun 8 Nov 2026 (receipt):

  • briefqwen3.8-27b
  • buildqwen3.8-27b
  • conciergeqwen3.8-27b
  • decideclef
  • embedqwen3-embedding-4b
  • imagez-image-turbo
  • rerankbge-reranker-v2-m3
  • screennemotron-3.5-content-safety
  • vision-paritydeepseek-v4.1-flash-1017
  • voice.listenwhisper-large-v3-turbo
  • voice.livevoxtral-mini-4b-realtime
  • voice.speakqwen3-tts-12hz-1.7b

Vultr Object Storage

Every blob and signed receipt is copied to a bucket each minute, and read back if a file is lost.

VPC, firewalls and DNS

Created from the repository through the Vultr API.

Blue border: a Vultr product. Dashed: sealed, untrusted work. Coral: holds the model keys.

Trust promises

Our promises to you and your customers.

  1. Nothing changes until you say goThe old site is untouched until go-live, and undo is one tap for 30 days.
  2. Your WebAgents ask firstBefore anything that matters, and you decide what matters.
  3. Your keys stay yoursNo WebAgent sees a password, card or wallet credential.
  4. Every action has a receiptIn plain words, and anyone can verify it.
  5. Your site and data are yoursExport everything. The platform is open source.
  6. Visitors always knowThe site says when they're talking to AI.
  7. Honest numbersWe never invent activity or results, on your site or on this page.

What comes next

From one site to a fleet on Vultr.

  1. Now

    One site, end to end

    The health report, the Move, go-live on a passkey, Ask this site, the agent door and the gauntlet, on Vultr.

  2. Next

    Payments

    PayPal through the Effects Gateway. Every payment is an approved effect with a receipt.

  3. Dec to Jan

    Pilot

    Ten pilot sites on the fleet profile on Vultr Kubernetes Engine, with the brief and approvals on WhatsApp.

  4. Q1 2027

    Version 1

    The agency console, a Vultr Marketplace listing, billing and more regions.

See what your site could do.

Rather talk to a person? WhatsApp us, 6 a.m. to 11 p.m. EAT.