Getting Started
Guavy reads and scores market news and commentary around the clock, and serves the results over a REST API and a native MCP server. This guide covers what you need to make your first calls.
API Overview
Every news story, analysis, press release and official statement Guavy reads gets six scores (Sentiment, Clout, Speculation, FUD/FOMO Intensity, FUD/FOMO Direction and Tone) and a list of the assets it may affect, each with a direction and a time frame. The API serves those scored items alongside sentiment history, price history, technical indicators and trend data, with the same core endpoints in every market Guavy covers. Crypto also has the Guavy trade simulator: buy and sell signals, recommendations and backtests.
To use the Guavy API, you need a Guavy account. Every live market is reachable on every plan; your plan sets your per-market token budget and commercial-use rights, not which markets you can access. Once you have an account and are signed in, you can copy your API key from the dashboard and start making calls.
Using the Guavy API
There is no batch endpoint: a route that takes a symbol answers for
that one instrument. If you are syncing a large amount of data, request only as
many records as you need with limit (a smaller limit
costs fewer tokens), page with skip on the routes that take it
(list-symbols and the trade-simulator lists), and cache responses so you do not
fetch the same data twice. Any other route ignores skip.
Commercial use in apps, funds, or agents, including redistribution, is covered by a Business license.
Everything is plain REST over HTTPS, so it works the same from a backend service, a script, or a mobile app, with no separate SDK or mobile license required.
API Structure
The Guavy API generally follows REST conventions, with some deviations.
- Each endpoint is one route, grouped by section (Instruments, Sentiment, Newsroom, Trades, Technical Analysis).
- Every data request is a GET.
- Requests require authentication using your API key, sent as a Bearer token.
- Responses are JSON objects, served as
application/json. - Errors include standard HTTP status codes and messages.
- The action is named in the path (get-recent-briefs, get-price-history), not by the HTTP method.
The API is described in an OpenAPI specification at /openapi.json, and each reference page lists its parameters and response fields with their types.
All API endpoints are available relative to https://guavy.com.
