Fractional AGI · US Neocloud Fabric · Energy-Backed Nodes

Agentic compute, metered by the fraction of a GPU-hour.

NODE AGI CLOUD brokers metered, fractional allocation of agentic AI capacity — GPU-hours, dedicated inference endpoints, agent seats, and secure enclave time — across vetted US-based neocloud providers today, and routes it to planned ECX energy-backed nodes as they come online. Buy the fraction you need. Govern every GPU-hour.

3PLANNED ECX NODES
8US NEOCLOUD INTEGRATION TARGETS
100%MUTATIONS DRY-RUN BY DEFAULT
115–290TARGET MW, ALL NODES
From the CEO

I have spent my career close to the point where energy becomes intelligence. The constraint in American AI is not ambition and it is not capital. It is firm power, speed-to-grid, and disciplined governance of the compute those megawatts buy. That is the gap NODE AGI CLOUD exists to close.

Fractional AGI is a simple idea with hard edges: treat agentic AI capacity as a metered resource, the way a utility treats a kilowatt-hour. Most enterprises do not need a data center. They need a reliable fraction of one — a few thousand governed GPU-hours a month, an inference endpoint that does not move, and an audit trail a board can read. We deliver that fraction through vetted US-based neoclouds now, and as our planned ECX nodes come online behind their own power, your fraction moves onto our own steel.

I will not oversell what does not yet exist. Our facilities are planned, with target capacities and published execution risks. What exists today is the brokerage, the governance layer, and the engineering discipline to make every allocation accountable to a named human being. That combination is rare, and it is the honest foundation everything else is built on.

Chief Executive Officer, Energycapitalx (ECX) Connect on LinkedIn

Book a briefing with the CEO

Why power-backed nodes matter

MW → GPU-hr

Every fraction of agentic capacity is downstream of a megawatt. ECX's planned node network is designed so that the energy position and the AI workload sit under one governance roof — the fraction you buy is backed by assets built for it, not rented around it.

Node capacities stated as targets. Owner to confirm.

The Model

What Fractional AGI actually is

A metered, fractional allocation of agentic AI capacity — brokered across vetted US neocloud providers today, and routed to ECX nodes as they come online. You allocate in fractions of a GPU-hour, not in data centers.

01 / ALLOCATE

Fractions, not fleets

Purchase exactly the GPU-hours, inference endpoints, agent seats, and secure enclave time your workload requires. Scale by the fraction as demand moves. Unallocated capacity is never your liability.

02 / BROKER

America-first fabric

Capacity is brokered across vetted, US-headquartered neocloud providers — evaluated on price per GPU-hour, availability, and governance posture — through one SDK and one audit trail.

03 / ROUTE

Home to the node

As planned ECX nodes come online, fractions migrate onto energy-backed ECX infrastructure: fiber-anchored edge at San Clemente, enterprise edge at Tustin, and the flagship Edwards campus.

Commercial Structure

Three fractions of control

Every tier is metered, governed, and human-approved. Pricing is quote on request — sized to your fraction, region, and compliance envelope.

TIER I

Fraction

Shared capacity · metered GPU-hours
Pricing: quote on request
  • Shared inference endpoints on vetted US neoclouds
  • Agent seats with per-seat metering
  • Standard governance: dry-run default, full audit trail
  • Best-effort availability windows
Request access
TIER II

Dedicated Fraction

Dedicated endpoints & GPU allocations
Pricing: quote on request
  • Dedicated inference endpoints, pinned to your allocation
  • Reserved fractional GPU-hours across providers
  • Priority placement in the ranking and routing engine
  • Named account engineer and quarterly capacity review
Book a briefing with the CEO
TIER III

Sovereign / Secure Fraction

Enclave time on planned ECX nodes
Pricing: quote on request
  • Secure enclave time with strict human approval gates
  • Routing preference to planned ECX node capacity as it comes online
  • Air-gap-oriented workflows and enhanced audit retention
  • Designed for regulated and federal-adjacent workloads
Request access
The Destination Fabric

Node network Planned

Three planned ECX facilities form the Southern California–Mojave corridor — the destination your fractions route to as capacity comes online. All capacities are targets, not commitments. No facility is online today.

FacilityLocationTarget capacityStrategic roleStatus
ECXI ZERO
energycapital.io
Calle Extremo, San Clemente, CA 5–15 MW target Telecom and fiber backhaul aggregation node; latency bridge between the LA and San Diego corridors; sub-5ms connectivity anchor. Planned
ECXI ATEP
cipherbit.io
0 Victory Loop, Tustin, CA — former MCAS Tustin zone 10–25 MW target Enterprise edge AI and IoT validation node under the Cipherbit brand; private, low-latency inference for Orange County and greater LA enterprise. Planned
ECXI IO
Edwards AFB, CA
Edwards AFB, Kern County, CA 100–250 MW target Flagship federal "AI Security Factory" and primary compute node for the planned secure-fraction tier; high-density liquid-cooled campus design. Planned

Facilities are planned; target capacities and execution timelines are subject to zoning, interconnection, and federal processes. Owner to confirm.

Today's Fabric

Neocloud integration layer

Fractions are brokered today across US-headquartered neocloud providers. The following are supported integration targets of the NODE AGI CLOUD Python SDK — listed for technical compatibility only. No partnership, resellership, or endorsement is claimed or implied.

LambdaSDK live
VultrSDK live
Together AISDK live
CrusoeVerify
CoreWeaveK8s
Voltage ParkStub
OmegaCloudStub

Provider names are trademarks of their respective owners. No affiliation or endorsement implied.

The Instrument

Python SDK with governance built in

One package brokers every provider: aggregated offers ranked by $/GPU-hour and availability, fractional allocation across providers, and an HTTP service. Mutating operations are impossible to fire by accident.

  • Broker. Aggregate offers across providers; rank by $/GPU-hr and availability; split a GPU-hour demand fractionally across the cheapest set.
  • Governance. Launch and terminate are dry-run by default and require an explicit ApprovalToken with approver name and ticket id.
  • Audit. Append-only JSONL audit log records every attempt — dry-run or live.
  • Service. FastAPI app exposing GET /api/offers, POST /api/quote, POST /api/plan — and deliberately no launch endpoint.

Download the Python SDK (.zip)

# Fractional allocation across vetted US neoclouds from nodeagi import Broker, ApprovalToken from nodeagi.base import LaunchRequest broker = Broker() # Rank every offer by $/GPU-hour and availability offers = broker.rank(broker.collect_offers(gpu_model="H100")) # Split 5,000 GPU-hours fractionally across providers plan = broker.plan_fractional( demand_gpu_hours=5_000, max_providers=3, max_price_per_gpu_hr=2.75, ) for slice_ in plan.slices: print(slice_.provider, slice_.gpu_hours, slice_.est_cost) # Mutations: dry-run by default req = LaunchRequest(provider="lambda", instance_type="gpu_8x_h100", region="us-west-2", quantity=2) result = broker.launch(req) # dry-run, audited assert result.dry_run is True # Live launch: named human + ticket, or it refuses token = ApprovalToken(approver="A. Approver", ticket_id="ECX-042") result = broker.launch(req, dry_run=False, approval=token)
Non-Negotiable

Security and governance

Autonomous infrastructure change is not a feature we ship. Every mutating action in the NODE AGI CLOUD stack passes three gates before a single watt of capacity moves.

Gate 1

Human approval

Live execution requires an explicit ApprovalToken carrying a named approver and a ticket id. No token, no launch — enforced in code, not in policy documents.

Gate 2

Dry-run default

Every launch and terminate call is a dry-run unless an operator deliberately sets dry-run false and supplies a valid token. The safe path is the default path.

Gate 3

No autonomous changes

The HTTP service exposes read-only endpoints only — offers, quote, plan. There is no launch endpoint. The system cannot block, delete, quarantine, or reconfigure anything on its own.

Engage

Request access

Tell us about your fraction. We respond with a scoping call and a quote — on request, never invented.

Request saved locally. This portal is a proposal draft; the form does not transmit data. Your request is held locally in this page session only. To reach us directly, book a briefing with the CEO.

This form is front-end only. No data leaves your browser. Proposal draft — not an offer. Owner to confirm.