X-RAY Documentation

X-RAY developer docs: REST API reference, MCP integration for Claude, and guides for querying live Web3 labor-market data.

All pages

  1. Introduction
  2. Platform
  3. Data Sources
  4. Coverage & Refresh
  5. Reading the Numbers
  6. Signals
  7. Hiring
  8. Development
  9. Tokens
  10. Protocols
  11. Landscape
  12. Company Profiles
  13. Workspace
  14. Custom Dashboards
  15. Comparing & Benchmarking
  16. MCP
  17. Getting Started with MCP
  18. What the Assistant Can Do
  19. Example Questions
  20. Subscription & Billing
  21. Troubleshooting
  22. Account & Access
  23. FAQ

Introduction

X-Ray is a market-intelligence workspace for Web3. It watches what companies do — who they hire, what they ship, how their tokens trade, how much value their protocols hold, and what the market is talking about — and turns that into a small number of readable dashboards.

What you get

  • Six live signal surfaces — Hiring, Development, Tokens, Protocols, Landscape, and Company profiles.
  • Custom dashboards — pick the companies you care about and track them as one portfolio.
  • MCP access — connect an AI assistant (Claude, ChatGPT, Cursor and other MCP clients) directly to X-Ray data and ask questions in plain language.

How access works

| Surface | Who can use it | | --- | --- | | All signal dashboards | Everyone, no account needed | | Company profiles & search | Everyone | | Custom dashboards | Any signed-in account (free) | | MCP server | Paid MCP subscription |

There is no public REST API. Programmatic access is delivered through MCP — see the MCP section.

Where to start

  1. Open the Overview deck on the home page for the state of the market in one screen.
  2. Drill into a single signal — Hiring, Development, Tokens, Protocols or Landscape.
  3. Sign in and build a Custom dashboard around the companies you track.
  4. Subscribe to MCP if you want your AI assistant to query the same data.

Platform

How X-Ray is put together: where the data comes from, how often it refreshes, and how to read what you see.

  • Data sources — the feeds behind each dashboard.
  • Coverage & refresh — what is tracked and how current it is.
  • Reading the numbers — the conventions used everywhere in the product.

Data Sources

Every number in X-Ray comes from an observable, external source. Nothing is estimated by a model, and there are no AI-generated opinions anywhere in the product.

The five collectors

Hiring. Job postings from company career pages and job boards are collected, de-duplicated, and normalised into a common shape: role, grade, location, salary range, and skill clusters. Postings are also tracked when they disappear (a role was closed) and when they reappear (the same role was re-opened).

Development. Public repository activity for tracked organisations — commits, releases, contributor counts, stars and forks — collected continuously so short-term shifts in engineering output are visible.

Tokens. Market data for tracked assets: price, market capitalisation, volume, supply, plus market-wide indicators such as total market cap, dominance, and sentiment indices.

Protocols. On-chain value metrics per protocol — total value locked, chain breakdown, and short-window change — for the whole DeFi universe, not just the largest names.

Landscape. Real-time editorial and event streams: exchange listings and delistings, market news, governance-forum activity, and political signal relevant to crypto markets.

Normalisation

Raw records are mapped onto shared taxonomies so cross-signal questions work:

  • Companies — one canonical record per company, with logo, website and profile.
  • Sectors — a two-level taxonomy (sector → subsector) attached to companies.
  • Blockchains — companies are linked to the chains they build on.
  • Skill clusters — hard skills, soft skills and benefits, extracted from job descriptions and grouped into comparable clusters.

Because everything routes through the same company record, you can move from a hiring spike to that company's repositories, token and protocol without changing tools.

Coverage & Refresh

Refresh cadence

| Signal | Refresh | | --- | --- | | Hiring | Continuous through the day; new postings usually visible within hours | | Development | Continuous polling for commits and releases; full repository snapshot daily | | Tokens | Daily market snapshot, with history retained per day | | Protocols | Daily snapshot of value locked, with history retained per day | | Landscape | Near real-time — streams are polled every minute |

History

Every collector writes both a latest state and a historical record. That is why every dashboard can show not only "where things are" but "where things moved" — trends, deltas and period comparisons are computed from stored history, never re-derived from a single snapshot.

Coverage

Coverage is company-first. A company enters X-Ray once it is a meaningful actor in Web3, and from that point every collector that applies to it starts running: careers page, repositories, token (if one exists), protocol (if it operates one). Companies without a token or protocol still appear fully in Hiring and Development.

Reading the Numbers

A few conventions apply across the whole product.

Time windows

Every metric states the window it covers — 30D, 24H, 7D. When a delta is shown, it compares the window to the exact preceding period of the same length: a 30-day figure is compared with the 30 days before it, never with a calendar month.

Missing data

If a value cannot be computed from real data it renders as an em dash (—) and its delta is hidden. A zero always means a real, measured zero.

Deltas you can trust

Deltas are suppressed when the underlying baseline is too thin to be meaningful — for example when a comparison period has almost no data, or when a computed change is implausibly large. A hidden delta is intentional, not a bug.

Active vs. closed roles

A vacancy is active while it is still published at the source. When it disappears it is marked closed and keeps its history. When an identical role is published again it is linked to the previous posting and counted as re-opened, which is how repeated-posting patterns become visible.

Units

Large numbers are abbreviated consistently — K thousands, M millions, B billions, T trillions — and a chart axis always uses one unit for the whole axis so bars stay comparable.

What is deliberately absent

  • No AI-written summaries or "market signals".
  • No subjective scores or rankings invented by X-Ray.
  • No user behaviour tracking inside the product.

The data is the product; interpretation is left to you.

Signals

Signals are the public dashboards. All of them are free and require no account.

| Dashboard | Question it answers | | --- | --- | | Hiring | Who is staffing up, for what roles, at what pay | | Development | Who is actually shipping code | | Tokens | How tracked assets and the market as a whole are trading | | Protocols | Where value is locked and where it is moving | | Landscape | What just happened — listings, news, governance, politics | | Company profiles | Everything above, for one company |

Every dashboard shares the same layout: a header block with headline metrics, a filter sidebar, and panels below. Filters are additive — narrowing one dimension narrows every panel on the page.

Hiring

Hiring is the earliest visible signal of intent. Companies hire months before they ship.

What the dashboard shows

  • Active roles — everything currently published across tracked companies.
  • Hiring activity over time — postings per day/week/month, split into published, re-opened and unpublished, so churn is distinguishable from growth.
  • Top hiring companies — ranked by open roles in the selected window.
  • Role composition — breakdown by grade (junior → lead) and by function.
  • Skills demand — the hard skills, soft skills and benefits appearing most often, grouped into clusters rather than raw keyword counts.
  • Compensation — median and average of published salary ranges, by sector and by grade. Only postings that disclose at least one salary value are counted.

Filters

Company, sector and subsector, blockchain, role grade, location, and date range. Location matching is inclusive: selecting a city also matches broader mentions of the same place.

Vacancy detail

Selecting a role opens the full posting — description, requirements, salary range, skill clusters, and links back to the company profile and the original source.

What to look for

  • A sustained rise in senior and lead roles usually precedes a product line, not a refill.
  • Repeated re-opening of the same role often indicates a hiring problem, not growth.
  • Skill clusters appearing across many companies at once are the clearest leading indicator of a technology shift.

Development

Development measures delivery. It is the counterweight to hiring: intent versus output.

What the dashboard shows

  • Commit activity — a calendar heatmap of daily commit volume across tracked organisations. Intensity is scaled by quantile, so quiet periods stay readable next to very active ones.
  • Commits over time — trend for the selected window with a comparison against the preceding period of equal length.
  • Releases — tagged releases with dates, so shipping rhythm is visible separately from raw commit noise.
  • Repository leaderboard — repositories ranked by recent activity, with stars, forks and contributor counts.
  • Contributors — how many distinct people are pushing code, which separates a healthy team from a single maintainer.

Filters

Company, organisation, repository, and date range.

What to look for

  • Rising headcount with flat commits is a warning sign; the reverse is often a team about to hire.
  • Release cadence tightening is a better ship signal than commit volume alone.
  • Contributor count collapsing while commits hold steady means concentration risk.

Tokens

Tokens covers tradable assets and the market context around them.

What the dashboard shows

  • Market header — total market capitalisation, 24-hour volume, and dominance of the leading assets.
  • Sentiment gauge — the market fear-and-greed reading, plus altcoin-season and broad-index indicators.
  • Asset table — price, market cap, volume, circulating and total supply, with change over the selected window.
  • Trend charts — historical market cap and volume, built from stored daily snapshots.

Filters

Asset, sector, and date range.

Notes on interpretation

Token history is stored as one snapshot per day, so intraday movement is out of scope by design — X-Ray is built for structural change, not for trading. Where a daily baseline is missing, the corresponding delta is hidden rather than computed against an incomplete point.

Protocols

Protocols tracks where capital actually sits.

What the dashboard shows

  • Total value locked — aggregate across all tracked protocols, with a 24-hour weighted change.
  • Protocol table — TVL per protocol with 1-day, 7-day and 30-day change, category, and the chains it runs on.
  • Category breakdown — how value is distributed across lending, DEXs, liquid staking, restaking and the rest.
  • Chain breakdown — which networks hold the value, and how that share is shifting.
  • History — daily TVL series per protocol.

Filters

Protocol, category, chain, and date range.

What to look for

  • Value migrating between chains is usually visible here days before it is discussed anywhere else.
  • A protocol whose TVL is flat while its category grows is losing share, even if its absolute numbers look fine.

Landscape

Landscape is the real-time layer: discrete events rather than aggregated metrics. Streams are polled every minute.

Tabs

Listings. New exchange listings and delistings, parsed per ticker, so a single announcement covering several assets produces one row per asset.

News. Crypto market news, cleaned at serve time — editorial widgets, promotional blocks and disclaimers are stripped so only the substance remains.

Governance. Posts from DeFi governance forums: proposals, discussions and votes across major protocol communities.

Politics. Political and macro signal relevant to crypto markets, including schedules and public statements that historically move the market.

How to use it

Landscape answers "what just happened", while the other dashboards answer "what is changing". A listing or a governance vote here is often the event that explains a move you noticed in Tokens or Protocols.

Company Profiles

Every tracked company has a public profile page that assembles its footprint across all signals.

On a profile

  • Identity — description, website, sectors, subsectors, and the blockchains it builds on.
  • Hiring — open roles, hiring activity over time, role and skill composition.
  • Development — repository activity and release cadence, where public repositories exist.
  • Market — token and protocol metrics, where they exist.

Finding a company

  • The search page lists all tracked companies with instant filtering.
  • The command palette (⌘K / Ctrl+K) searches companies, tokens, protocols and roles from anywhere in the product.

Public profiles show a representative slice of the underlying data. The complete series for a company is available inside custom dashboards and over MCP.

X-RAY · Data Stream · Insights · Docs · Pricing