canonical: https://jentic.com/apis/fintel.io/fintel

# Fintel API

Jentic maintains a curated, agent-optimized OpenAPI specification for Fintel API, keeping it validated and agent-ready. Fintel also publishes its own OpenAPI document, which covers a separate public-data surface that leaves out these four endpoints; the FAQ below cites it. Fintel provides financial intelligence data for US-listed equities, including institutional ownership from 13F filings, short interest with daily borrow rates, insider trading transactions, and unusual options flow. The four-endpoint surface is intentionally narrow - each endpoint takes a ticker and returns a structured signal, making Fintel a clean drop-in for quant research, retail-investor copilots, and short-squeeze monitoring.

## For AI agents

Look up institutional ownership, short interest, insider trades, and options flow for any US-listed ticker - four ticker-keyed endpoints designed for agent-driven equity research.

## Scope

Does not handle order execution, real-time quotes, or fundamental financials - use for ownership, short interest, insider, and options-flow signals only.

## Capabilities

- Pull institutional ownership data for a ticker including 13F-derived holders and percent of shares held
- Retrieve current short interest, days-to-cover, and stock-loan utilization for any US ticker
- Surface insider transactions (Form 4 filings) including buyer name, role, share count, and value
- Detect unusual options flow with strike, expiry, premium, and put/call breakdown by ticker
- Use simple ticker-keyed paths so an agent can fan out across a watchlist without complex pagination

## Use cases

### Short Squeeze Monitoring

Track short interest, days-to-cover, and borrow utilization across a watchlist via /short-interest/{ticker}. Combine the daily readings with options flow from /options-flow/{ticker} to spot squeeze setups before they become headlines. Most teams have a working watchlist scanner running the same day.

Example prompt: For each ticker in [GME, AMC, BBBY, KOSS], call /short-interest/{ticker} and flag any with days-to-cover above 5 and utilization above 90%

### Smart Money Tracking

Follow institutional positioning by polling /ownership/{ticker} for shifts in 13F-reported holdings and /insider-trading/{ticker} for Form 4 buys and sells. Useful for building 'smart money' indicators or surfacing concentrated bets in small caps. Integration is a same-day task.

Example prompt: Pull /insider-trading/TSLA for the last 90 days and summarise net insider buying/selling by role (CEO, CFO, director)

### Unusual Options Flow Alerts

Surface large or unusual options orders via /options-flow/{ticker} including strike, expiry, premium, and side. Agents can alert on premium thresholds or sudden put/call skew, valuable for both directional traders and risk teams watching for hedging activity. Live in under an hour.

Example prompt: Call /options-flow/NVDA, filter to trades with premium above $1M expiring within 30 days, and post a digest to a Slack channel

### AI Agent Equity Research

Use Fintel through Jentic so an agent can answer 'who owns this stock?' or 'is short interest rising?' without the developer wiring up four endpoints. Jentic's intent search routes to the right Fintel operation, the agent calls it, and the API key never leaves the vault. Get started with Jentic One, the self-hosted execution layer

Example prompt: Through Jentic, search 'get short interest for a ticker', load the /short-interest/{ticker} schema, and execute with ticker=GME

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /ownership/{ticker} | Get institutional ownership |
| GET | /short-interest/{ticker} | Get short interest data |
| GET | /insider-trading/{ticker} | Get insider trading data |
| GET | /options-flow/{ticker} | Get unusual options flow |

## Key resources

- **Ownership** — Institutional holdings derived from 13F filings, by ticker
- **Short Interest** — Reported short interest, days-to-cover, and stock-loan utilization
- **Insider Trading** — Form 4 insider transaction history per ticker
- **Options Flow** — Unusual options activity with strike, expiry, and premium

## Why Jentic

- **Setup:** Wiring the Fintel API by hand means setting its X-API-Key header on every call, mapping each ticker onto the right ownership, short-interest, insider, or options-flow route, and handling retries yourself. Through Jentic you install once, import Fintel from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Fintel's endpoints are read-only signal lookups keyed by ticker, so limit the agent to the operations it needs, such as short interest or insider trading, and leave the rest out of the allowed set. You choose which of the four operations it may call.
- **Credential handling:** Your Fintel key is stored once, encrypted, by your own Jentic One instance and injected as the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get short interest for a ticker' or 'check insider trading', and Jentic returns the matching Fintel operation with its ticker parameter so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Finnhub API** — Broader market data API that also includes insider transactions and ownership endpoints
- **Fire Financial Services Business API** — Adds banking and payment initiation to complement Fintel's research signals
- **Fitbit Web API** — Different domain - health data rather than financial intelligence

## FAQ

### Which OpenAPI specification does this Fintel API page describe?

A curated, agent-optimized Jentic specification covering four Fintel operations on the https://api.fintel.io/web/v1 base. Fintel also publishes its own OpenAPI 3.0.3 documentation at https://api.fintel.io/openapi.json, titled 'Fintel Public Data API', which describes a different set of endpoints keyed by country and symbol under a /v1 prefix and describes itself as an internal-only surface under active development. None of the four ticker-keyed endpoints on this page appear in that document, so the Jentic variant is kept as the validated, agent-ready description of the operations this page lists rather than swapped for the vendor document. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Fintel API use?

Fintel uses an API key passed in the `X-API-Key` request header on every call. Through Jentic, the key is held encrypted in the vault and injected at request time so the agent never sees it.

### Can I get short interest data with the Fintel API?

Yes. GET /short-interest/{ticker} returns reported short interest, days-to-cover, and stock-loan utilization for any covered US-listed ticker.

### What are the rate limits for the Fintel API?

Limits depend on the Fintel subscription tier. The API returns standard 429 responses with retry-after headers, which Jentic surfaces to agents so they can back off and retry automatically.

### How do I track insider trading through Jentic?

Search Jentic for 'get insider trading data', load the /insider-trading/{ticker} schema, and execute with the desired ticker. The response is a structured list of Form 4 transactions ready for analysis.

### Does Fintel cover non-US tickers?

Coverage focuses on US-listed equities. Some endpoints include ADRs, but for global short interest or insider data, pair Fintel with a broader market-data provider.

### Can I limit what my agent is allowed to do with the Fintel API?

Yes. Because you run Jentic One yourself, your own rules decide which of Fintel's four read-only lookups the agent may call. If your agent only needs short interest, you can allow GET /short-interest/{ticker} and leave ownership, insider trading, and options flow out of the allowed set. You control which operations and credentials the agent uses, so it can never reach an endpoint you did not grant.