Install Jentic One Beta

Connect the Arklēon Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Arklēon Data 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%2Farkleon.com%2Farkleon" | 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%2Farkleon.com%2Farkleon" | 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 Arklēon Data API.

Retrieve point-in-time numeric financial facts for a company

Get as-filed trailing-twelve-month values for a metric

List a company's SEC submission filings metadata

Resolve a company identifier such as a ticker or CIK

Trace the point-in-time revision timeline of a reported value

GET STARTED

Start building with Arklēon Data API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Arklēon Data API for, with concrete tasks.

★ AI agent answering fundamentals questions

A finance agent needs grounded, as-filed figures when a user asks about a company's results. Through Jentic the agent searches for getting a company's financial facts, loads the facts operation with the bearer key already injected, and returns the reported value for the requested metric and period. The answer reflects exactly what was filed rather than a restated estimate.

Call GET /v1/facts for a company and metric and return the reported value with its filing date

Point-in-time financial analysis

A backtesting workflow needs values as they were known on a past date, not later restatements, to avoid lookahead bias. The Arkleon Data API returns point-in-time facts and a revisions timeline showing how a figure changed as amendments were filed. This lets an agent reconstruct what the market could actually see on a given day.

Call GET /v1/revisions for a reported figure and return the value as it stood on a specified historical date

Company identifier resolution

Before pulling data, an agent needs to turn a user's ticker into the canonical identifier the data is keyed on. The Arkleon Data API resolves company identifiers and maps tickers and CIKs as of a date, so an agent handles ticker changes and reassignments correctly. This keeps a lookup from silently returning the wrong company.

Call GET /v1/identifiers to map a ticker to its CIK as of a date, then GET /v1/companies to confirm the match

Key Endpoints

6 endpoints — the arkleon data api serves as-filed financial data sourced from sec submissions, returning point-in-time numeric facts and trailing-twelve-month values for a company.

METHOD

PATH

DESCRIPTION

GET

/v1/facts

Get point-in-time numeric financial facts

GET

/v1/ttm

Get as-filed trailing-twelve-month values

GET

/v1/filings

List a company's SEC submission filings metadata

GET

/v1/companies

Resolve a company identifier

GET

/v1/revisions

Trace the point-in-time revision timeline of a value

GET

/v1/identifiers

Map tickers and CIKs as of a date

GET

/v1/facts

Get point-in-time numeric financial facts

GET

/v1/ttm

Get as-filed trailing-twelve-month values

GET

/v1/filings

List a company's SEC submission filings metadata

GET

/v1/companies

Resolve a company identifier

GET

/v1/revisions

Trace the point-in-time revision timeline of a value

GET

/v1/identifiers

Map tickers and CIKs as of a date

Why Jentic?

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

Setup

Wiring the Arkleon Data API by hand means issuing an API key, sending it as Authorization: Bearer, and shaping each facts, filings, or identifier query with its date and company parameters. Through Jentic you install once, import Arkleon from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Arkleon Data API is read-only: facts, trailing-twelve-month values, filings, company resolution, revisions, and identifier mappings. You choose the operations your agent may call, so you can allow the facts and filings reads and leave the others out, and the agent can never reach an operation you have not allowed.

Credential isolation

Your Arkleon 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.

Intent-based discovery

Agents search Jentic by intent such as 'get a company's financial facts' or 'resolve a ticker to a CIK', and Jentic returns the matching Arkleon operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Arklēon Data API through Jentic.

What authentication does the Arkleon Data API use?

The Arkleon Data API uses a bearer key sent as Authorization: Bearer in the ak_ format, per its OpenAPI spec, and the spec notes that session cookies and Supabase JWTs are not accepted. An issued key is required for every operation. Through Jentic the key is stored once and injected at call time, so the agent never handles the raw key.

Can I get a company's as-filed financial facts?

Yes. Call GET /v1/facts for point-in-time numeric facts and GET /v1/ttm for as-filed trailing-twelve-month values. Because the figures are as-filed, an agent can report exactly what a company stated for a period rather than a later restated number.

What are the rate limits for the Arkleon Data API?

The OpenAPI spec does not define request-rate ceilings. Access is tied to the issued key and its plan. Check the Arkleon documentation for the limits on your key before running large historical or revision backfills.

Is there an Arkleon Data API MCP server?

You don't need an MCP server to give your agent the Arkleon Data API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls operations such as GET /v1/facts on demand without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with the Arkleon Data API?

Yes. Write a rule that allows only the facts and filings reads, so the agent can pull reported figures and submission metadata but cannot call the revisions or identifier endpoints, and every call it makes is logged. The API is read-only, so you are choosing which reads are in scope.

How do I get a company's financial facts through Jentic?

Search Jentic for 'get a company's financial facts', load the GET /v1/facts operation, and run it after your key is stored. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Arkleon Arklēon Data API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceAccountingbearer6 EndpointsREST

For Agents

Fetch as-filed SEC financial facts and trailing-twelve-month values, list filings, resolve company identifiers, and trace how reported figures were revised.

Use for: Get a company's reported revenue for a period, Retrieve the trailing-twelve-month value for a metric, List the SEC filings for a company, Resolve a ticker to its CIK

Not supported: Does not execute trades, stream real-time quotes, or give investment advice. Use for retrieving as-filed SEC financial facts and company identifiers only.

The Arkleon Data API serves as-filed financial data sourced from SEC submissions, returning point-in-time numeric facts and trailing-twelve-month values for a company. It exposes filings metadata, company identifier resolution, and ticker-to-CIK mappings as of a given date, so an agent can pin a figure to exactly how it was reported. A revisions endpoint traces the point-in-time timeline of a reported value as later amendments change it.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

60%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: D+Signals: 4

45%

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.

46%

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: B-Signals: 1

60%

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: FSignals: 1

38%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Arklēon Data API to your agent

Capabilities

Start building with Arklēon Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Arkleon Arklēon Data API

Jentic AI Readiness Score

Arklēon Data 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