# Prometheus Fuels > Prometheus Fuels is a Santa Cruz, California electrofuels company (founded 2019, Rob McGinnis, Y > Combinator) that turns atmospheric CO2 into carbon-neutral methanol, gasoline, diesel, jet fuel and > renewable natural gas using a "no-desorb" direct air capture system and its Faraday Reactor > hydrocarbon electrolyzer, run on off-grid solar. It also markets an Ultra Long Duration Energy > Storage (ULDES) product for data-center power. It is a physical manufacturer: as of 2026-08-05 it > publishes NO product API, no developer portal, no SDK and no /llms.txt. The only machine-readable > surface on its hosts is the WordPress REST API (wp/v2) that serves its own corporate website. ## Company - [Prometheus Fuels](https://prometheusfuels.ai/): Company website. The original domain prometheusfuels.com 301-redirects here. - [About](https://prometheusfuels.ai/about/): Company background, team, plant, investors and customers. - [Technology](https://prometheusfuels.ai/technology/): The direct air capture and Faraday Reactor process. - [ULDES](https://prometheusfuels.ai/uldes/): Ultra Long Duration Energy Storage for data-center power. - [GitHub organization](https://github.com/Prometheus-Fuels): Exists ("Making fuel from the air.") but has zero public repositories. - [LinkedIn](https://www.linkedin.com/company/prometheusfuels) - [X](https://x.com/prometheusfuels) - [YouTube](https://www.youtube.com/@PrometheusFuels) - [Forge Global secondary-market listing](https://forgeglobal.com/prometheus-fuels_stock/) ## APIs Prometheus Fuels operates one machine-readable API surface: the WordPress REST API serving its corporate website. This is site infrastructure, not a product API. Read operations respond anonymously; write operations require WordPress application passwords. - [WordPress REST API discovery](https://prometheusfuels.ai/wp-json/): Root discovery document; 29 namespaces advertised. - [wp/v2 route index](https://prometheusfuels.ai/wp-json/wp/v2): 134 routes, self-describing with per-route arguments. - [WordPress REST API reference](https://developer.wordpress.org/rest-api/reference/): The upstream human reference for these routes. Collections that returned HTTP 200 anonymously on 2026-08-05: `posts`, `pages`, `news-articles`, `categories`, `tags`, `media`, `comments`, `users`, `search`, `taxonomies`, `types`, `statuses`. Collections that returned 401: `settings`, `menus`, `themes`, `plugins`, `wp-abilities/v1/abilities`. The `news-articles` collection is the site-specific custom post type carrying Prometheus Fuels press and news coverage — the one endpoint here that returns company-specific content rather than generic CMS plumbing. ## Specs Twelve OpenAPI 3.1.0 documents (94 operations total) derived by API Evangelist from the route metadata the server itself publishes. Nothing was invented. - openapi/prometheus-fuels-news-articles-api-openapi.yml — 10 operations - openapi/prometheus-fuels-pages-api-openapi.yml — 13 operations - openapi/prometheus-fuels-posts-api-openapi.yml — 13 operations - openapi/prometheus-fuels-media-api-openapi.yml — 9 operations - openapi/prometheus-fuels-users-api-openapi.yml — 21 operations - openapi/prometheus-fuels-categories-api-openapi.yml — 7 operations - openapi/prometheus-fuels-tags-api-openapi.yml — 7 operations - openapi/prometheus-fuels-comments-api-openapi.yml — 7 operations - openapi/prometheus-fuels-search-api-openapi.yml — 1 operation - openapi/prometheus-fuels-taxonomies-api-openapi.yml — 2 operations - openapi/prometheus-fuels-types-api-openapi.yml — 2 operations - openapi/prometheus-fuels-statuses-api-openapi.yml — 2 operations ## Semantics - authentication/prometheus-fuels-authentication.yml — HTTP Basic via WordPress application passwords. - conventions/prometheus-fuels-conventions.yml — pagination, filtering, field selection, caching, CORS. - errors/prometheus-fuels-problem-types.yml — the flat WordPress error envelope and its codes. - data-model/prometheus-fuels-data-model.yml — entity graph and relationships. - lifecycle/prometheus-fuels-lifecycle.yml — versioning by namespace; no deprecation policy, SLA or status page. - conformance/prometheus-fuels-conformance.yml — standards conformance, honestly scored. - security/prometheus-fuels-domain-security.yml — TLS 1.3; no HSTS, DNSSEC, CAA, SPF or DMARC observed. - skills/ — two packaged Agent Skills grounded in real operationIds. ## Not available - No developer portal, API reference, pricing, status page, changelog or support surface for any API. - No OpenAPI, AsyncAPI, GraphQL SDL or Postman collection published by the company. - No MCP server: /wp-json/mcp returns `rest_no_route`; no `mcp` namespace is advertised. - No A2A agent card: /.well-known/agent-card.json and /.well-known/agent.json both 404. - No /.well-known/ documents of any kind, including security.txt. - No first-party SDK or client library on npm, PyPI or any other registry. - Nothing about fuel production, ULDES systems, plant telemetry or offtake agreements is exposed through any API.