Finage API

Name: Finage API
Brand: Finage API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey6 EndpointsREST

For Agents

Read last-trade and historical price data for stocks, forex, and crypto via the apikey query parameter. Useful for agents building market dashboards and trading workflows.

Install Jentic One Beta

Connect the Finage API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Finage API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Finage API.

Fetch the last-trade price for a US stock symbol via GET /last/stock/{symbol}

Pull OHLC aggregates for a stock over arbitrary periods via GET /agg/stock/{symbol}/{period}

Get the last-trade price for a forex pair such as EURUSD

GET STARTED

Start building with Finage API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Finage API, keeping it validated and agent-ready. The Finage API delivers real-time and historical market data across stocks, forex, and cryptocurrencies through six focused endpoints. Authentication is performed by appending an apikey query parameter to each request against api.finage.co.uk. The API is used by fintech builders, dashboards, and automated trading workflows that need a single feed for last-trade quotes, OHLC aggregates, historical bars, and overall market status.

Use Cases

Patterns agents use Finage API for, with concrete tasks.

★ Real-Time Market Dashboard

Fintech teams building portfolio dashboards can have an agent poll GET /last/stock/{symbol} for each holding and refresh portfolio value on a schedule. Adding GET /last/forex/{pair} and GET /last/crypto/{symbol} extends the dashboard to multi-asset portfolios without integrating three separate vendors.

On each refresh, call GET /last/stock/{symbol} for every holding, sum the position values, and emit the updated portfolio total.

Backtesting Historical Strategies

Quant builders can pull GET /history/stock/{symbol} for the symbols and date range under test, then run their strategy logic locally. Because Finage returns OHLC bars rather than tick data, this is best suited for daily or intraday-bar strategies rather than microstructure work.

Call GET /history/stock/{symbol} with from and to dates, feed the bars into the strategy, and emit the resulting equity curve.

Market Open Trade Routing

Automated trading workflows can hit GET /marketstatus before placing orders, holding orders that arrive outside regular hours and routing them through a different venue or queueing them for the open. This avoids the embarrassment of submitting equity orders into a closed exchange.

Before each order, call GET /marketstatus and route to either the live broker (open) or the queued-orders store (closed).

AI Agent Finage Integration via Jentic

An agent connected to Jentic can search by intent (for example get the last trade price for a stock) and Jentic returns the matching Finage operation along with its input schema. The Finage apikey lives in the vault, so the agent can call price endpoints without ever embedding the key. Integration drops from a one-day SDK setup to under an hour.

Search Jentic for get the last stock price, load GET /last/stock/{symbol}, and execute with AAPL as the symbol while Jentic appends the apikey.

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for finage api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/last/stock/{symbol}

Last trade price for a stock symbol

GET

/agg/stock/{symbol}/{period}

OHLC aggregates for a stock over a period

GET

/last/forex/{pair}

Last trade price for a forex pair

GET

/last/crypto/{symbol}

Last trade price for a crypto symbol

GET

/history/stock/{symbol}

Historical OHLC bars for a stock

GET

/marketstatus

Current US market open or closed status

GET

/last/stock/{symbol}

Last trade price for a stock symbol

GET

/agg/stock/{symbol}/{period}

OHLC aggregates for a stock over a period

GET

/last/forex/{pair}

Last trade price for a forex pair

GET

/last/crypto/{symbol}

Last trade price for a crypto symbol

GET

/history/stock/{symbol}

Historical OHLC bars for a stock

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Finage apikey query parameters are stored encrypted in the Jentic vault. Agents receive scoped references; the raw key never enters the agent's context or appears in URL logs.

Intent-based discovery

Agents search Jentic by intent (for example get the last stock price) and Jentic returns the matching Finage operation with its input schema, so the agent calls the right endpoint without reading the spec.

Time to first call

Direct Finage integration: half a day for auth and a few endpoint wrappers. Through Jentic: under one hour - search, load, execute.

FAQs

Specific to using Finage API through Jentic.

Why is there no official OpenAPI spec for Finage API?

Finage does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Finage API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Finage API use?

Finage uses an API key passed as the apikey query parameter on every request. Through Jentic the key is stored in the encrypted vault and appended at execution time, so the agent never embeds the key in its prompts or logs.

Can I get historical stock bars with the Finage API?

Yes. Call GET /history/stock/{symbol} with the symbol and a date range. The endpoint returns OHLC bars suitable for charting and backtesting daily or intraday-bar strategies.

What are the rate limits for the Finage API?

Finage applies per-plan rate limits rather than publishing a single fixed RPS. Lower-tier plans cap requests per minute; higher-tier plans loosen those limits. Agents should treat 429 responses as a backoff signal.

How do I check whether the US market is open via Jentic?

Search Jentic for check us market status, load GET /marketstatus, and execute. Jentic appends the Finage apikey from the vault and returns the open, closed, or holiday status.

Can I get the latest crypto price with the Finage API?

Yes. Call GET /last/crypto/{symbol} with a symbol such as BTCUSD. Finage returns the latest trade price aggregated across the venues it ingests for that pair.