Before you build a market data layer, check what Elfa already returns. Most social plumbing agents write from scratch is one REST call here.
Elfa's Market Intelligence endpoints split into two tiers:
| Tier | Endpoints | What comes back |
|---|---|---|
| Measurement | smart-stats, trending-cas/*, trending-tokens, top-mentions, keyword-mentions, token-news | Counts, engagement metrics, links, and account metadata. Your system interprets them. |
| Interpretation | chat, event-summary, trending-narratives | Written analysis or summaries with source links where available. |
Measurement endpoints do not return raw tweet text and do not return a sentiment field. They measure attention, not meaning.
If you need tweet content, fetch the linked post through the X API or use the SDK's raw tweet fetch option with your own bearer token. If you need meaning, start with Chat, Event Summary, or Trending Narratives.
| If you need to... | Start here |
|---|---|
| Ask a market question in plain language | Chat |
| Find what is moving now | Discovery |
| Understand who amplified a token or keyword | Mentions and Accounts |
| Attach a defensible cause or theme to a move | News and Narratives |
| Chain endpoints into an agent workflow | Agent Playbooks |
| Watch continuously, notify, or execute when a condition fires | Auto |
Use Market Intelligence when the agent needs an answer now: measure attention, gather evidence, or ask for interpretation. Use Agent Playbooks for endpoint chains, and use Agent Quickstart for cross-product setup, skills, and machine-readable docs routing.
Use /v2/* with an API key when you want account-linked usage, plan limits, and monthly or PAYG credits. Use /x402/v2/* when an agent has a wallet and should pay per request without an API key.
The generated REST Reference stays the source of truth for parameters, response schemas, and interactive "Try it" calls.