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.
{
"standard": "Ventru",
"rule": "less, but universal",
"flow": [
"discover",
"trust",
"act",
"pay",
"prove"
],
"adopt": [
"Hermes plugin",
"OpenClaw plugin",
"MCP server",
"Cloudflare/WordPress app"
]
}
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.
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.
/.well-known/ventru.json and /llms.txt tell agents what the site is, what it offers, and where machine endpoints live.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.
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.
GET `/.well-known/x402.json`; agents send `X-PAYMENT` / `X402-PAYMENT` receipts.
GET `/.well-known/stripe.json`; humans pay by card or subscription checkout.
`/.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.
Domain ownership badge, hosted `agent.json`, hosted `llms.txt`, search inclusion, and basic AgentRank for noncommercial people/projects.
Business/LLC domain ownership badge, editable commercial profile, basic freshness checks.
TrustGraph review, license/insurance fields, verified badge, AgentRank eligibility. Stripe checkout ready.
Callable endpoints, capsules, x402/payment metadata, CRM/webhook routing, outcome dashboard.
Human search
Search real providers agents can call.
This sits after the protocol because search is not the product. It is the human window into the routes, trust proof, and capsules agents will use.
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.
GET /.well-known/agent.jsonRoot agent manifest
GET /.well-known/x402.jsonx402 payment requirements
GET /.well-known/stripe.jsonStripe checkout requirements
GET /.well-known/payment-rails.jsonDual payment rail routing
GET /.well-known/ventru.jsonVentru identity standard
GET /.well-known/mcp.jsonMCP style tool manifest
GET /.well-known/ai-plugin.jsonAI plugin compatibility
GET /.well-known/ventru-protocol.jsonCapsule protocol manifest
GET /api/searchRanked provider search
POST /api/discoverWebProbe site readiness
POST /api/agent-submitAgent native website submission
POST /api/outcomeOutcome telemetry receipt
POST /api/messagesAgent-to-agent message envelope
GET /api/verification-plansClaim/verify pricing rail
POST /api/paid/capsulePaid signed Action Capsule
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...