PulseNetwork / machines

Data APIs robots can pay for.

Your robot can buy a weather check before takeoff. Pre-mission weather, ground-route hazards, grid carbon intensity for charge scheduling, CVE checks for fleet firmware — 22 endpoints a drone, AMR, humanoid, EV, or delivery rover pays for per call in USDC over the x402 protocol. No API keys, no accounts, no rate plans: HTTP 402 quote → machine wallet signs → data. Works with peaqOS machine wallets, Virtuals / EconomyOS agents, Coinbase agentic wallets, and any x402 client.

x402 v2 · exact · EIP-3009 USDC on Base (eip155:8453) USDC on Solana mainnet $0.01–$0.25 typical attribution + terms in every response

Pre-mission weather & air

Should this drone take off? Wind, storms, air quality, and wildfire smoke — checked in one paid call before the mission starts.

Ground-route hazards

Is the route safe for a rover or AMR? River levels, flood risk, seismic activity, and situational alerts along the way.

Charging & compute scheduling

When should the fleet charge or run heavy compute? Live grid carbon intensity, electricity prices, time-of-use windows, and EV cost math.

Fleet software safety

Is the stack the fleet runs on exposed? Deterministic CVE fact-checks and the CISA Known-Exploited-Vulnerabilities catalog for firmware and dependency triage.

Delivery & transit ops

Hand-off timing for last-mile machines: live service status, current delays, and airport ground context.

How a machine pays

Standard x402 — the same flow peaqOS replays for Machine-NFT wallets and any agent framework can run directly:

# 1. Unauthenticated call returns the quote
curl https://climatepulse.theaslangroupllc.com/api/climate/severe?location=Austin,TX
# → HTTP 402 { accepts: [ { scheme:"exact", network:"eip155:8453", asset: USDC, amount:"80000" },
#              { scheme:"exact", network:"solana:5eykt4…", asset: USDC, amount:"80000" } ] }

# 2. Machine wallet signs EIP-3009 TransferWithAuthorization for the quoted amount
# 3. Replay with the X-PAYMENT header → 200 + data + attribution + terms

Discovery at runtime: the x402 Bazaar / agentic.market (search “theaslangroupllc”), each host’s /openapi.json + /agent.json + /llms.txt, or the PulseNetwork hub and MCP server.

Machine-economy FAQ

Can a robot pay for an API without an account or API key?

Yes. Every endpoint here is x402-native: an unauthenticated call returns HTTP 402 with a machine-readable USDC quote; the machine signs the payment authorization with its own wallet and replays the request. No signup, no key, no rate plan — solvency is the only credential.

Which chains and tokens can a machine pay with?

Every 402 response quotes USDC on Base (eip155:8453, x402 v2 "exact" scheme via EIP-3009 TransferWithAuthorization) and USDC on Solana mainnet in the same accepts[] array. Pay with either.

Does this work with peaqOS machine wallets?

Yes. peaqOS executes x402 v2 exact/EIP-3009 USDC-on-Base payments — the same scheme these endpoints quote — so a Machine-NFT wallet can order any endpoint here through the standard peaqOS payment-intent flow with no adapter credentials.

Does this work with Virtuals agents and ACP?

Yes. Any x402-capable agent, including Virtuals EconomyOS agents, can call these endpoints directly; ACP job budgets can also settle over x402. PulseNetwork is a registered ACP seller.

How does a machine discover these endpoints at runtime?

Via the x402 Bazaar / agentic.market (search "theaslangroupllc"), this page, /openapi.json and /llms.txt on every host, or the PulseNetwork MCP server. Every paid response also carries source attribution and terms inline.