Economic agency
Give every machine a durable, owner-controlled identity for participating in work and value flows.
Runtime 8 · Application layer for autonomous machines
Infrastructure for the machine economy.
A production application layer where robots, drones, sensors, and edge hardware can establish identity, coordinate work, request resources, settle value, and leave verifiable records.
Non-custodial signingOwner-scoped operationsSolana settlement
RUNTIME
IdentityWallet owned
ResourcesProvider matched
SettlementUser signed
TelemetryMachine sourced
● APPLICATION CONTROL PLANE
The coordination gap
Machines are ready to do more than execute commands.
Autonomous hardware increasingly chooses tasks, consumes services, and produces value. It needs economic infrastructure designed for identities that are neither people nor traditional servers.
Resource exchange
Coordinate access to compute, inference, data, charging, connectivity, and specialized services.
Operational evidence
Connect jobs and telemetry to receipts so operators can inspect what happened and when.
Programmatic settlement
Move from approved work to user-reviewed, non-custodial payment and explicit confirmation states.
Machine Console
One control plane for the runtime.
Connect an operator wallet to inspect owned machines, open runtime sessions, coordinate jobs and resources, watch telemetry, and complete settlements.
- Machine registry Owner scoped
- Resource marketplace Persistent
- Telemetry delivery Event driven
- Settlement lifecycle Explicit states
Runtime 8 / Console previewv0.9.4
Operator workspace
● CONNECTEDNetwork overview
MachinesOWNER SCOPEIdentity verified
TelemetryEVENT FLOWFreshness derived
SettlementUSER SIGNEDConfirmation tracked
Runtime moduleSourceState
Machine telemetryCredentialAUTHORIZED
Resource requestWalletPERSISTED
Settlement receiptChainVERIFIED
Illustrative interface preview · the Console displays authenticated production records
Runtime loop
From machine action to durable proof.
The application joins runtime primitives and resource coordination into a clear operational lifecycle.
Machine action
Hardware performs work and submits an authenticated runtime event.
Runtime & policy
Identity, capability, ownership, and operating context are evaluated.
Resource request
The application discovers compatible provider capabilities and persists a request.
Settlement
A trusted transaction is prepared, reviewed, signed, submitted, and confirmed.
Receipt & proof
Outcome references and settlement evidence become an auditable record.
Runtime stack
Eight application modules. One operating layer.
Runtime 8 combines public runtime interfaces with production application services for authentication, persistence, marketplace coordination, and live operations.
Machine identity
Wallet-owned machine records, roles, capabilities, and revocable machine credentials.
Runtime sessions
Durable machine session records mapped to the runtime-8 session model.
Policy boundary
Capability and ownership gates before machine and settlement operations proceed.
Resource layer
Provider discovery, requests, quotes, grants, consumption records, and receipts.
Telemetry
Credential-authenticated ingestion, retention, freshness, and live Console delivery.
Jobs
Work-order lifecycle connected to owned machines and required capabilities.
Settlement
Non-custodial transaction preparation with separate signing and confirmation states.
Receipts & proof
Evidence references and chain receipts linked back to authorized resource activity.
Resource economy
Machines can acquire what the next task requires.
The Resource Layer turns provider capabilities into an authorization-aware service lifecycle—from discovery and quoting through access, execution, settlement, and evidence.
ComputeInferenceWeatherChargingNavigationSensor data
01MachineAuthenticated identity
02Resource requestNeed + constraints
03Provider discoveryCompatible capabilities
04Quote and accessExplicit grant
05Runtime consumptionMachine activity
06SettlementWallet reviewed
07Resource receiptRecorded evidence
Built for physical systems
Infrastructure for machines that work in the world.
Autonomous robot fleets
Coordinate warehouse and logistics machines across work orders, service access, runtime evidence, and settlement.
Drone operations
Let mission systems acquire weather, navigation, compute, and charging resources with a traceable lifecycle.
DePIN hardware
Give sensors and edge nodes a common application layer for providing or consuming resources.
Physical AI agents
Connect autonomous decisions to policy boundaries, external services, economic activity, and inspectable proof.
Runtime to economy
Hardware becomes a network participant in four steps.
A shared identity and state model lets isolated machines coordinate resources and form permissioned markets.
Machine identity
An owner links hardware to a durable runtime identity and operating role.
Machine state
Sessions, jobs, and telemetry make current operating context inspectable.
Machine resources
Providers and requesters exchange authorized service access.
Machine markets
Settlement and receipts allow repeatable economic coordination at network scale.
Developer runtime
Inspect the primitives. Build the application.
The public TypeScript package exposes runtime interfaces for wallet-linked machine sessions, work lifecycle, telemetry normalization, unsigned intents, and receipt verification.
Quick start@machinefi/runtime · v0.9.4
# Install the runtime SDK $ npm install @machinefi/runtime # Inspect deterministic fixture status $ npx machinefi status --chain solana --fixture # Explore authenticated application routes $ open /console
Operator control plane
Put autonomous machines into motion.
Connect a Solana wallet, register a machine, and coordinate its runtime from a production-backed Console.