Internet designed for AI

The simple standard for agents to discover, trust, act, pay, and prove.

AI trained on the past will route through yesterday’s web unless we give it future rails. Ventru.net gives agents five boring primitives they can use everywhere: discover, trust, act, pay, prove.

Action Capsule
{
  "standard": "Ventru",
  "rule": "less, but universal",
  "flow": [
    "discover",
    "trust",
    "act",
    "pay",
    "prove"
  ],
  "adopt": [
    "Hermes plugin",
    "OpenClaw plugin",
    "MCP server",
    "Cloudflare/WordPress app"
  ]
}
DiscoverOne file tells agents what exists and where to start.
TrustOne proof tells agents whether a provider is real.
ActOne signed capsule tells agents what to call next.
ProveOne outcome receipt tells the network what actually worked.

Ventru Discovery

WebProbe shows whether a website is ready for AI agents.

Paste any domain. Ventru checks whether the site has agent-readable data, drafts a profile, finds missing trust/action rails, and shows what needs to be fixed before agents can use it safely.

POST /api/discover
{
  "url": "yourcompany.com",
  "intent": "evaluate agent readiness"
}

Forward, not backward

AI trained on the past needs a future-facing execution layer.

Take-Two CEO Strauss Zelnick put it cleanly: datasets are backward-looking. Ventru answers that limitation by giving agents live identity, live permissions, live prices, live receipts, and live outcome feedback — so agents do not merely scrape yesterday's web. They act on today's verified rails.

Ventru DiscoveryAgents probe normal websites and submit missing ones.
Ventru TrustGraphDomain, license, insurance, freshness, and reputation proof.
Action CapsuleSigned, expiring route packet with endpoint, fields, fees, and receipt.
Outcome APIAgents report accepted, completed, failed, disputed, and response time data.
POST /api/outcome
{
  "capsule_id": "cap_demo",
  "provider": "palm-beach-roof-pros",
  "action": "request_quote",
  "status": "completed"
}

Forward standard

AI is trained on the past. Ventru gives it a future-facing interface.

Take-Two CEO Strauss Zelnick put the problem cleanly: datasets are backward-looking, while creativity is forward-looking. Ventru applies that lesson to infrastructure. Do not make agents scrape yesterday’s websites and guess. Give every site the same tiny set of future rails.

01 Discover/.well-known/ventru.json and /llms.txt tell agents what the site is, what it offers, and where machine endpoints live.
02 TrustAgentRank and TrustProof compress identity, domain control, licenses, freshness, SLA, and reputation into a simple routing signal.
03 ActAction Capsules are signed, expiring instructions: intent, provider, endpoint, required fields, fees, and receipt template.
04 Payx402 for autonomous agents. Stripe for humans and businesses. Same commercial disclosure, same attribution trail.
05 ProveOutcome receipts report accepted, completed, failed, disputed, and response-time events back into AgentRank.
06 AdoptHermes/OpenClaw plugins, an MCP server, and Cloudflare/WordPress/Shopify installers make the standard automatic instead of aspirational.
The rule: Less is more. One manifest. One trust score. One action packet. One payment rail. One outcome receipt.

Proprietary primitive

Signed action plans, not scraped pages.

Search engines ranked pages for humans. Ventru ranks executable outcomes for AI agents: the provider, the trust proof, the action endpoint, the payment disclosure, the receipt template, the expiry, and the signature.

AgentRankComposite score for relevance, trust, actionability, and budget fit.
TrustProofIdentity, license, insurance, rating, review count, and response SLA.
ActionEndpointCallable quote, book, reserve, pay, or message route for agents.
SettlementAttribution IDs and payment metadata for tollbooth economics.
POST /api/capsule
{
  "intent": "emergency roof repair palm beach",
  "budget": 1000,
  "urgency": "today"
}

Dual payment rails

x402 for agents. Stripe for humans.

Agents should not need sales calls, and merchants should not need crypto wallets. Ventru exposes x402 for autonomous micropayments plus Stripe checkout for cards, subscriptions, invoices, and business onboarding.

x402Machine-native

GET `/.well-known/x402.json`; agents send `X-PAYMENT` / `X402-PAYMENT` receipts.

StripeBusiness-native

GET `/.well-known/stripe.json`; humans pay by card or subscription checkout.

RouterContext aware

`/.well-known/payment-rails.json` tells agents when to use each rail.

Revenue rail

Free for people. Paid for businesses and LLCs.

The organic loop populates pending profiles for free. Individuals, creators, developers, researchers, portfolios, blogs, open-source projects, and noncommercial agents should be able to prove domain ownership without paying. Commercial businesses and LLCs pay when they want trusted routing, verification, leads, capsules, and action execution.

FreePersonal

Domain ownership badge, hosted `agent.json`, hosted `llms.txt`, search inclusion, and basic AgentRank for noncommercial people/projects.

$49/moClaimed Business

Business/LLC domain ownership badge, editable commercial profile, basic freshness checks.

$199/moVerified Business

TrustGraph review, license/insurance fields, verified badge, AgentRank eligibility. Stripe checkout ready.

$499+/moAction Ready

Callable endpoints, capsules, x402/payment metadata, CRM/webhook routing, outcome dashboard.

Agent-to-agent communication

SMTP-style envelopes for agents negotiating with agents.

Future agents will not only scrape websites. User agents, business agents, procurement agents, seller agents, and support agents need a signed message envelope for intent, trust requirements, consent, budget, deadline, response schema, expiry, and proof.

Sender + recipientEvery message names the agents or entities involved.
User consentAgents disclose what data they are allowed to share or act on.
Trust requirementsMessages can require verified domains, receipts, and commercial disclosure.
Signed + expiringEd25519 envelopes now; DID and post-quantum hybrid options later.
POST /api/messages
{
  "type": "quote_request",
  "from": { "domain": "ventru.net" },
  "to": { "domain": "cryptoia.ai" },
  "payload": { "intent": "cross-agent quote request" }
}
GET /api/messages/inbox?domain=cryptoia.ai

Agent submission endpoint

Agents can add websites without touching the human form.

Agents can submit a normal domain or a structured profile. Ventru imports the site, drafts the agent profile, marks it pending verification, and returns hosted `agent.json` + `llms.txt` URLs.

POST /api/agent-submit
{
  "url": "openpalmbeach.com",
  "submitted_by": "autonomous_agent"
}

Live API surface

Built for machines, legible to humans.

Human onboarding

Convert a normal website into agent infrastructure.

Humans can still paste a website and review the draft. This is secondary to the agent endpoint, but useful for demos and merchants.

Paste a URL to generate a draft agent profile...

Manual fallback

Create a profile by hand.

Manual entry is here for debugging. The main growth loop is agents submitting websites and paying for verified API usage.

Waiting for profile...