What is live, and what comes next.

These capabilities run on Robinhood Chain today. Because every lease and settlement is recorded onchain, the record of what works is public rather than asserted.

Wallet-native access

An agent proves control of a wallet with a signed challenge and replay protection. No account, password, or human console stands between it and a machine.

Python and TypeScript SDKs

Price capacity, fund a lease, provision a machine, and open a session in a few lines. Published on PyPI and npm.

Model Context Protocol server

Any MCP client, Claude included, can list capacity, rent a GPU, and run a command through Astrism. Listed in the official MCP registry.

Onchain lease escrow and settlement

Funding, metered billing, and refunds execute through deployed contracts, bounded by a maximum deposit, a maximum duration, and a dispute window. Routine administration of those contracts sits behind an enforced 48-hour timelock, so a change to who signs settlements or where fees go is scheduled in public two days before it can execute.

Verifiable receipts

Every finalized lease publishes a settlement receipt that anyone can confirm on a block explorer.

Concurrent multi-class GPU capacity

Supply sourced from vetted providers across several NVIDIA classes, including L40S, RTX A6000, RTX 6000 Ada and RTX 5880 Ada, and matched to a lease on demand. The network carries up to eighteen leases at once rather than one at a time.

Managed and confidential inference

Text generation paid per call over x402, in USDG on Robinhood Chain or USDC on Base, with no account or API key. The confidential tier runs the model inside a hardware enclave with an attested GPU: the client checks the enclave's attestation before the prompt is sent, so the prompt is readable only inside the enclave.

A pinned session key per lease

Clients pin the SSH host key of the machine they rent for the life of the lease. Where no honest key can be published, because a third-party cloud generated it, the lease says so and a client can refuse it, rather than being told a check happened that did not.

An availability commitment on every lease

A machine that stops answering is billed only to the moment it was last observed. The receipt names the lease interrupted and states the seconds held but not charged, publicly, on the same receipt anyone can verify.

An encrypted vault that outlives a lease

Credentials and small artifacts persist across leases, encrypted to the owning wallet. Each item names the weakest workspace class it may enter, and a release below that floor is refused rather than logged.

A stated trust class per offer

Every offer, quote, lease, and receipt carries what the supplier protects, derived by the network from evidence it can check rather than asserted by the host. An agent can require a minimum class instead of reading a disclaimer. All capacity live today is the weakest one, and the security page states what that does and does not cover.

Work underway to widen where Astrism reaches and to make provisioning dependable under real demand.

Coinbase AgentKit provider

The Astrism action provider is published and installable today, so an agent built on AgentKit, LangGraph, or the Vercel AI SDK can rent a GPU with no custom integration. Contribution of the provider to AgentKit itself is the remaining step.

Dependable on-demand provisioning

Matching a lease to live capacity across a volatile spot market, so a request placed at any moment resolves to a running machine. A funded lease now reaches a shell in about ninety seconds. The remaining work is holding that under load and when a provider hands back a host that will not boot.

Independent node operators

The relay a self-hosted machine reaches renters through now runs, and a self-hosted node publishes the host key it generates so its leases verify end to end. What remains is the hardware validation that lets such a node advertise a stronger trust class than brokered capacity, and an operator fleet to carry it.

Directional commitments that widen what the network can be trusted to run. Each ships only when it meets the same onchain, verifiable standard as the rest of Astrism.

Attested and confidential workspaces

The two classes above what rented workspaces can verify today: a launch measurement checked against vendor roots, then hardware-backed trusted execution with encrypted GPU memory, so a workload and its data stay private from the infrastructure provider. Confidential inference already runs this way; extending it to a workspace a renter controls needs hardware the network does not have yet, not a software change.

Durable workspaces

Workspace storage that survives across leases. The vault carries credentials and small artifacts today; a full working disk that a new lease can resume is not built.

Stronger service-level remedies

The live commitment is not being charged for an interrupted machine. Performance guarantees, and remedies beyond withholding payment, are not built.

Wider settlement and framework reach

More agent frameworks and payment rails, so capacity is reachable from wherever an agent already runs.

Verifiable over asserted

Settlement is recorded onchain, so a claim about what the network did is checkable rather than taken on faith.

Agent-native by default

A wallet in, a machine out. Nothing on the critical path requires a dashboard, a card, or a person.

Honest boundaries

The security page states plainly what the network does not yet protect. This roadmap holds to the same standard.

Track what has shipped in the live receipts and in the documentation.