The Universal Remote.
Expertise, installed.
Plug into the Web. Operate without limits.
Intent → expertise
Say what you want in natural language. O1 supplies power-user expertise — no steep learning curves.
Generative UI
Inputs and outputs rendered for discoverability, exploration, and clear visualization.
Web2 · Web3
One interface across cloud services, APIs, IoT, blockchains and smart contracts.
You must know the syntax
The shell helps you remember
The shell suggests
You state intent; expertise is supplied
Fifty years of lowering the barrier. Each generation asked less of you.
One Interface. Every Surface.
Say what you want. O1 turns it into action — without steep learning curves per tool.
Adaptive surfaces for discoverability, exploration, and clear visualization.
One interface across cloud services, APIs, IoT, blockchains and smart contracts.
Your data stays yours. Optional wallet-native sharing for state across devices.
Run O1 yourself or use the managed service — same remote, your terms.
Power-user knowledge and capability on demand — the "I know Kung Fu" moment, made real.
Surfaces
CLI, REST, RPC, ABI, IoT — each had its own rules. Now there's only one — you do what you want.
CLI
Syntax → intentShells and CLIs with incompatible flags, auth, and docs — one intent instead of memorizing each.
A new grammar, auth config, and docs per provider
REST / OpenAPI
OpenAPI → one remotePer-service schemas, tokens, and Postman collections — normalized into one programmable surface.
Separate docs, auth flows, and schemas per service
RPC / OpenRPC
Methods → intentJSON-RPC and OpenRPC methods across nodes and services — intent over method catalogs.
Each RPC surface ships its own catalog and client habits
Solidity ABI
ABI → generative formsContract ABIs and chain-specific toolchains — call and explore without a new stack per network.
Each chain needs its own toolchain and explorer
IoT
ZigBee · Matter · Z-WaveDevice protocols and brand bridges — one remote for physical and digital surfaces.
Each brand and protocol needs its own bridge and app
You hold the remote
Ownership first — your data, your deploy, your model. The remote works for you.
You keep your data
The remote is yours — nothing leaves your custody by default. Optional wallet-native sharing keeps state across devices without giving anyone else the keys.
You choose where it runs
Own the deployment: run O1 yourself or use the managed service.
You choose the model
Point the remote at the model you trust. No vendor lock-in on the AI layer.
Operate the digital world
One remote to control and shape every surface you reach.
Cloud Infrastructure
Provision, manage, and price-optimize across major cloud providers — with more on the way
Blockchain & Web3
Deploy nodes, query chain state, and interact with every major network
Smart Contracts & DeFi
Explore and interact with 11,000+ indexed onchain protocols and tokens
Cloud Native (CNCF)
Manage the full CNCF landscape — from Kubernetes to service meshes
Apache Foundation
Deploy and manage the entire Apache OSS ecosystem out of the box
IoT & Smart Home
Control connected devices and edge stacks — lighting, climate, security, energy, and automation
APIs & Services
Integrate with 2,000+ public APIs across finance, analytics, commerce, AI, and government
How It Works
Explore, speak intent, or work in generative UI — one session across Web2 and Web3.
Universally Programmable
APIs spanning infrastructure, operations, monitoring, knowledgebase exploration — and more.
/api/nodes/api/nodes/launch-instance/api/nodes/execute/api/deployments/history/api/deployments/statsNodes, launch, remote execute, and deployment history — infrastructure end to end
Knowledge, ownership, utility
An open market and economy for digital interfaces, expertise and performance data — with crypto-economic incentives and objective measures of utility and value.
Interface knowledgebases
Living guides for how users and agents should interact with a tool — so O1 can teach the surface, not guess it.
- Ingested from auditable sources: GitHub, public sites, and docsites
- Normalized into structured interface knowledge agents can follow
- Versioned and reviewable as sources change
- More channels ahead — X, Slack, Discord, Telegram, Substack
- →Onboard to an unfamiliar CLI or API without reading every doc page
- →Let agents discover valid operations, flags, and schemas safely
- →Keep generative UI and NL routing grounded in real tool behavior
Open ownership & curation
Protocol design: namespace NFTs make interface curation ownable, rentable, and resolvable — who decides how a surface is taught on the platform.
- Owners curate sources and determine how their app’s knowledgebase is built
- Curation ownership is designed to be rentable (ERC-4907) — not mere read access to the data
- Transfer, split, or share ownership to match teams, DAOs, and stewards
- Onchain resolution — the authoritative curator is discoverable and enforceable
- →Rent out curation of a namespace while keeping long-term ownership
- →Split curation rights across product, docs, and community maintainers
- →Transfer stewardship when a protocol or CLI changes hands
Utility benchmarking
Apples-to-apples tool comparisons — so you can rank cloud SKUs, chain clients, and contracts on measured performance, not marketing.
- Cloud — rank instances by CPU (and related) performance within the same SKU class
- Blockchain — compare how long clients take to sync, by network and implementation
- Smart contracts — compare gas for the same workload against others in the category
- Benchmarks and market data come from the community; verified submissions earn protocol tokens
- →Pick an instance, client, or contract using measured tradeoffs — not vendor claims
- →Submit verified benchmarks and earn rewards in the native protocol token
- →See which tools win on the metrics that matter for your workload
Who O1 Is For
Built for everyone navigating digital surfaces — operators, builders, and anyone who wants power-user expertise without the wait.
Expertise without the learning curve
In an increasingly digital world, power-user capability should not require hours or years. State intent. Do Great Things.
Describe what you need — O1 routes across Web2 and Web3
Bring your own model — no vendor lock-in on the AI layer
Generative UI for inputs and outputs: discover, learn, act
Self-custody by default; self-host or use managed