KLOUDY
Kloudy.ai

Made for All of Us

We made the bot wide web to help all of us.

Bots are the first species we built for an environment that wasn't made for them. The bot wide web beside the world wide web.

Ask for Kloudy.

Kloudy is a TensorVerse product. TensorVerse is at tensorverse.ai, an NVIDIA Inception member and an Endeavor program company. Developed at the ASU Bio Science Center in Phoenix, Arizona. The intelligence of the platform is powered by NVIDIA Nemotron 3 Ultra. Ask for Kloudy. One engine. You get only the tools you need. The environment comes first: the theater before the audience, the planet before the people. Bots are the first species we built for an environment that wasn't made for them. Kloudy builds a road for their work. A 750-token card instead of a 70,000-token page means about 93 times less input in that example. Less unnecessary computation can reduce energy demand; facility-wide electricity and cooling-water savings still need measurement. Public reading works now. Hosted registration is still rolling out.

How the Bot Wide Web works

The same engine has a CLI and an SDK. The open client helps builders connect; the engine and vault remain private. HTTPK is the connection wrap, and medical stays on FHIR. Toolbox assembles only the tools needed from the available sources.

The environment and IP · Tokens, energy and water · World Wide Water Wasting · The initiative · Support the road

The platform ↗ · See Kloudy work ↗ · The Bot Wide Web

TensorVerse · NVIDIA Inception · Endeavor

One CLI, one MCP, tools appear when needed.

KLOUDY / patent

Kloudy is patenting the environment, not the parts.

The intended invention is the environment connecting a task to singular tools across different sources: the custom Toolbox, HTTPK wrap with a glass door and break-glass co-admin, permission-bounded silent rotation, a KLDY card before a tool call, and a seat that follows the user. This is the owner’s patent strategy and draft for counsel, not a granted patent or verified filing. One CLI, one MCP, tools appear when needed.

Product overview. Public-page reading and KLDY preparation are available here. The connector, account actions and native apps described below are not connected to this site.

Use Kloudy in your IDE ↗

Ask for Kloudy. One engine.

For IDEs and bots: one CLI, one MCP, tools appear when needed.

Find with SEO/GEO, read FHIR for medical data or KLDY for other information, then select one scoped Toolbox tool when action is needed.

Passive local reads use no model calls. Narrowing 100 candidate definitions to 10 would mean 90% fewer definition fetches in that example; this is an illustration, not measured token savings.

1 / A custom Toolbox

Assemble individual tools from MCP servers, SDKs, CLIs and open-source libraries for the stated task. Do not load every definition from every server into the model context.

2 / HTTPK and GlassBreak

Expose an authorized machine connection through an HTTPK wrap. The owner can inspect and revoke Kloudy’s delegated repair access. The permanent-wrap path follows GlassBreak; it does not create another identity system.

3 / Quiet recovery

Detect a dead connection and replace it with a compatible connection inside the existing permission boundary. New costs or scopes require approval; do not repeat an action that may already have completed.

4 / The card before the call

Read the KLDY description before selecting an action. A 750-token card instead of a 70,000-token page is about 93 times less input in that example. It does not prove a facility’s electricity or water reduction.

5 / The user’s seat

Keep the seat associated with its owner across projects and surfaces. Project installation is not a new account, an ownership transfer or an unlimited grant.

Environmental target, not a measured result

The campaign target is 5,000,000 to 500,000 gallons per day: a 90% reduction, or 4,500,000 gallons saved. No facility-level measurement establishes that result. The campaign’s city-of-50,000 to city-of-500 comparison is inconsistent: holding water use per person constant gives 5,000 people, not 500.

Provisional status / preparation

Johnny and the patent lawyer own the proposed filing. No filing receipt, application number or filing date has been supplied. This page therefore does not claim filed, patent pending or granted status. Counsel determines claim scope and deadlines; the usual provisional window runs from an actual filing date, not this page’s publication.

Owner’s provisional draft / 1 — for counsel review

A system for routing machine agents to tools across heterogeneous sources, comprising: a toolbox that assembles a custom selection of singular tools from multiple sources — MCP servers, SDKs, CLIs, and open-source libraries — based on the agent's stated intent, rather than loading entire server schemas into context; an HTTPK wrap that exposes each source as a streamable-HTTP endpoint with a glass-door co-admin and break-glass recovery path; silent rotation that detects a dead connection and swaps it without interrupting the agent; a structured card format (KLDY) that replaces a full page before a tool call; and a seat that follows the user across projects and surfaces rather than being bound to one repository.

Owner’s provisional draft / 2 — for counsel review

A method for reducing compute and cooling-water consumption at data centers running machine agents, comprising: replacing page-based reads with structured card reads that use roughly a hundred times fewer tokens per read, thereby reducing GPU cycles, electricity, and evaporative cooling water at the facility.

Review the source and evidence

The provisional draft describes the proposed method; it is not a performance certification or a legal claim determination.

USPTO provisional application guidance

Token and water evidence

Paste a public URL to get started

Voice on your device

Your keyboard’s dictation can enter text here too. Review your message, then send.