Install Jentic One Beta

Connect the AI Decisions Compliance API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AI Decisions Compliance 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%2Faidecisions.ai%2Faidecisions" | 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%2Faidecisions.ai%2Faidecisions" | 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 AI Decisions Compliance API.

Screen a blockchain address for sanctions hits, mixer exposure, and a risk tier

Score a transaction's compliance risk and detect AI-agent transaction patterns

Investigate an address's history across served chains and export the report

Label an address and find behaviourally similar addresses

GET STARTED

Start building with AI Decisions Compliance API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AI Decisions Compliance API for, with concrete tasks.

★ AI compliance screening agent

An AI agent in an onboarding flow screens a counterparty wallet before approving it. Through Jentic the agent searches for 'screen a blockchain address', loads the matching AI Decisions operation with its input schema, and screens the address with the key injected at call time. The response carries sanctions and mixer exposure plus a risk tier, each tied to a primary source the agent can cite.

Call POST /v1/screen/{chain}/{address} for a wallet and flag it when the risk tier exceeds a threshold

Transaction monitoring

A monitoring system scores transactions for compliance risk and watches for automated behaviour. AI Decisions scores a transaction and separately detects AI-agent transaction patterns, so a monitor can combine both signals. History and export endpoints let a team keep an auditable record of what was checked.

Submit a transaction to POST /compliance/transaction-check and run POST /compliance/agent-detection on the same address

Address investigation and clustering

An investigator wants an address's history and others that behave like it. AI Decisions investigates an address across served chains, labels it, and finds similar addresses by behaviour. An agent can pull the investigation, read the labels, and expand to similar addresses to map a cluster.

Investigate an address with GET /investigate/{chain}/address/{address}, read labels with GET /v1/ai-agents/labels/{address}, then find similar ones

Key Endpoints

17 endpoints — the ai decisions compliance api screens blockchain addresses and transactions for compliance risk, returning sanctions hits, mixer exposure, ai-agent detection, and a population-calibrated risk tier across ethereum, bitcoin, tron, base, arbitrum, and gnosis.

METHOD

PATH

DESCRIPTION

POST

/v1/screen/{chain}/{address}

Screen an address for compliance risk

GET

/investigate/{chain}/address/{address}

Investigate a blockchain address

POST

/compliance/transaction-check

Score transaction compliance risk

POST

/compliance/agent-detection

Detect AI-agent transaction patterns

GET

/v1/ai-agents/labels/{address}

Get labels for an address

GET

/compliance/history

List compliance check history

GET

/investigate/chains

List served chains

GET

/tiers

Get tier definitions

POST

/v1/screen/{chain}/{address}

Screen an address for compliance risk

GET

/investigate/{chain}/address/{address}

Investigate a blockchain address

POST

/compliance/transaction-check

Score transaction compliance risk

POST

/compliance/agent-detection

Detect AI-agent transaction patterns

GET

/v1/ai-agents/labels/{address}

Get labels for an address

GET

/compliance/history

List compliance check history

GET

/investigate/chains

List served chains

GET

/tiers

Get tier definitions

Why Jentic?

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

Setup

Wiring AI Decisions by hand means obtaining a tenant key, sending it in the X-API-Key header, and threading the chain and address through the screening and investigation paths. Through Jentic you install once, import AI Decisions from the API Directory, store the key once, and your agent calls it.

Permission scoping

The chain and address sit in the URL path such as /v1/screen/{chain}/{address}, so a rule can pin your agent to screening and investigation for the chains it needs. You choose which operations it may call, so report export and the Companies House lookups are not included unless you add them.

Credential isolation

Your AI Decisions tenant key is stored once, encrypted, by your own Jentic One instance and attached as the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'screen a blockchain address' or 'score a transaction', and Jentic returns the matching AI Decisions operation with its input schema, including the chain and address, so the agent calls the right endpoint.

FAQs

Specific to using AI Decisions Compliance API through Jentic.

What authentication does the AI Decisions Compliance API use?

It authenticates with a tenant API key sent in the X-API-Key request header, as declared in its OpenAPI spec, with GET /health left open as a liveness check. Through Jentic the key is held by your own instance and attached per call, so an agent screening addresses never sees it.

Which chains can the AI Decisions API screen?

The screening and investigation endpoints cover Ethereum, Bitcoin, Tron, Base, Arbitrum, and Gnosis, with the chain supplied in the request path. GET /investigate/chains reports the served chains and whether a transaction history is available for each.

What are the rate limits for the AI Decisions Compliance API?

Limits are tied to the tier on your key rather than a single fixed ceiling in the spec, and GET /tiers returns the tier definitions. Check the AI Decisions documentation for the per-tier request allowance before running bulk screening jobs.

Is there an AI Decisions MCP server?

You do not need an MCP server to give your agent AI Decisions. Jentic connects it directly from the API Directory: import it, store your tenant key once, and your agent calls the screening and investigation operations it needs on demand.

How do I screen a wallet address through Jentic?

Search Jentic for 'screen a blockchain address', load the POST /v1/screen/{chain}/{address} operation, and run it with the chain and address. The response carries the risk tier and source-backed labels, with the key attached by your instance. 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 AI Decisions API?

Yes. The chain and address travel in the URL path, so a rule can allow the agent to screen and investigate addresses while leaving report export and the Companies House lookups out unless you add them. The agent stays bound to the operations you grant, and every call is logged.

AI Decisions Compliance API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityComplianceapiKey17 EndpointsREST

For Agents

Screen blockchain addresses and transactions for sanctions, mixer exposure, AI-agent patterns, and a risk tier across six chains for AI agents, with source-backed labels.

Use for: Screen a wallet address for sanctions exposure, Score the compliance risk of a transaction, Investigate an Ethereum address's history, Get the risk labels for a Bitcoin address

Not supported: Does not freeze funds, file suspicious-activity reports, or provide investment advice. Use for screening blockchain addresses and transactions for compliance risk only.

The AI Decisions Compliance API screens blockchain addresses and transactions for compliance risk, returning sanctions hits, mixer exposure, AI-agent detection, and a population-calibrated risk tier across Ethereum, Bitcoin, Tron, Base, Arbitrum, and Gnosis. Each label resolves to a primary public source so a finding can be traced. It also scores and finds behaviourally similar addresses, investigates an address's history on served chains, and exports investigation reports. A separate lookup checks UK companies in the Companies House register by name or number.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 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).

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

46%

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

16%

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.

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

50%

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

53%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AI Decisions Compliance API to your agent

Capabilities

Start building with AI Decisions Compliance API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AI Decisions Compliance API

Jentic AI Readiness Score

AI DECISIONS Compliance 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