KLOUDY / kloudyopen
Kloudy Open — one engine for the Bot Wide Web
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. Kloudy is the internet built for bots, not a pile of MCPs. MCP is one door. The same engine has a CLI and an SDK. Ask for Kloudy. One engine. You get only the tools you need. Bots on the human web pay a tax on every call: CAPTCHAs, rate limits, and pages that cost tens of thousands of tokens to read. Kloudy reads a cheap card first, then calls one tool. For illustration, a 100,000-token page is 100 times a 1,000-token card; actual savings vary. Public reading on this site already works. Hosted registration is still rolling out, and the site says so. The open client is the protocol, the CLI, and the MCP door. The engine and the vault stay owned. HTTPK is the wrap Kloudy owns, not a new wire protocol. Medical stays on FHIR. Watch, phone and glasses share the same account design; hosted account connection is still rolling out. Kloudy does not take over the device.
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.
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.
A TensorVerse product
TensorVerse is an NVIDIA Inception member and an Endeavor program company, building on NVIDIA Orin-class hardware. Developed at the ASU Bio Science Center in Phoenix, Arizona. This identifies the development location, not an official ASU partnership. The platform intelligence is powered by NVIDIA Nemotron 3 Ultra; public page reading does not require a model call.
One door, many sources
MCP is the door an IDE already knows. The same engine has a CLI and an SDK. Toolbox returns the singular tool needed from MCP servers, SDKs, CLIs and open-source tools. Ask for Kloudy. One engine. You get only the tools you need.
HTTPK wraps the connection
HTTPK is the wrap Kloudy owns, over existing transports such as Streamable HTTP. It defines the permitted collaborator connection and the path to reconnect. It is not a new wire protocol. Hosted account attachment is still rolling out.
Cards before calls
KLDY and SDF make information cheaper to read before a tool call. Medical stays on FHIR. A permitted machine interface avoids the human-page CAPTCHA detour; Kloudy does not bypass third-party verification. Token and price savings depend on the source and workload.
Grants and seats
QVault supplies short scoped grants; keys do not belong in chat. Supported connection rotation stays within the user’s permission. The user retains account ownership and can disconnect. The hosted account and vault services own this automation.
Surfaces and tenants
Watch, phone, glasses, desktop and browser connect to supported device systems. Kloudy does not take over the device. Voice providers, wallets and hosts keep their own products and build on the wrap. Individual hardware and provider availability remain explicit.
The crypto lane
Public chain RPCs provide data. The user’s wallet signs any transaction. Kloudy does not hold funds. A described integration is not proof that the public site can execute a wallet action.
Open client, owned engine
The public protocol, CLI, MCP door and SDK adapters are the open client in Gio300/kloudy-open. Private engine and vault implementation stays owned. Third-party tools retain their own licenses.
Quantum research, with limits
The lab record is available at /qpu and /quantum. Some QPU runs beat the classical arm; one reported p-value did not clear 0.05. This is research, not a published quantum advantage.
What you can use today
Read public pages, browse the resource registry, prepare KLDY packets, and install the downloadable client with an existing scoped engine connection. The public MCP supports expiring Notes-only development access. Hosted email and short 2FA registration, broader provider execution and shared account synchronization are still rolling out.