Market Evolution
& Value Capture
How value emerges as the agentic internet scales — and where Inapse sits within that. An analytical framework for understanding the structural opportunity, without speculative projections.
/The Rise of AI-Native Users
A new class of users interacting through intent, not interfaces.
/Behavioral Shift
Users learn interfaces, navigate menus, and manually execute each step. The burden of execution sits with the human.
Users express intent. Agents interpret, plan, and execute autonomously. The interface becomes invisible.
Inapse users are AI-native by default.
/Category Growth
Three converging forces are compressing the timeline for agentic adoption. None of these are speculative — each is already in motion.
Consumer and enterprise AI usage has crossed the early-adopter threshold. The infrastructure question is no longer "if" but "how fast".
Frameworks like OpenClaw demonstrate that users want agents to act on their behalf — not just answer questions. Demand precedes infrastructure.
Repetitive digital tasks — payments, bookings, data retrieval — are the first candidates for agent execution. The use cases are concrete and immediate.
This shift is already underway.
/Scenario Modeling
Rather than projecting specific numbers, the following scenarios model how the execution layer becomes progressively more critical as agentic adoption scales.
- —Early adoption of AI workflows in select verticals
- —Execution limited to low-risk, high-frequency tasks
- —Inapse operates as a niche infrastructure layer
- —Value capture is real but contained
- —Agents become common in messaging and productivity tools
- —Regular execution of tasks across financial and digital services
- —Inapse becomes a standard integration for agent platforms
- —Execution layer captures meaningful transaction volume
- —Agents become the default interface for digital interaction
- —Execution layer becomes critical infrastructure — like DNS or SWIFT
- —Inapse sits at every agent-to-system handoff
- —Value capture is structural, not transactional
/Value Capture Layer
In technology stacks, value does not distribute evenly across layers. It concentrates at the layer that is hardest to replace and most critical to the flow of value.
| Layer | Function | Value Accumulation | Replaceability |
|---|---|---|---|
| Interface | User-facing UI / chat | Low — commoditising fast | High |
| Intelligence | LLM reasoning & planning | Moderate — competitive | Moderate |
| Execution← Inapse | Secure action on real systems | High — structural bottleneck | Low |
| Protocol | Standards & interoperability | Very high — network effects | Very low |
Inapse positions itself as the execution layer bridging AI, APIs, and financial systems — the layer where intent becomes irreversible action, and where the cost of switching is highest.
/OpenClaw Connection
OpenClaw demonstrated real, measurable demand for agent-mediated interaction. Users adopted it not as a novelty but as a functional tool for getting things done.
That demand is the signal. The gap it exposed is the opportunity.
OpenClaw operates at the intelligence and interface layers. It can interpret intent and plan actions — but it cannot execute them securely against real systems.
There is no secure execution layer. That is precisely what Inapse provides.
As agent ecosystems scale, execution becomes the bottleneck — and the value layer.
"Investing in Inapse is not a bet on user growth alone —
it is a bet on owning the layer through which AI-native users execute value."
/How Infrastructure Gets Valued
From early architecture to category ownership.
/Valuation Progression
Infrastructure companies follow a recognisable trajectory. The table below reflects how the market has historically valued companies at each stage of development — not a prediction, but a reference frame.
| Stage | Description | Typical Range |
|---|---|---|
| Concept | Idea / early build | $5M – $10M |
| Architecture Built← Inapse | Core tech solved | $15M – $30M |
| Early Traction | Usage emerging | $50M – $150M |
| Infrastructure Breakout | Category forming | $500M – $2B+ |
| Protocol Layer | Network dominance | $5B – $50B+ |
Inapse is currently positioned at the "Architecture Built" stage — where the core technical challenges have already been solved.
The infrastructure exists. The question is not whether the execution layer can be built — it is whether Inapse captures the category as adoption scales.
/Comparable Trajectories
The following companies are not direct comparables — they operate in different markets. They are referenced to illustrate how infrastructure and execution layers have historically captured value as their categories scaled.
Stripe built the execution layer for internet commerce — not a payments app, but the infrastructure that payments apps are built on. As the category scaled, Stripe's value accrued disproportionately because switching costs at the execution layer are structural.
Inapse occupies the same structural position for AI-native execution.
Twilio turned communications infrastructure into a programmable API layer. Its value was not in the messages sent, but in being the indispensable bridge between applications and real-world systems. Developer adoption created network effects that compounded over time.
Inapse bridges AI agents and real-world digital systems through a similar API-first model.
OpenAI's valuation trajectory reflects the market's recognition that the intelligence layer is foundational. Early investors priced in the structural importance of the layer — not current revenue — because the category was clearly forming.
Inapse is priced at the architecture stage, before category formation is complete.
Ethereum's value accrued not from a single application but from being the execution environment for an entire ecosystem. Protocol layers that become standards capture value through network effects that are nearly impossible to displace once established.
Inapse's QRC20 protocol positions it for similar network-effect dynamics at the agent execution layer.
/Layer-Based Value Capture
| Layer | Role | Value Capture | Switching Cost |
|---|---|---|---|
| Interface | Apps & UX | Low | Low |
| Intelligence | AI reasoning | High | Moderate |
| Execution | Inapse | Very High | High |
| Protocol | Standards | Extreme | Very High |
Companies that control execution and infrastructure layers tend to capture disproportionate value compared to interface-level products.
This is not a new pattern. It has played out across payments (Stripe), communications (Twilio), cloud (AWS), and financial clearing (SWIFT). The execution layer is where the value concentrates — because it is where the action is irreversible, and where the cost of switching is highest.
/Current Positioning
At its current valuation, Inapse is priced as an early-stage infrastructure layer — not as a fully realized network.
The architecture is built. The protocol is defined. The use cases are validated through OpenClaw. What has not yet been priced in is category formation — the point at which the execution layer becomes the default path for agent-to-system interaction at scale.
"This is not about predicting valuation —
it is about understanding how value accrues if this layer becomes essential."
/Where Value Becomes Revenue
Inapse monetizes execution — not attention.
/Core Concept
Advertising, subscriptions, and engagement loops. Revenue is tied to how long users stay — not what they accomplish.
Revenue is tied to completed actions — payments, bookings, data operations, API calls. Value is created when something gets done.
When an action is executed, value is created — and that is where Inapse captures revenue.
/Revenue Streams
A small fee captured per completed intent. The model is transactional — Inapse earns when an action is successfully executed, not when a user simply interacts.
→ Scales directly with execution volume.
Value captured when Inapse routes execution across third-party services — payments processors, data providers, booking systems. The routing layer creates a natural toll position.
→ Scales with the breadth of integrations.
Shareable, composable execution flows built on the QRC20 protocol. Creators and enterprises can publish pipelines; Inapse captures value from pipeline usage and composition.
→ Network effects compound over time.
Premium infrastructure access for enterprise deployments — custom execution environments, priority routing, dedicated pipeline capacity, and SLA-backed integrations.
→ High-margin, recurring revenue layer.
/Why This Scales
The keyboard is the most-used interface in computing. Inapse sits at the input layer — every interaction is a potential execution event.
As AI workflows automate repetitive tasks, the number of execution events per user increases. More automation means more executions, not fewer.
Unlike attention-based models where engagement is the proxy for value, every execution event in Inapse represents a real-world action with measurable economic weight.
Revenue scales with execution, not just user growth.
/Value Flow Model
Even a modest take rate becomes meaningful when applied to high-frequency, high-volume execution events. The model does not require a large percentage — it requires ubiquity.
As agents automate more actions on behalf of users, the number of intents executed per user increases. Revenue grows not just with user acquisition, but with depth of automation per user.
"Inapse does not need to maximize revenue per user —
it benefits from being embedded in every executed action."