- Brand
- Coinversa
- Category
- Data & Analytics
- Primary Subcategory
- Institutional Financial Data & Equity Research Platforms
Integration details
Description
Coinversa Pulse provides read-only analytics for Hyperliquid markets. Explore open interest, long/short positioning, liquidation risk, public-wallet trading activity, behavioral cohorts and builder revenue. Compare related assets across venues, inspect order-book structure, and check the coverage and freshness of available data. Coinversa supports market research and analytics; it does not place orders, sign transactions or transfer funds.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Institutional Financial Data & Equity Research Platforms
- Secondary Subcategories
- None listed
- Brand
- Coinversa
- Access
- Account required
- First tracked
- 2026-10-15
- Tool count
- 115
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Your score is coming
ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.
What discovery looks like

Get alerts for Coinversa Pulse
Get updates when Coinversa Pulse’s Discoverability Score or category rank changes.
Competing in ChatGPT Institutional Financial Data & Equity Research Platforms
View Category115 tools agents can invoke
Distinct wallets that filled at least one perp trade in the last 24h, exchange-wide, plus total match count. The 'daily active traders' headline number. Cached up to 120s.
pulse_active_traders
Lookup one asset by canonical name or synonym. Returns every venue it trades on, collateral tokens, open interest per venue, and synonyms list. Accepts both canonical names (GOLD, BTC) and synonyms (PAXG, XAUT) — the server resolves them. Use when the user mentions a specific asset and you need its venue availability.
list_asset
Get the biggest winning or losing trades across all of Hyperliquid. Use type='wins' for the largest profitable trades, or type='losses' for the largest losses. Useful for market sentiment and narrative analysis.
pulse_biggest_trades
Cohort composition of a builder's attributed users over the period (day/week/month): split by all-time exchange-wide profitability tier (pnlTiers) and size tier (sizeTiers), largest cohort first, each with users, share of totalUsers, builder fees paid, attributed volume, realized PnL, and fills. Tiers are LIFETIME labels, as legacy tier identifiers mapped in the server instructions — not the 30d-rolling tiers the pulse cohort tools use — and wallets missing from the rollup appear under 'untracked' so per-tier user counts always sum to totalUsers. Attribution slightly undercounts versus ledger revenue (trigger-order fills — see the response's dataNotes). Use for 'which profitability tiers make up builder X's users?' or 'which size tiers pay most of its fees?'. Requires Pro tier. Availability: computed per builder on request and can exceed its 30-second budget on large builders; if it times out, retry once a minute later.
builder_cohorts
Individual fills attributed to a builder (0x-hex address) within a lookback window (since, e.g. '6h' or '7d', clamped to 90d), optionally filtered to one exact coin (BTC, xyz:GOLD, @123 spot, #10010 HIP-4 outcome) or one wallet. Each fill: time, wallet, coin, marketType (perp|spot|hip4), side (BUY|SELL), price, size, USD volume, realized PnL, builderFeeUsd, tid, and the order id it attributes to (null if untracked). Trigger-order (stop/TP) fills are not yet attributed, so this feed slightly undercounts versus ledger revenue — see the response's dataNotes. Use for 'show me the flow going through frontend X right now' or auditing one wallet's activity via a builder. Requires Pro tier.
builder_fills
How fast and how unevenly a builder monetizes the wallets it acquires (takes only the 0x-hex builder address — no other parameters): users and minFills, avgRevenueUsd and medianRevenueUsd of lifetime attributed builder fees per qualifying wallet, concentration (avg/median — 1 = evenly spread, higher = skewed toward a few large payers, 0 when the median is 0), daysToPeak, daysToHalfRevenue and daysToThreeQuartersRevenue as {avgDays, medianDays} measured from each wallet's first attributed fill to its single highest-revenue day and to 50% and 75% of its lifetime fees, and peakDayDistribution bucketing those wallets into under7d, from7To30d and over30d. NOT the lifetime user base builder_lifecycle covers: the universe is the TRAILING-YEAR acquisition cohort — wallets whose first builder-fee order via this builder fell within the last 365 days, with at least minFills (fixed at 3) lifetime attributed fills — computed per wallet then aggregated, so young cohorts' truncated series bias the day counts low; see the response's dataNotes. Use for 'how fast and how unevenly does builder X monetize a new user?'. Requires Pro tier.
builder_journey
Builders (HIP-3 dexes, frontends, bots) ranked by exact revenue from Hyperliquid's on-chain cumulative builder-fee ledger over the requested period. Each row carries join-attributed fill volume, distinct users, and fill counts — plus the same metrics for the immediately preceding window for deltas — the builder's most common requested fee rate over the last 7d of orders (feeTenthsBp, tenths of a basis point), and builderName from a curated registry (omitted when unknown). Attributed metrics slightly undercount versus ledger revenue because trigger-order fills (stop/TP) are not yet attributed — see the response's dataNotes; the 'verified' stamp gives the ledger block this data was reconciled against. Use for 'which builders earn the most?' or 'is builder X growing?'. Ledger history begins at the fee ledger's first on-chain entry: dataNotes states that date whenever a window predates it, and data_coverage (builder_ledger) reports it. Requires Starter tier or higher.
builder_leaderboard
Where every wallet that ever traded via this builder stands today (takes only the 0x-hex builder address — no other parameters): totalUsers split into five MUTUALLY EXCLUSIVE statuses that sum back to it, each {users, share} — active (attributed fill via THIS builder within 7d), cooling (within 30d but not 7d), switched (no fill here in 30d but at least one via a DIFFERENT builder in that window, detectable only with all-builder attribution), dormant (no fill via any builder in 30d, last fill here within 90d) and movedOn (no fill anywhere in 30d and none here in 90d) — plus trueRetention ((active+cooling)/totalUsers), churn ((dormant+movedOn)/totalUsers) and competitiveLoss (switched/totalUsers), which sum to 1, and competitiveLossFeesUsd, the builder fees those switched wallets paid to OTHER builders in the last 30d. LIFETIME universe on the ORDERS plane — every wallet that ever placed a builder-fee order via this builder, including ones whose orders never filled (they land in movedOn, or in switched if they filled via a DIFFERENT builder in the last 30d) — with only the status test reading recent attributed fills, so this is one snapshot of the whole historical user base rather than builder_retention's per-cohort monthly grid; see the response's dataNotes. Use for 'how many of builder X's users are still active, and how many did a rival take?'. Requires Pro tier. Availability: typically 1-15 seconds; can exceed its 30-second budget on the largest builders, in which case retry once a minute later.
builder_lifecycle
What this builder's users INTEND at placement time, before anything fills (0x-hex builder address plus a day/week/month period): totalIntents — non-trigger order intents plus still-PENDING stop/TP placements, the actions denominator — an actions[] mix of {actionType, orders, share}, largest first except the 'trigger' pseudo-type which is appended last, over 'order' (plain placements), 'batchModify' (modify intents on an existing order) and 'trigger' (pending stop/TP placements), a tifs[] time-in-force mix of {tif, orders, share} over non-trigger intents ('unknown' covers market orders and older rows), reduceOnlyShare, a trigger breakdown (total, takeProfit, stopLoss, triggerMarket, triggerLimit, positionTpsl, standaloneTpsl, resolved, pending) and fillConversion {orders, filledOrders, share} — the share of non-trigger intents whose own oid took at least one attributed fill. Measured on the PLACEMENT plane, not the fill plane behind builder_fills and builder_traders, so orders that never filled still count; trigger placement history begins 2026-03-24, and a resolved placement is excluded from totalIntents and the 'trigger' action because it already surfaces as a plain 'order' row, while the trigger breakdown covers both statuses — see the response's dataNotes. Use for 'do builder X's users place stops and take-profits, and how much of their order flow actually fills?'. Requires Pro tier.
builder_orders
The top 10 OTHER builders this builder's active users also traded through in the period (day/week/month), ranked by shared users — i.e. which other frontends/bots/dexes this builder's audience also uses. Returns activeUsers (the share denominator: distinct wallets with attributed fills via this builder) and per row: the other builder's 0x address, curated builderName (omitted when unknown), sharedUsers, share of this builder's active users, and feesUsd those shared users paid to the OTHER builder in the period. Based on attributed fills, which slightly undercount (trigger-order fills — see the response's dataNotes). Use for 'who is builder X's closest competitor?' or 'where else does its audience trade?'. Requires Pro tier.
builder_overlap
Single-builder overview for a 0x-hex builder address: exact revenue from Hyperliquid's on-chain builder-fee ledger over the period (day/week/month), first/last fee accrual timestamps, distinct fee tokens, most common requested fee rate over the last 7d of orders (feeTenthsBp, tenths of a basis point), a daily attributed series (fees/volume/users/fills) with the biggest day highlighted, top coins by attributed volume, and how many of the period's attributed wallets are all-time profitable. Attributed metrics slightly undercount versus ledger revenue (trigger-order stop/TP fills not yet attributed — see the response's dataNotes); builderName comes from a curated registry, omitted when unknown. Returns 404 for addresses with no revenue in the fee ledger. Use for 'how is builder X doing?' or 'what do people trade on frontend Y?'. Requires Starter tier or higher. Availability: typically 10-25 seconds on large builders; the coin split (topCoins) may come back null with an explanation in dataNotes when the live pass exceeds its budget. Ledger history begins at the fee ledger's first on-chain entry (see data_coverage, builder_ledger).
builder_profile
Monthly retention matrix for a builder's users (takes only the 0x-hex builder address — no other parameters): wallets are cohorted by the calendar month (YYYY-MM, UTC) of their first builder-fee order via this builder, and each cohort's activeWallets[k] counts wallets still active k months later, where 'active' = placed at least one builder-fee order that month (index 0 = the cohort month itself = newWallets). Covers the last 12 calendar months, oldest cohort first. Measured on the ORDERS plane — the order need not fill — so counts can exceed the attributed-fill user counts on builder_cohorts/builder_overlap; see the response's dataNotes for the attribution caveat. Use for 'does builder X retain users month over month, or churn them?'. Requires Pro tier.
builder_retention
Wallets that traded via a builder (0x-hex address) in the window, sortable by builder fees paid, volume, or realized PnL. Each row: wallet, realized PnL on its attributed fills, builderFeesUsd, volumeUsd, fills, latest equity (0 if untracked), and the wallet's ALL-TIME exchange-wide cohort tiers (pnlTier/sizeTier, as legacy tier identifiers mapped in the server instructions; null if untracked) — lifetime labels, unlike the 30d-rolling tiers the pulse cohort tools classify by, so memberships can differ. Attributed fills slightly undercount versus ledger revenue (trigger-order stop/TP fills not yet attributed — see the response's dataNotes). Use for 'who are builder X's biggest fee payers?' or 'how many Sharps-tier wallets use this frontend?'. Requires Pro tier. Availability: this endpoint computes per builder on request and can exceed its 30-second budget on large builders; if it times out, retry once a minute later.
builder_traders
Get historical hourly bias snapshots for trader cohorts. Returns long/short notional and account counts per tier. netBias is notional-weighted percent: 100 * (longNotional - shortNotional) / (longNotional + shortNotional), from -100 to +100 (zero for no notional), both per coin and in the global aggregate. Global bias is recomputed from summed notionals, not summed percentages. Filter with tierType and/or tier for a readable series. The default window is 7d. Returns { rows, totalCount, truncated, note? } with rows newest first, capped at limit (default 100, max 2000); when truncated, narrow filters or the time window. See data_coverage for the available history. Plan: Pro ($199/month) or higher.
pulse_cohort_bias_history
Get historical daily performance statistics for trader cohorts. Returns PnL, volume, trade counts, and active trader counts per tier — 32 tier rows per day, so filter with tierType and/or tier for a readable series. Use this to track the consistency and profitability of different groups over time. API default window 30d, max 30d. Returns { rows, totalCount, truncated, note? } sorted by date (newest first) then tierType and tier, capped at `limit` (default 100); when truncated, narrow with tierType/tier or a shorter since, or raise limit (max 2000). Cohort history is served for up to the last 30 days; see data_coverage. Plan: Pro ($199/month) or higher.
pulse_cohort_performance_daily
Get historical performance data for a specific trader cohort over time. Shows how a tier's aggregate PnL, trade count, and activity have changed day-by-day. Use for questions like 'how has the Sharps tier's daily PnL and trade count changed over the last month?' For long/short bias over time use pulse_cohort_bias_history. Plan: Pro ($199/month) or higher.
pulse_cohort_history
See what a specific trader cohort is holding RIGHT NOW. For example, get all live positions held by 'apex' (Apex) tier traders or 'heavyweights' (Heavyweights) size wallets. Returns the cohort's current open positions (coin, side, size, notional, entry price). Plan: Pro ($199/month) or higher.
pulse_cohort_positions
Get behavioral cohort analysis across every tracked wallet on Hyperliquid. Returns PnL tiers (Apex/apex, Sharps/sharps, Grinders/grinders, Scrapers/scrapers, The Crowd/crowd, Bleeders/bleeders, Trapped/trapped, Blown Out/blown_out) and size tiers (Heavyweights/heavyweights, Cruiserweights/cruiserweights, Middleweights/middleweights, etc). Response payloads use legacy tier identifiers; the server instructions map them to these display names. Each tier shows wallet count, avg PnL, avg win rate, and total volume. For the current tracked-wallet total, call pulse_global_stats first.
pulse_cohort_summary
See every trade a specific cohort has made recently. For example: 'show me all trades the apex (Apex) tier made in the last hour.' Plan: Pro ($199/month) or higher.
pulse_cohort_trades
How crowded and liquidation-prone one coin is right now. Get the current risk snapshot for a single coin. Use this when a user asks 'is BTC crowded?', 'who is holding the risk?', or 'how liquidation-prone is this market right now?'. Always returns the coin's concentration scalars — concentrationTop5, nearLiquidationNotional, nearLiquidationPositions, avgLiquidationDistancePct — plus availability/freshness stamps. Everything else is a section you opt into with `include`: market, longShort and topPositions are the default posture set; sizeBreakdown, liquidationHeatmap (40 buckets), liquidationSummary7d and recentLiquidations are opt-in. The response lists sections and omittedSections. topPositions is capped at `limit` (default 10, the API serves 20) with totalCount/truncated/hasMore/nextOffset; page with offset until nextOffset is null. For the heatmap alone use live_liquidation_heatmap; for liquidation events use live_recent_liquidations; for time series use live_coin_risk_history. Plan: Starter ($29/month) or higher.
live_coin_risk_snapshot
Side-by-side comparison of 2-5 wallets via their lifecycle summaries — win rate, total/avg PnL, hold duration, biggest win/loss, fees, liquidations. Use for head-to-head trader comparison ('who is the better trader, A or B?'). Plan: Starter ($29/month) or higher.
pulse_compare
Cross-market aggregation for one asset: per-venue long/short positions, notional, net bias, unique wallets, leverage, plus a cross-venue total. Also returns biasRange (max-min netBias across venues) to detect disagreement. Accepts canonical names or synonyms (e.g. PAXG resolves to GOLD). Use when the user asks 'is gold crowded?', 'do different dexes disagree on BTC direction?', 'total OI on ETH across all venues?'.
pulse_cross_market_asset
Current mark price of a crypto, commodity or stock perp on Hyperliquid: last mark and index price, 24h change, 24h volume, open interest and funding. Use it for a plain 'what is the price of X?'. When the user wants more than the latest price — a chart, how price moved or trended over hours or days, highs and lows, or indicators such as RSI, MACD or moving averages — call market_recent_candles instead (choose its interval, e.g. 1h or 4h). Use standard symbols (BTC, ETH, SOL) or builder dex format (xyz:SILVER, xyz:BRENTOIL, xyz:TSLA). io, mkts and para markets are not served yet.
market_price
Report the data window (start/end or latest row) and freshness stamp of each dataset behind this server, with the API route each figure came from. Relevant before relying on a historical date range or citing a start date, or for questions about how fresh or complete the data is; live tools (prices, positioning, liquidation maps) already return current data with their own freshness stamps. Datasets: trades (indexed trade history, /pulse/stats), builder_ledger (fee ledger + attribution coverage), census (chain-state stamp), hip4 (latest outcome fill), liquidations (risk-route availability/freshness), lifecycles (latest close; rolling 90-day window), cohort_history, book (L4 order-book rollups: coins covered, latest L1 height/time and age; snapshot-derived, refreshed every 60 s, no history). Where the API exposes no window start the dataset is listed with windowStart null and a note; no date is guessed. Sources are queried sequentially (the API's per-key burst allowance is small) and a failing source is reported in that dataset's notes rather than failing the call. Also returns server { version, hiddenTools, toolCount }. Free tier (some sources need a higher tier and then report the tier gate in notes).
data_coverage
Top entities (owners, NOT wallets) ranked by combined gross open entry notional across all their sub-accounts. This is the deduplicated view a wallet leaderboard cannot give: a fund running 35 sub-accounts appears as ONE entity with its true combined book. System/protocol accounts are excluded. Each row: entity master address, wallet count, open position count, gross entry notional. Requires Pro tier.
pulse_entity_leaderboard
Current open interest for the whole exchange by dex, with long/short notional split. Gross both-sides convention (matches HyperTracker/hl.eco headlines; halve for one-sided OI). Use for 'what's the OI on Hyperliquid / on xyz?', market-size questions, and long-vs-short balance checks. Cached up to 120s.
pulse_exchange_oi
Exchange-wide position vitals by dex: open positions and wallets holding them, plus the 24h flow — positions closed, liquidations, and TOTAL REALIZED PNL across the whole exchange (gross profits/losses split). Answers 'how many positions are open on Hyperliquid?' and 'did traders collectively make or lose money today?' Cached up to 120s.
pulse_exchange_positions
24h trading volume for the WHOLE exchange, split by dex: native Hyperliquid ('hl') plus every builder dex (xyz, io, para, ...), with per-dex match counts and distinct traders. Use for 'how much volume does Hyperliquid do?' — and note builder dexes are a large share of it (~30% on 2026-09-23; read byDex for today's split rather than assuming). Aggregates cached up to 120s.
pulse_exchange_volume
Exchange-wide view of crowding, leverage and liquidation risk right now. Get the exchange-wide market risk snapshot. Use for questions like 'which coins have the most concentrated open interest?' or 'how much notional is near liquidation?'. Always returns the exchange totals — open interest, unique wallets, long/short counts, net bias, average leverage, unrealized PnL, top-10 crowding concentration and near-liquidation notional — plus availability/freshness stamps. The bulky parts are sections you opt into with `include`: topCrowdedCoins (default), longShort (per-coin long/short breakdown, ~25 rows), liquidationSummary7d (7-day totals plus byCoin and a daily timeline) and history (one open-interest row per market, ~325). The response lists sections and omittedSections. topCrowdedCoins, longShort.bySymbol, liquidationSummary7d.byCoin and history.oi are each capped at `limit` (default 10) with totalCount/truncated/hasMore/nextOffset on each list; page with offset (nextOffset null means that list is finished) or raise limit. For a coin-level view use live_coin_risk_snapshot; for time series use live_coin_risk_history. Plan: Starter ($29/month) or higher.
live_risk_overview
Find closed perp positions whose exit captured a high fraction of the indexed maximum favorable excursion (MFE). Reports gross realized PnL before fees and direction-aware capture percent from entry/exit/MFE prices. Requires a favorable move of at least 1%; inconsistent rows whose exit exceeds indexed MFE are excluded, not clamped into 100% capture. Indexed extrema may differ from a fresh candle reconstruction. Within the rolling lifecycle retention window (normally 90 days; see data_coverage). Plan: Pro ($199/month) or higher.
pulse_exits_near_peak_favorable_move
Rank wallets by realized PnL per dollar of trading fees paid, over closed lifecycles in the rolling 90-day window. Returns wallet, total PnL, total fees, PnL-per-fee-dollar ratio, and lifecycle count. Use for 'which wallets earn the most PnL per dollar of fees?'. minPnl/minFees exclude wallets with small totals. Plan: Pro ($199/month) or higher.
pulse_fee_efficiency_leaderboard
Get global Hyperliquid trading statistics: total traders, trades, volume, PnL, and data coverage period. Use this to understand the overall scale of the market. dataStartDate/dataEndDate are the indexed trade window (from 2025-03-22); data_coverage reports the window and freshness of every dataset.
pulse_global_stats
Measure overlap between HIP-4 outcome traders and perp traders over a recent window. Returns outcome trader count, perp trader count, overlap count, and overlap percentage. Requires a Pro-or-higher key.
hip4_cross_product_overlap
Get daily HIP-4 volume trajectory: fills, unique trades, unique wallets, contracts, and notional USDH by day. Use for outcome-market activity trends. HIP-4 fills are indexed from mainnet launch (2026-05-02; the API clamps every look-back to it) — see data_coverage for freshness.
hip4_daily_volume
Return the most active HIP-4 outcomes over a recent window, ranked by fill count. Includes outcome/question metadata when available.
hip4_most_active
Get details for one HIP-4 outcome contract by outcome ID. Returns metadata when available plus side tokens, fills, unique wallets, notional USDH, and trading timestamps.
hip4_outcome
Get recent real fills for one HIP-4 outcome. Excludes settlement, pair-redeem, and auction-phase fills. Returns trade time, wallet, side, price, size, PnL, and fee.
hip4_outcome_recent_trades
Get the full HIP-4 summary for one outcome across both sides: fills, unique wallets, contracts, side notional, total notional, realized PnL, and trading window. Requires a Starter-or-higher key.
hip4_outcome_summary
List active HIP-4 outcome contracts that traded recently. Returns outcome IDs, question metadata when available, side tokens, fills, unique wallets, notional USDH, and first/last traded timestamps. Use when users ask what prediction/outcome markets are active. Outcomes are sorted by notionalUsdh descending and capped at `limit` (default 25, max 200; the API route has no paging, so the cap is applied by the connector) — the response carries count (returned), totalCount, truncated and a note; raise limit or shorten hours to see more. HIP-4 fills are indexed from mainnet launch (2026-05-02; the API clamps every look-back to it) — see data_coverage for freshness.
hip4_outcomes
Join one HIP-4 outcome's current net-positive holders to currently open perp positions on the same underlying asset. Returns per-side wallet counts, open-position overlap, long/short wallet counts, net underlying position, underlying notional, aligned vs hedge counts, prediction-native counts, and top wallets with a position-classification label (aligned, hedged or prediction-native). Use when users ask whether outcome traders are already exposed to the same asset, whether a side is directional or hedged, or which large outcome holders have no underlying perp exposure. Requires a Pro-or-higher key.
hip4_perp_position_context
List HIP-4 question metadata from Hyperliquid outcomeMeta, including question IDs, descriptions, fallback outcomes, named outcomes, settlement metadata, and parsed expiry/threshold fields when present. Questions are returned newest first (questionId descending) and capped at `limit` (default 25, max 200; the API route has no paging, so the cap is applied by the connector) from `offset` — the response carries count (returned), totalCount (after filtering), truncated, hasMore and nextOffset (null on the last page — stop there) and a note naming the next offset. Narrow with `status` (open = nothing settled yet, settled = at least one named outcome settled) or `search` (matches name, description and class). For one question's outcomes use hip4_outcomes; HIP-4 is indexed from mainnet launch (2026-05-02) — see data_coverage.
hip4_questions
List recent HIP-4 settlements. Returns outcome ID, settlement time, winning side when determinable, winner/loser fill counts, winner payouts, and loser losses.
hip4_recent_settlements
Rank top HIP-4 outcome traders by recent outcome activity. Returns address, fills, distinct outcomes, contracts, notional USDH, and realized PnL. Requires a Starter-or-higher key.
hip4_top_traders
Get one wallet's HIP-4 outcome history: outcome ID, side index, side token, fills, net shares, gross bought/sold USDH, realized PnL, and first/last traded. Requires a Starter-or-higher key. Rows are sorted by gross notional (grossBoughtUsdh + grossSoldUsdh) descending and capped at `limit` (default 50, max 200; the API route has no paging, so the cap is applied by the connector) — the response carries count (returned), totalCount, truncated and a note; raise limit or shorten days to see more. The API clamps days to 90 and to HIP-4 mainnet launch (2026-05-02) — see data_coverage.
hip4_trader_outcomes
Find wallets with a high win rate and positive PnL across a moderate number of trades. Filters by minimum win rate, minimum total PnL, and a minimum and maximum trade count; the maximum excludes the highest-activity wallets, which dominate PnL-ranked leaderboards. Returns matching wallets with their win rate, PnL and trade count.
pulse_high_win_rate_low_activity_wallets
Get historical hourly open interest snapshots (notional USD). Supports per-coin filtering or global exchange aggregation. Max range is 30 days. Plan: Pro ($199/month) or higher.
market_historical_oi
Global PnL heatmap by UTC hour of position close. Returns, for each of the 24 hours, lifecycle count, total PnL, avg PnL, wins, and losses. Use for 'what time of day is most profitable to close?' / session-bias analysis. Plan: Starter ($29/month) or higher.
pulse_hour_profitability
Largest individual fills on a market by USD notional (price x size) in a recent window, each with time, price, size, notional and both counterparties where indexed (wallet address, PnL and size cohort, and what the fill did to that wallet's position: Open Long, Close Short, ...). 'Whale' here means the TRADE is large (minNotional, default $1M, floor $100k) — not the 'whale' size tier, which is lifetime volume, and not realized PnL (pulse_biggest_trades ranks by PnL). Use for 'any big BTC prints in the last hour?', 'who sold $5M of ETH?'. The window is capped at 24h by the API (fills are not indexed by notional); longer values are rejected. Returns largest first. sourceCount/sourceTruncated are the API's own figures (sourceTruncated=true means at least one more fill above minNotional exists in the window); count/totalCount/truncated describe the rows in THIS response after any size limiting, so never read a shortened list as complete. Fills whose exchange id was missing carry idKind=synthetic and cannot be paired with their counterparty. asOf is compute time, not an ingestion watermark (coverage.completeness is unknown). Pro tier.
live_whale_trades
Get the largest individual liquidations across Hyperliquid — forced closes ranked by realized loss. Returns wallet, coin, side, entry VWAP, peak size, realized PnL, penalty fee, liquidation method, and liquidator address. Use for 'which liquidations had the largest losses?' and post-mortem analysis. Default returns $10k+ losses. Plan: Pro ($199/month) or higher.
pulse_largest_liquidation_losses
Answers: who is sitting on this book, and where? Returns the largest resting orders (wallet, side, price, size, original size, distance from mid, tif, order type, how long it has rested) and the biggest wallets per side by total resting size. Example: 'is one wallet holding up the ETH bid?' — book_whales('ETH', limit=10) and check whether bid_wallets[0].size dominates. Wallet addresses join to the trader tools (pulse_trader_profile, pulse_trader_performance). Snapshot-derived: refreshed every 60 s, latest-only (no history), and `as_of_height` is the L1 block the answer is true at — check `age_s` before citing it; a rollup older than 20 minutes (`age_s` > 1200) returns 503. `market_orderbook` remains the aggregated L2 view; this is the L4 one. Coin is case-sensitive in the node's own spelling (BTC, xyz:GOLD, #28200) and is passed through unchanged — 'btc' will 404. Plan: Pro ($199/month) or higher.
book_whales
Coinversa Pulse ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Coinversa Pulse's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Coinversa Pulse alternatives on ChatGPT?
As of 2026-11-03, Coinversa Pulse competes with AeonData, Aiera, AIR Credit Intelligence, Alpha Vantage, ALPHAPORT.AI, AlphaYou - Market Intelligence, AnnuityRatesHQ, Balanços.AI and 72 more in ChatGPT Institutional Financial Data & Equity Research Platforms, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.


