energy.fuel-stations

Locate alternative-fuel stations across the US via NREL Alternative Fuels Data Center. Search by lat/lon + radius (miles), state, or zip. Filter by fuelType (BD=Biodiesel | CNG=Compressed Natural Gas | ELEC=Electric vehicle charging | E85=Ethanol | HY=Hydrogen | LNG=Liquefied Natural Gas | LPG=Propane | RD=Renewable Diesel), status (E=Available | P=Planned | T=Temporarily Unavailable), access (public/private), and EV network. For EV chargers, returns connector types (J1772, CHAdeMO, Tesla, etc.), Level 1/2/DC-fast counts, pricing, and access hours. Indispensable for trip-planning agents, fleet logistics, EV-adoption analysis.

price
$0.0012 USDC per call
method
GET/api/energy/fuel-stations
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The fuel stations API is a pay-per-call energy endpoint built for AI agents and autonomous software. Locate alternative-fuel stations across the US via NREL Alternative Fuels Data Center.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in fuel stations data source for an agent tool-use loop, an MCP host, or a backend that needs energy data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
latnumber
min -90 · max 90
lonnumber
min -180 · max 180
radiusnumber
min 0.1 · max 500
fuelTypestring
statestring
min 2 chars · max 2 chars · match ^[A-Za-z]{2}$
zipstring
match ^\d{5}$
statusstring
one of: all | E | P | T
accessCodestring
one of: all | public | private
networkstring
min 1 chars · max 80 chars
limitinteger
min 1 · max 200

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/energy/fuel-stations?lat=-90&lon=-180&radius=0.1&fuelType=example&state=xx&zip=12345&status=all&accessCode=all&network=example&limit=25'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/energy/fuel-stations?lat=-90&lon=-180&radius=0.1&fuelType=example&state=xx&zip=12345&status=all&accessCode=all&network=example&limit=25' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/energy/fuel-stations?lat=-90&lon=-180&radius=0.1&fuelType=example&state=xx&zip=12345&status=all&accessCode=all&network=example&limit=25'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.energy.fuelStations({
  "lat": -90,
  "lon": -180,
  "radius": 0.1,
  "fuelType": "example",
  "state": "xx",
  "zip": "12345",
  "status": "all",
  "accessCode": "all",
  "network": "example",
  "limit": 25
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.energy.fuel_stations(lat=-90, lon=-180, radius=0.1, fuelType="example", state="xx", zip="12345", status="all", accessCode="all", network="example", limit=25)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "energy.fuel-stations",
    "arguments": {
      "lat": -90,
      "lon": -180,
      "radius": 0.1,
      "fuelType": "example",
      "state": "xx",
      "zip": "12345",
      "status": "all",
      "accessCode": "all",
      "network": "example",
      "limit": 25
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
metaobject
Example response datajson
{
  "ok": true,
  "items": [
    {}
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "meta": {
    "stationLocatorUrl": "example"
  }
}

FAQ

Do I need an API key to use the fuel stations API?
No. energy.fuel-stations is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the fuel stations API cost?
$0.0012 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the fuel stations API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call energy.fuel-stations from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: fuel stations api · energy fuel stations api · fuel stations api for ai agents · x402 energy api · fuel stations api no api key · pay per call fuel stations api · energy api