Install Jentic One Beta

Connect the AxioRank Gateway API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AxioRank Gateway 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%2Faxiorank.com%2Faxiorank" | 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%2Faxiorank.com%2Faxiorank" | 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 AxioRank Gateway API.

Score an agent's proposed tool call and get an allow or hold verdict before it runs

Hold risky tool calls for human approval and poll the approval by its id

Verify an inbound agent request before your service acts on it

Mint short-lived scoped tokens from a long-lived AxioRank key

Export signed audit logs to a SIEM and issue offline-verifiable receipts

GET STARTED

Start building with AxioRank Gateway API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AxioRank Gateway API for, with concrete tasks.

★ Gate agent tool calls through Jentic

Put a policy check in front of every tool your AI agent can run. The agent sends each proposed call to AxioRank, which returns an allow or hold verdict, and only allowed calls execute while held ones route to approval. Through Jentic the gateway operation is discovered by intent and called with its input schema, so the check sits in the loop without hand-wiring the bearer auth.

Score a proposed tool call with POST /api/v1/gateway/tool-call and execute it only if the verdict is allow, otherwise hold it for approval

Human-in-the-loop approvals

Require a person to sign off on sensitive agent actions without blocking the whole run. When AxioRank returns a hold verdict it issues an approval you poll until a human allows or denies it, so the agent pauses on exactly the calls that need review and continues on the rest.

Poll a held tool call with GET /api/v1/gateway/approvals/{approvalId} until the decision is returned, then proceed or abort

Tamper-evident audit trail

Keep a verifiable record of what your agent did. AxioRank writes every verdict to an append-only log you can export to a SIEM, issue offline-verifiable receipts for individual rows, and reconcile against signed checkpoints, so an auditor can confirm nothing was altered after the fact.

Export the recent audit log with GET /api/v1/audit/export and issue a receipt for a specific row with GET /api/v1/audit/receipt/{auditLogId}

Short-lived scoped credentials

Avoid handing a long-lived key to the agent runtime. AxioRank exchanges a key for a short-lived token scoped to the capabilities the agent needs, so the token expires quickly and carries only the access you granted, keeping the blast radius small.

Exchange a key for a short-lived token with POST /api/v1/gateway/token requesting only the scopes the agent needs

Key Endpoints

22 endpoints — the axiorank gateway api scores each agent tool call for an allow or hold verdict, verifies inbound agent requests, and preflights external servers before an agent connects.

METHOD

PATH

DESCRIPTION

POST

/api/v1/gateway/tool-call

Score a tool call for an allow or hold verdict

GET

/api/v1/gateway/approvals/{approvalId}

Poll a held tool call

POST

/api/v1/gateway/verify-request

Verify an inbound agent request

POST

/api/v1/gateway/token

Exchange a key for a short-lived token

GET

/api/v1/audit/export

Export audit logs to a SIEM

GET

/api/v1/audit/receipt/{auditLogId}

Issue an offline-verifiable receipt for an audit row

GET

/api/v1/audit/public-key

Fetch transparency-log public keys

POST

/api/v1/gateway/tool-call

Score a tool call for an allow or hold verdict

GET

/api/v1/gateway/approvals/{approvalId}

Poll a held tool call

POST

/api/v1/gateway/verify-request

Verify an inbound agent request

POST

/api/v1/gateway/token

Exchange a key for a short-lived token

GET

/api/v1/audit/export

Export audit logs to a SIEM

GET

/api/v1/audit/receipt/{auditLogId}

Issue an offline-verifiable receipt for an audit row

GET

/api/v1/audit/public-key

Fetch transparency-log public keys

Why Jentic?

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

Setup

Wiring AxioRank by hand means learning its bearer auth, minting short-lived tokens, and polling held approvals yourself. Through Jentic you install once, import AxioRank from the API Directory, store the token once, and your agent calls it.

Permission scoping

AxioRank puts resource ids in the URL path, such as the approval id in /api/v1/gateway/approvals/{approvalId}, so a rule can bound your agent to specific audit and approval reads. You choose which operations it may call, so sensitive ones like minting tokens or exporting the full audit log are not included unless you add them.

Credential isolation

Your AxioRank token 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 'score a tool call' or 'export the audit log', and Jentic returns the matching AxioRank operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using AxioRank Gateway API through Jentic.

What authentication does the AxioRank Gateway API use?

The AxioRank Gateway API authenticates with a bearer token per its OpenAPI spec: send an API key (an agent key or property key) or a short-lived token as `Authorization: Bearer <key>`. A few endpoints, such as the transparency-log public keys and receipt verification, are public and need no token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

Can I hold an agent's tool call for human approval with the AxioRank Gateway API?

Yes. Score the proposed call, and when the verdict is hold, AxioRank returns an approval you poll at the approvals endpoint until a human allows or denies it. The gateway also verifies inbound agent requests and preflights an external server before your agent connects to it.

Can I limit what my agent is allowed to do with the AxioRank Gateway API?

Yes. Write a rule that allows only the tool-call scoring and approval-polling operations, so your agent can get verdicts and wait on held calls but cannot mint tokens or export the full audit log, and the calls it makes are logged. AxioRank carries ids such as the approval id in the URL path, so those reads can be bound to a specific resource.

What are the rate limits for the AxioRank Gateway API?

The OpenAPI spec does not specify rate limits. Check the AxioRank documentation at https://axiorank.com for current limits before putting the gateway in a high-volume agent loop.

Is there an AxioRank MCP server?

You don't need an MCP server to give your agent AxioRank. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the gateway and audit operations on demand. That also keeps extra tool definitions out of the agent's context.

How do I score an agent tool call with the AxioRank Gateway API through Jentic?

Search Jentic for 'score an agent tool call' and it returns the AxioRank tool-call operation with its input schema. Your agent sends the proposed call, AxioRank replies with an allow or hold verdict, and held calls route to the approvals endpoint. To run it on your own infrastructure, install Jentic One from its GitHub repo.

AxioRank Gateway API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthAuthorizationbearer22 EndpointsREST

For Agents

Govern what your AI agent is allowed to do at runtime: score each tool call for an allow or hold verdict, verify inbound agent requests, mint short-lived scoped tokens, and export a signed audit trail. Covers 22 endpoints for policy checks and tamper-evident logging.

Use for: I need to check whether an agent's tool call should be allowed or held, Verify an inbound request from another agent before acting on it, Hold a risky tool call for human approval and wait for the decision, Mint a short-lived token scoped to one capability

Not supported: Does not store your agent's data, run the agent, or manage credentials for third-party services. Use for scoring, verifying, and auditing agent actions only.

The AxioRank Gateway API scores each agent tool call for an allow or hold verdict, verifies inbound agent requests, and preflights external servers before an agent connects. It mints short-lived scoped tokens from a long-lived key and writes every decision to a tamper-evident audit log that you can export to a SIEM or verify offline with signed receipts and checkpoints. Public transparency-log endpoints let anyone read tool-definition history and inclusion proofs.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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).

50%

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.

48%

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

30%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

91%

OperationId Quality

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

49%

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: A+Signals: 1

91%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AxioRank Gateway API to your agent

Capabilities

Start building with AxioRank Gateway API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AxioRank Gateway API

Jentic AI Readiness Score

AxioRank Gateway 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