Quickstart

1. Create a key from your dashboard. It is shown once, so copy it straight into an environment variable.
2. Send it as a bearer token on every request.
3. Read the JSON response.

Request

curl https://fearandgreedgraph.com/api/v1/fear-greed \
  -H "Authorization: Bearer $FEARANDGREED_API_KEY"

Response

{
  "as_of": "2026-08-29",
  "current": 54,
  "zone": "Neutral",
  "previous_close": 51,
  "indicators": { "market_momentum": 52.4, "...": null },
  "plan": "free"
}

Python

import os, requests

r = requests.get(
    "https://fearandgreedgraph.com/api/v1/fear-greed",
    headers={"Authorization": f"Bearer {os.environ['FEARANDGREED_API_KEY']}"},
    timeout=10,
)
r.raise_for_status()
print(r.json()["current"])

JavaScript

const res = await fetch("https://fearandgreedgraph.com/api/v1/fear-greed", {
  headers: { Authorization: `Bearer ${process.env.FEARANDGREED_API_KEY}` },
});
if (!res.ok) throw new Error(await res.text());
const { current, zone } = await res.json();

Authentication

Pass your key in the Authorization header using the Bearer scheme. Keys begin with sk_live_.

Authorization: Bearer sk_live_xxxxxxxxxxxxxxxxxxxx

There is no query-string parameter for the key, deliberately: URLs are written to server logs, browser history and Referer headers, and a key that reaches any of those is compromised.

Rate limits

Limits are applied per key. Free and Plus keys use a 24-hour window; Pro keys use an hourly window. Every response carries the current state:

X-RateLimit-Limit: 300
X-RateLimit-Remaining: 297

Exceeding the limit returns 429 with a Retry-After header in seconds. Back off for that long rather than retrying immediately.

Errors

Errors return the appropriate status with a JSON body of the form { "error": "..." }.

Endpoints

Endpoints marked live are available now. The rest are documented ahead of release and are not yet callable.

MCP server

Open the MCP setup guide for client configurations, example questions, the tool reference and troubleshooting.

Connect an AI agent to the site through the read-only Model Context Protocol server. It uses Streamable HTTP at https://fearandgreedgraph.com/mcpand requires a Pro API key. The same key works for REST requests.

In your agent's MCP settings, add the server URL and set the Authorization header to Bearer YOUR_API_KEY. Keep the key in your agent's secret storage, not in a shared config file.

The server provides these tools:

• get_site_guide explains the site, methodology and data sources.
• find_site_pages locates pages relevant to a question.
• get_fear_greed_index returns the latest dated reading and indicators.
• get_fear_greed_history returns up to 365 recent daily readings.
• get_stock_quotes returns prices and daily changes for up to ten tickers.

Ask your agent, for example, “What is the latest Fear and Greed reading, and how has it changed over the past week?” Tool results include source links and dates so the agent can cite the site accurately.

Key security

• Store keys in environment variables, never in source control. If a key reaches a public repository, revoke it immediately.
• Use one key per application. A leak then costs you one revocation rather than every integration you run.
• Rotate on staff changes and whenever a key may have been exposed. Create the replacement, deploy it, then revoke the old one for zero downtime.
• We cannot recover a key. Only a hash is stored, so support cannot read one back to you. Rotation is always the answer.

Manage all of this from your API keys dashboard.