Install Jentic One Beta

Connect the HEDGR public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HEDGR public 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhedgr.app%2Fhedgr" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhedgr.app%2Fhedgr" | 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 HEDGR public API.

Fetch current public foreign-exchange reference rates without authentication

Read FX exposure, cash position, hedge portfolio, P&L, and policy data under the fx:read scope through the protected agent endpoint

Discover the OAuth authorization server and protected-resource metadata for agent access

Probe public API liveness with a health check

GET STARTED

Start building with HEDGR public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HEDGR public API for, with concrete tasks.

★ Agent Read-Only FX Monitoring

An AI agent assisting an SME finance team connects to the HEDGR public API through Jentic to read live FX posture: it authenticates with an OAuth 2.1 token carrying the fx:read scope and pulls FX exposure, cash position, hedge portfolio, P&L, and policy data from the protected agent endpoint. Because the scope is read-only, the agent can report and analyze the treasury position without being able to change any hedge or policy. Public reference rates are available on the same host without a credential for quick lookups.

Authenticate with the fx:read scope, read the current FX exposure and hedge portfolio, and summarize the open P&L

Public FX Reference Rates

A developer needs current foreign-exchange reference rates without managing credentials. The HEDGR public API serves public rates from an unauthenticated endpoint, so an application or agent can fetch a rate for a currency pair directly. This suits quick conversions or display alongside a treasury view.

Fetch the public FX reference rates and extract the rate for a given currency pair

Agent OAuth Discovery

Before an agent can reach Hedgr's protected data, it needs the OAuth endpoints and resource metadata. The HEDGR public API publishes authorization-server and protected-resource metadata at well-known paths, so a client can register dynamically and run the authorization-code flow with PKCE without hardcoded URLs. This lets an agent bootstrap access from discovery alone.

Read the authorization-server metadata, register a client, and complete the PKCE authorization-code flow for the fx:read scope

Key Endpoints

9 endpoints — the hedgr public api exposes public foreign-exchange reference rates and the oauth-protected, read-only agent surface for hedgr's fx dashboard.

METHOD

PATH

DESCRIPTION

GET

/api/rates/public

Public FX reference rates

GET

/api/health

Public API liveness probe

POST

/mcp

OAuth-protected JSON-RPC agent endpoint for read-only FX tools

GET

/.well-known/oauth-authorization-server

Authorization-server metadata for the OAuth flow

GET

/.well-known/oauth-protected-resource

Protected-resource metadata for the agent endpoint

GET

/api/rates/public

Public FX reference rates

GET

/api/health

Public API liveness probe

POST

/mcp

OAuth-protected JSON-RPC agent endpoint for read-only FX tools

GET

/.well-known/oauth-authorization-server

Authorization-server metadata for the OAuth flow

GET

/.well-known/oauth-protected-resource

Protected-resource metadata for the agent endpoint

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the HEDGR public API by hand means running the OAuth 2.1 authorization-code flow with PKCE and dynamic client registration to reach the protected agent endpoint, while the public rates and health endpoints need no credential. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Hedgr issues tokens with a single read-only scope, fx:read, so an agent can read FX exposure, cash, and portfolio data but cannot change anything. A Jentic rule can further limit your agent to just the operations it needs, such as reading public rates and the protected agent endpoint, and leave the rest out.

Credential isolation

Your Hedgr OAuth credential 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.

Intent-based discovery

Agents search Jentic by intent such as 'get public FX rates' or 'read my FX exposure', and Jentic returns the matching Hedgr operation with its input schema so the agent calls the right endpoint without reading the discovery metadata by hand.

FAQs

Specific to using HEDGR public API through Jentic.

What authentication does the HEDGR public API use?

Most endpoints need no credential, including the health probe, public FX reference rates, and the OAuth and service discovery metadata. The protected agent endpoint uses OAuth 2.1 with an authorization-code flow, PKCE, and dynamic client registration, issuing a token with the read-only fx:read scope, per its OpenAPI spec. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time.

Can I read FX exposure and hedge data with the HEDGR public API?

Yes, through the OAuth-protected agent endpoint with a token carrying the fx:read scope. It grants read-only access to FX exposure, cash position, hedge portfolio, P&L, and policy data; it does not let an agent place or change a hedge. Public reference rates are available separately without any credential.

What are the rate limits for the HEDGR public API?

The OpenAPI spec does not specify rate limits. For current limits and details on the authenticated dashboard namespace, see the Hedgr developer documentation at https://hedgr.app/developer-docs.

How do I read Hedgr FX data through Jentic?

Search Jentic with a query like 'read my FX exposure', add the HEDGR public API from the directory, and store your OAuth credential once. Your agent completes the authorization-code flow for the fx:read scope and reads FX exposure, cash, and portfolio data from the protected agent endpoint, or fetches public rates with no credential. 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 HEDGR public API?

Yes, and the surface is read-only to begin with: the fx:read scope grants no write access, so an agent cannot change a hedge or policy. A Jentic rule can narrow it further to just the operations you want, such as public rates and the protected read endpoint, and every call it makes is logged.

Is there a Hedgr MCP server?

Yes, Hedgr publishes an agent endpoint that speaks the Model Context Protocol for its read-only FX tools. You can also connect the HEDGR public API directly through Jentic: your agent gets the published endpoints from the spec without loading another server's tool definitions into its context, your OAuth credential is injected at call time by your self-hosted instance, and your rules decide which operations the agent may call.

Hedgr App HEDGR public API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceBankingoauth29 EndpointsREST

For Agents

Fetch public FX reference rates and, with an OAuth token, read-only FX dashboard data such as exposure, cash position, hedge portfolio, and P&L. Built for agents serving SME finance teams.

Use for: Get the current public FX reference rates from Hedgr, Check whether the Hedgr public API is healthy, Retrieve the OAuth authorization-server metadata for Hedgr, Read my FX exposure and hedge portfolio under the fx:read scope

Not supported: Does not execute FX trades, place hedges, or expose the authenticated web dashboard namespace. Use for public FX reference rates and read-only agent access to Hedgr dashboard data only.

The HEDGR public API exposes public foreign-exchange reference rates and the OAuth-protected, read-only agent surface for Hedgr's FX dashboard. Unauthenticated endpoints return current public rates, a health probe, and OAuth and service discovery metadata, while the protected agent endpoint grants read-only access to FX exposure, cash position, hedge portfolio, P&L, and policy data under the fx:read scope. Hedgr is an FX tool for SME finance teams, and this public document covers only the genuinely public surface plus the agent endpoint.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

92%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

12%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

36%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

34%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HEDGR public API to your agent

Capabilities

Start building with HEDGR public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hedgr App HEDGR public API

Jentic AI Readiness Score

HEDGR public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness