# Terawatt Infrastructure

> Terawatt Infrastructure acquires, develops, owns and operates purpose-built
> electric-vehicle charging centers for commercial fleets across the United States —
> medium- and heavy-duty trucking, drayage, autonomous vehicle and rideshare operators.
> It sells charging-as-a-service, not software.

<!--
generated: 2026-08-30
method: generated
source: >-
  GENERATED by API Evangelist from this repo's apis.yml and probe artifacts. Terawatt
  Infrastructure publishes no llms.txt of its own — https://www.terawattinfrastructure.com/llms.txt
  returned 404 on 2026-08-30. Every URL below was fetched and returned HTTP 200 unless
  marked otherwise. Nothing here is authored on Terawatt's behalf beyond linking pages
  it publishes.
-->

## What Terawatt is, for an agent

Terawatt is an infrastructure owner-operator, not an API provider. Its assets are real
estate, grid interconnection and high-power charging hardware, run with proprietary
Charge Management Software and an operations and maintenance program. Notable sites
include the I-10 electrified corridor and locations serving the Ports of Los Angeles and
Long Beach.

## Developer / API surface

**There is none that is publicly reachable.** As of 2026-08-30:

- No developer portal, API reference, or SDK. `/developers`, `/docs`, `/api` all 404.
- No machine-readable contract. No OpenAPI, AsyncAPI, GraphQL SDL, Postman collection
  or JSON Schema at any discoverable location.
- No `.well-known` documents at all — security.txt, api-catalog, OAuth/OIDC metadata,
  agent card and ai-plugin manifest all 404.
- No MCP server and no A2A agent card.
- No API host in DNS. `api.`, `app.`, `developer.`, `docs.`, `portal.`, `ocpi.` and six
  other candidate subdomains of `terawattinfrastructure.com` are all NXDOMAIN.
- No public GitHub organization; no packages on npm, PyPI or any other registry.

**One integration surface exists but is customer-only.** Terawatt states in its own
engineering blog that it has "implemented Open Charge Point Interface (OCPI) with custom
extensions, which gives our customers visibility into our charging facility." OCPI is the
e-mobility roaming standard. No OCPI version-discovery endpoint answers anonymously
(`/ocpi/versions` → 404), no OCPI version or module list is published, and the custom
extensions are undocumented. A fleet operator gets this surface through a commercial
agreement, not through a signup.

Terawatt also runs a customer reservations portal (pre-booking charging sessions up to a
year ahead, with dynamic stall reassignment) and delivers charge-session data with per-kWh
billing through customer dashboards. Neither is exposed as a public API.

## Pricing

No published pricing. No plan tiers, no rate card. The commercial motion is a contact form
leading to a negotiated charging-as-a-service or site agreement. Billing is per kWh; the
rate is not public.

## Public pages

- [Home](https://www.terawattinfrastructure.com/)
- [About](https://www.terawattinfrastructure.com/about)
- [Solutions](https://www.terawattinfrastructure.com/solutions)
- [Trucking fleets](https://www.terawattinfrastructure.com/solutions/trucking-fleets)
- [Autonomous and rideshare fleets](https://www.terawattinfrastructure.com/solutions/autonomous-and-rideshare-fleets)
- [Blog](https://www.terawattinfrastructure.com/blog)
- [News](https://www.terawattinfrastructure.com/news)
- [Contact](https://www.terawattinfrastructure.com/contact)
- [Privacy policy](https://www.terawattinfrastructure.com/privacy-policy)
- [Code of conduct](https://www.terawattinfrastructure.com/legal/code-of-conduct)
- [Purchase order terms and conditions](https://www.terawattinfrastructure.com/legal/potc)
- [Sitemap](https://www.terawattinfrastructure.com/sitemap.xml) — 90 URLs, none of them developer-facing

## Background reading Terawatt publishes

- [How Terawatt's full-stack platform delivers reliable EV/AV fleet charging](https://www.terawattinfrastructure.com/blog/how-terawatts-full-stack-platform-delivers-reliable-ev-av-fleet-charging) — the OCPI statement lives here
- [What is charging-as-a-service (CaaS)?](https://www.terawattinfrastructure.com/blog/what-is-charging-as-a-service-caas-and-how-can-it-add-value-to-your-growing-ev-fleet)
- [EV charging reliability: what is it and how is it measured](https://www.terawattinfrastructure.com/blog/ev-charging-reliability-what-is-it-and-how-is-it-measured)
- [Unlocking the grid: a blueprint for fleet-scale EV charging](https://www.terawattinfrastructure.com/blog/unlocking-the-grid-a-blueprint-for-fleet-scale-ev-charging)

## Domain security posture (probed 2026-08-30)

TLS 1.3, HSTS with a one-year max-age, SPF present, DMARC at `p=reject`. No DNSSEC and no
CAA records. Full detail in `security/terawatt-infrastructure-domain-security.yml`.