The web was built on an assumption that’s quietly aging out: a person sits in front of a screen and reads pixels. Most of our infrastructure — auth, payments, content delivery, analytics — is shaped by that assumption.
That person is increasingly delegating. Not for novelty — for time. They ask an agent to enroll them in a course, find a flight, summarize a textbook, schedule a tutor. The agent dispatches to other agents, which call tools, which return results. The human is the principal; the program is the actor.
The web that handles this well isn’t the one we have. It’s structured, addressable, and consent-aware — and that’s what we’re building three companies to deliver.
01 — Content needs to be addressable, not scraped
When an agent helps a learner, it doesn’t want to render a page; it wants the lesson, the transcript, the quiz answers, the certificate state. Scraping is fragile and uncomposable. The fix is a shared protocol — Anthropic’s MCP being the leading candidate — that lets every content surface expose its capabilities.
Loopwise bakes MCP and OAuth into every school. Agents enroll, fetch, and record progress on a learner’s behalf, with explicit, scoped, revocable consent.
02 — Commerce needs to clear for non-human buyers
Stripe assumed a human with a card in a jurisdiction. Agents complicate every part of that sentence. Whose tax residency applies? Did the principal authorize this purchase? Is the transaction within scope?
Loopix answers them as the merchant of record. We collect, remit, and own the legal relationship — so the agent and the creator can focus on outcomes, not jurisdictions.
03 — Infrastructure needs to start in milliseconds
Long-running VMs are the wrong unit when an agent might fan out to a hundred services for a single request. Edge runtimes — V8 isolates, WASM, sub-50ms cold starts — are the right unit. And operators need to inspect and self-host the substrate, because policy and latency vary.
Sol Creek is that runtime — open-source and Apache-2.0, deploying full-stack apps to Cloudflare Workers in seconds, or self-hosted when policy demands it.
What we’re not
We’re not building an agent. The world has plenty. We’re building the surfaces agents need to do their job on someone’s behalf: content, commerce, compute. Each is independently useful. Together they form a stack.
How we operate
Kaik, Inc. is the operating company. The three brands ship under their own names because their audiences don’t overlap — a course creator, a developer, and a marketplace operator are three different people. Internally we share engineers, billing, and a thesis. Externally we ship three things, deliberately.
— S. Chen & J. Park, May 2026