name: funda-data description: > Fetch financial data from the Funda AI API (https://api.funda.ai). Covers quotes, historical prices, financials, SEC filings, transcripts, analyst estimates, options flow/greeks/GEX, supply chain graph, social sentiment, Polymarket, congressional trades, economics, ESG, news, AI-enriched news (sentiment + event timeline), AI-company recruit signals, and a Claude API proxy via Bedrock. Triggers: stock quotes, balance sheet, income statement, cash flow, analyst targets, DCF, options chain/flow, GEX, IV rank, max pain, earnings/dividend/IPO calendar, 10-K/10-Q/8-K, suppliers/customers/competitors, insider trades, 13F, Reddit/Twitter sentiment, Polymarket, treasury rates, GDP, CPI, FRED, commodity/forex/crypto, stock screener, ETF holdings, COT, ticker sentiment, OpenAI/Anthropic/xAI/Google/Mercor/SurgeAI job postings, product launch probabilities, AI threat to public stocks. Also triggers for "funda" or "funda.ai". If only a ticker is provided and Funda API can answer, use this skill.

Funda Data API Skill

Query the Funda AI financial data API for stocks, options, fundamentals, alternative data, and more.

Base URL: https://api.funda.ai/v1 Auth: Authorization: Bearer <API_KEY> header on all /v1/* endpoints. Pricing: This is a paid API. A Funda AI subscription is required. See funda.ai for pricing details.

Step 1: Check API Key Availability

The skill resolves FUNDA_API_KEY in this order:

1. FUNDA_API_KEY environment variable
2. FUNDA_API_KEY in .env in the current directory
3. FUNDA_API_KEY in .env at the git repo root (so a worktree inherits the key from the main checkout)

!`if [ -n "$FUNDA_API_KEY" ]; then echo "KEY_FROM_ENV_VAR"; elif [ -f .env ] && grep -qE "^FUNDA_API_KEY=" .env; then echo "KEY_FROM_LOCAL_DOTENV:$(pwd)/.env"; else GIT_COMMON=$(git rev-parse --path-format=absolute --git-common-dir 2>/dev/null); if [ -n "$GIT_COMMON" ]; then ROOT=$(dirname "$GIT_COMMON"); if [ -f "$ROOT/.env" ] && grep -qE "^FUNDA_API_KEY=" "$ROOT/.env"; then echo "KEY_FROM_ROOT_DOTENV:$ROOT/.env"; else echo "KEY_NOT_SET"; fi; else echo "KEY_NOT_SET"; fi; fi`

Then act on the result:

• KEY_FROM_ENV_VAR — use $FUNDA_API_KEY directly in curl calls.
• KEY_FROM_LOCAL_DOTENV:<path> or KEY_FROM_ROOT_DOTENV:<path> — load the key from the reported .env before each request:

  export FUNDA_API_KEY=$(grep -E "^FUNDA_API_KEY=" <path> | head -1 | cut -d= -f2- | sed 's/^["'\'']//;s/["'\'']$//')
  

  Substitute the path printed by the check above. Prefer sourcing once at the start of a session rather than re-exporting on every call.
• KEY_NOT_SET — ask the user for their Funda API key. They can either:

  export FUNDA_API_KEY="your-api-key-here"
  

  or add FUNDA_API_KEY=your-api-key-here to .env at the repo root (preferred when working across worktrees).

Once the key is available, proceed. All curl commands below use $FUNDA_API_KEY.

Step 2: Identify What the User Needs

Match the user's request to a data category below, then read the corresponding reference file for full endpoint details, parameters, and response schemas.

Market Data & Prices

Company Fundamentals

Analyst & Valuation

Options Data

Supply Chain Knowledge Graph

Social Sentiment & Alternative Data

AI-Enriched News

SEC Filings & Transcripts

Calendar & Events

Economics & Macro

Other Data

AI Company Recruit Signals

Hiring-based alpha signals covering OpenAI, Anthropic, Google, xAI, SurgeAI, and Mercor.

Claude API Proxy

Step 3: Make the API Call

Use curl with the bearer token to call the Funda API. Read the appropriate reference file first for exact parameter names and response formats.

Template:

curl -s -H "Authorization: Bearer $FUNDA_API_KEY" \
  "https://api.funda.ai/v1/<endpoint>?<params>" | python3 -m json.tool

Response format: All endpoints return {"code": "0", "message": "", "data": ...}. Check that code is "0" — non-zero means an error occurred (the message field explains why).

Pagination: List endpoints return {"items": [...], "page": 0, "page_size": 20, "next_page": 1, "total_count": N}. Pages are 0-based. next_page is -1 when there are no more pages.

Step 4: Handle Common Patterns

Multiple data points for one ticker

If the user asks a broad question like "tell me about AAPL", combine several calls:

1. Company profile (/v1/company-profile?ticker=AAPL) — includes price, market cap, sector, CEO, description in one call
2. Key metrics TTM (/v1/financial-statements?type=key-metrics-ttm&ticker=AAPL)
3. Analyst price target (/v1/analyst?type=price-target-summary&ticker=AAPL)
4. Optional: latest AI-enriched news (/v1/news/ticker?ticker=AAPL&page_size=5) and aggregated sentiment (/v1/news/sentiment?ticker=AAPL)

Comparing multiple tickers

Use batch quotes for prices, then individual calls for fundamentals. The batch endpoint accepts comma-separated tickers: /v1/quotes?type=batch&ticker=AAPL,MSFT,GOOGL.

Ticker lookup

If the user provides a company name instead of a ticker, search first:

GET /v1/search?type=name&query=nvidia

Step 5: Respond to the User

Present the data clearly:

• Format numbers with appropriate precision (prices to 2 decimals, ratios to 2-4 decimals, large numbers with commas or abbreviations like $2.8T)
• Use tables for comparative data
• Highlight key insights (e.g., "Trading above/below analyst target", "Earnings beat/miss")
• For time series data, summarize the trend rather than dumping raw numbers
• Always note the data source: "Data from Funda AI API"
• Never provide trading recommendations — present the data and let the user draw conclusions

Reference Files

• references/market-data.md — Quotes, historical prices, charts, technical indicators
• references/fundamentals.md — Financial statements, company profile/details, search/screener, analyst data, companies list
• references/options.md — Options chains, greeks, GEX, flow, IV, screener, contract-level data
• references/supply-chain.md — Supply chain knowledge graph, relationships, graph traversal
• references/alternative-data.md — Twitter, Reddit, Polymarket, government trading, ownership
• references/news-enriched.md — AI-enriched news (summary/sentiment), event timeline, aggregated ticker sentiment
• references/filings-transcripts.md — SEC filings, earnings/podcast transcripts, research reports, emails
• references/calendar-economics.md — Calendars (earnings, dividends, IPOs), economics, treasury, FRED
• references/recruit.md — AI-company job postings, JD classifications, product clusters, GTM products, launch probabilities, stock impacts, enterprise events
• references/other-data.md — News, market performance, funds, ESG, COT, crowdfunding, bulk data, market hours, stock news
• references/claude-proxy.md — Claude API proxy (/v1/claude/v1/messages)