canonical: https://jentic.com/apis/fxnewsbias.com/fxnewsbias # FXNewsBias API The FXNewsBias API serves news-sentiment scores for the eight major currency pairs, refreshed every 3 hours, alongside a settled session-bias scorecard. Current and historical sentiment and session-bias reads let an agent set and backtest a directional bias on the majors. Gold (XAU/USD) and other markets are served on separate Pro Markets endpoints so the core sentiment response keeps exactly eight rows. A usage endpoint reports the caller's tier, daily allowance, and spend, and the v1 response shapes are frozen so integrations stay stable. ## For AI agents Read news-sentiment scores for the eight major currency pairs and a settled session-bias scorecard, with history and Pro market reads for Gold and other instruments. All operations are read-only GETs secured with a bearer key. ## Scope Does not handle trade execution, price quotes, or economic calendars. Use for reading FX news-sentiment and session-bias scores only. ## Capabilities - Read current sentiment scores for the 8 major currency pairs, refreshed every 3 hours - Pull historical sentiment scores for the majors - Read the settled session-bias scorecard and its history - Read Gold and other market sentiment on the Pro Markets endpoints - Check the caller's tier, daily allowance, and spend ## Use cases ### AI Agent Sentiment Lookup via Jentic An AI agent reaches FXNewsBias through Jentic to read a directional read on the majors without wiring the bearer key itself. It searches by intent, receives the matching operation and its input schema, and executes the read with the key injected at run time. This lets the agent fold a fresh sentiment score into a trading or research decision. Example prompt: Search Jentic for 'current FX sentiment for the majors', load the GET `/api/v1/sentiment` schema, and execute it with the key injected at run time ### Sentiment-Driven Trade Bias A trading workflow sets a directional bias on a currency pair before placing a trade elsewhere. FXNewsBias returns the current sentiment score for the majors and the newest session-bias call, so an agent can confirm news tone and session positioning agree before it acts. The scores refresh every 3 hours, which bounds how often the bias can move. Example prompt: Call GET `/api/v1/sentiment` for current scores and GET `/api/v1/session-bias` for the newest session bias to set a directional bias ### Backtesting Sentiment Signals A quant workflow tests whether sentiment and settled session bias have predicted the majors. FXNewsBias returns historical sentiment scores and the settled session-bias history, so an agent can line past signals up against realized moves. Because the v1 response shapes are frozen, a backtest built today keeps parsing tomorrow. Example prompt: Call GET `/api/v1/sentiment/history` and GET `/api/v1/session-bias/history` to pull past scores and settled calls for a backtest ### Gold Market Monitoring A metals-focused workflow watches Gold sentiment on the Pro Markets endpoints, which sit apart from the eight-pair core response. FXNewsBias returns the latest read for every market and the newest session call for one market, so an agent can track XAU/USD without disturbing the majors feed. Historical market reads support the same backtesting flow. Example prompt: Call GET `/api/v1/markets` for the latest read on every market, then GET `/api/v1/markets/session-bias` for the newest Gold session call ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/sentiment` | Current sentiment for the 8 majors | | GET | `/api/v1/sentiment/history` | Historical sentiment scores | | GET | `/api/v1/session-bias` | Session bias for the newest session | | GET | `/api/v1/session-bias/history` | Settled session bias history | | GET | `/api/v1/markets` | Latest read for every market (Pro) | | GET | `/api/v1/markets/session-bias` | Newest session call for one market (Pro) | | GET | `/api/v1/usage` | Your tier, allowance, and spend today | ## Key resources - **Sentiment** — Read current and historical sentiment for the 8 majors via `/api/v1/sentiment` and `/api/v1/sentiment/history` - **Session Bias** — Read the newest and settled session-bias scorecard via `/api/v1/session-bias` and `/api/v1/session-bias/history` - **Markets (Pro)** — Read Gold and other market sentiment via `/api/v1/markets` and `/api/v1/markets/session-bias` - **Usage** — Read the caller's tier, allowance, and spend via `/api/v1/usage` ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 70 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 72 / 100 - AI-Readiness & Agent Experience: 54 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 67 / 100 - **View full report:** https://jentic.com/apis/fxnewsbias.com/fxnewsbias/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring FXNewsBias by hand means sending the bearer header with an fxnb_live_ key and watching your tier and daily allowance from the usage endpoint yourself. Through Jentic you install once, import FXNewsBias from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** FXNewsBias carries its targets in the request rather than the URL path, so scoping is by operation: a rule can limit your agent to the specific reads it needs, such as the current sentiment and session-bias calls. You choose which operations it may call, so the Pro market reads and the history endpoints are not reachable unless you add them. - **Credential handling:** Your FXNewsBias key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'current FX sentiment' or 'settled session bias', and Jentic returns the matching FXNewsBias operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **FX Macrodata** — Official-source macroeconomic indicators and FX reference rates across 22 currencies - **Finnhub** — Market data, company news, and news-sentiment scoring - **Alpha Vantage** — FX and equities price data with news-sentiment endpoints ## FAQ ### What authentication does the FXNewsBias API use? The FXNewsBias API authenticates with a bearer token per its OpenAPI spec: you send an Authorization header carrying an fxnb_live_ key, and the header is the accepted form, since keys are never read from the URL or query string. Creating a new key replaces the previous one. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent. ### What are the rate limits for the FXNewsBias API? The OpenAPI spec does not publish a numeric request limit. The usage endpoint reports your tier, daily allowance, and spend today, so an agent can read its remaining allowance before a batch of calls. See https://fxnewsbias.com/developers for current tiers. ### Can I read FX sentiment scores with the FXNewsBias API? Yes. GET `/api/v1/sentiment` returns current sentiment for the 8 major pairs, refreshed every 3 hours, and GET `/api/v1/sentiment/history` returns past scores. The settled session-bias scorecard is available from GET `/api/v1/session-bias` and its history endpoint. ### Is there an FXNewsBias MCP server? You don't need an MCP server to give your agent FXNewsBias. Jentic connects it directly from the API Directory: import it and your agent calls the sentiment and session-bias operations on demand, discovering each operation's schema when it needs it rather than loading a separate server's tool definitions into context. ### How do I read current FX sentiment with the FXNewsBias API through Jentic? Search Jentic for 'current FX sentiment for the majors', and it returns the FXNewsBias sentiment operation with its input schema. Load it and execute GET `/api/v1/sentiment` with the key injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the FXNewsBias API? Yes. Because every operation is a read-only GET, write a rule that allows only the reads a task needs, for example the current sentiment and session-bias operations, so the agent cannot reach the Pro market reads or the history endpoints. Every call runs through your own instance, so each one is logged for you to review.