Massive.com

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The quickstart calls deprecated /v3/reference/dividends, while its linked dividend reference specifies /stocks/v1/dividends. The signup, key-retrieval, and curl steps are unambiguous, but the quickstart's first call targets /v3/reference/dividends, which the documentation index labels "Dividends (Deprecated)", while the live Dividends page and its markdown mirror both document GET /stocks/v1/dividends. The REST Quickstart walks through signing up, obtaining an API key from the dashboard, choosing between query-string or header auth, and provides a working curl command against the dividends endpoint. The dividends endpoint documentation also shows the full URL, parameters, and sample response.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

Pricing and the dividend plan table give 5 calls per minute, paid unlimited calls, a 100-RPS ceiling, and plan access. No request limit appears anywhere under /docs/; the four values are only reachable in one knowledge-base article that also states "While we do not have a specific rate limit" alongside the 5-per-minute free-tier cap and the 100-requests-per-second ceiling, while plan-specific data access lives separately on each endpoint page as "Included in all Stocks plans". The free-tier limit of 5 API calls/minute and paid plans labelled 'Unlimited API Calls' are present only in the pricing page's client-side JavaScript. There is no dedicated rate-limits page in the docs. No 'recommended ceiling' (e.g. requests/second beyond which performance degrades) is documented anywhere. Plan-specific data access (2y/5y/10y/20+ years history, which data types are included) is available on the pricing page.

FAIL consensus from 3 FAIL.

The docs recommend staying below 100 requests per second, but give no exact throttle trigger or retry timing. The only error condition documented in the REST path is the authorization error; no page under /docs/ mentions HTTP 429, a Retry-After header, retry timing, or backoff, so recovery from REST throttling cannot be derived from the documentation. The official documentation never mentions HTTP 429 by status code, never describes the trigger condition, never specifies retry timing or a Retry-After header, and does not offer a documented safe correction strategy. The Python client README generically warns of 'rate limit errors' and the REST Quickstart mentions that client libraries handle 'retry logic' but gives no concrete guidance. An agent recovering from a 429 would have to guess timing and strategy.

PASS consensus from 3 PASS.

The /docs/websocket/stocks fetch failed as JavaScript-rendered, but the quickstart documents connection, authentication, confirmation, and subscription. One page carries the whole path: the wss://socket.massive.com/stocks endpoint, the connected status frame, the {"action":"auth","params":"YOUR_API_KEY"} message, the auth_success confirmation, and a working subscribe example. The WebSocket Quickstart documents the full path: two connection URLs (delayed wss://delayed.massive.com/stocks, real-time wss://socket.massive.com/stocks), the auth message to send the API key, the successful-auth response containing 'status':'auth_success' and 'message':'authenticated', and the subscription message format {'action':'subscribe','params':'AM.AAPL,AM.MSFT'}. The server-to-client connection-handshake message is also shown.

PARTIAL consensus from 3 PARTIAL.

The current example matches REST, but package names conflict and another dividend example uses the deprecated method. The Python sample on the Dividends page calls list_stocks_dividends with the same limit and sort parameters as the shell example and matches the current /stocks/v1/dividends endpoint, but no page under /docs/ gives the install command, which is only on the linked GitHub repository as "pip install -U massive". The Python client README clearly documents pip installation, import, and client creation with an API key. However, the README's code examples only show list_aggs, get_last_trade, list_trades, get_last_quote, and list_quotes, not list_dividends or any dividend-retrieval method. The REST API uses GET /stocks/v1/dividends, and the Python client does expose list_dividends() (on DividendsClient), but the README does not demonstrate it, so an agent following only the README would not discover the dividend path.