METERED DATA ORACLE · LIVE ON BASE

Real-world signal,
priced per query.

Agents subscribe to signed feeds and pay a fraction of a cent for each datapoint they actually read. No flat fees, no stale data, no API keys.

$PULSE · 0x9Df1...b83C · BASE
BTC/USD.spot · 1H
$68,420
+1.84%
24h
Watchlist
ETH3,915 +0.6
SPX5,930 +0.4
FED74% -3.1
NYC21°C +2.0
GAS0.021 +8.1
Live feeds
0
Read latency
0
Feed uptime
0
Monthly fee
$0
last read  BTC/USD.spot  $0.0008
✓ signed · 0xF2a1...9d
The problem

Agents need fresh data, not data plans.

An agent might read a price once an hour or ten thousand times a second. Flat monthly API plans make no sense for software that scales by the request. Pulsefeed meters access at the datapoint, so an agent pays for exactly the signal it consumes and nothing more.

Feed catalog

Hundreds of signed feeds.

SymbolFeedValue24hLatencyPer read
BTCspot index$68,420.11+1.84%42ms$0.0008
ETHspot index$3,915.40+0.62%39ms$0.0008
FEDrate decision odds74.0%-3.10%58ms$0.0012
NYCtemperature21.0°C+2.0°71ms$0.0004
SPXindex level5,930.20+0.41%47ms$0.0010
NFLgame win prob61.5%-4.20%63ms$0.0009
GASbase gwei0.021+8.10%35ms$0.0003
Protocol

Subscribe, read, pay per point.

[01]

Pick a feed

Choose from hundreds of feeds across markets, prediction odds, weather, sports, and on-chain metrics.

[02]

Read on demand

Pull a single value or stream updates. Each datapoint arrives cryptographically signed by its provider.

[03]

Pay per read

x402 settles a fraction of a cent in USDC per read. Providers earn directly, with no platform lock-in.

Features

Built for software buyers.

metered_access

Pay per datapoint read, not per month. Cost scales exactly with consumption, with no minimums.

signed_data

Every value carries a provider signature. Agents verify authenticity on-chain before they act on a number.

realtime_stream

Subscribe for push updates over webhooks or hold an open stream for tick-by-tick signal.

diverse_catalog

Markets, prediction odds, weather, sports, on-chain metrics and event outcomes in one interface.

provider_payouts

Anyone can list a feed, stake for trust, and earn USDC on every read with no middleman.

low_latency

Reads return in tens of milliseconds so agents act on signal while it is still fresh.

API

One read, one cent fraction.

Read any feed over x402 or wire it into your agent through the MCP server. Each call returns a signed value and settles in USDC. Subscribe for streams when you need every tick.

VIEW API REFERENCE
read.ts● connected
// read a signed datapoint, pay per call
const p = await pulse.read({
  feed: "BTC/USD.spot",
  pay:  "x402"            // $0.0008 USDC
});

pulse.verify(p.sig);     // authentic
// { value: 68420.11, ts: 17..., provider: "coinbase" }
Token

$PULSE

The settlement rail and trust bond for the data network.

pay/

Per-read settlement

Reads settle in USDC over x402, with a protocol cut collected and shared with PULSE stakers.

stake/

Provider trust bond

Feed providers stake PULSE for listing and are slashed for publishing bad or stale data.

vote/

Catalog governance

Holders decide which feeds are featured and set quality and dispute thresholds.

FAQ

Common questions.

Every datapoint is signed by its provider and verifiable before your agent uses it. Providers stake PULSE as a bond and are slashed for publishing false or stale values.

Typically a fraction of a cent in USDC per read, settled instantly over x402. No subscriptions and no minimums.

Yes. Subscribe to a feed for webhook pushes or hold open a stream for tick-by-tick data. You pay per datapoint delivered.

Yes. Anyone can list a feed, stake PULSE for trust, and earn USDC on every read. The catalog is open and governed by token holders.

Give your agent a pulse.

Fresh, signed, real-world signal, priced by the read.