Install Jentic One Beta

Connect the EVM API to your agent

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

Get native and ERC20 token balances for a wallet address

Retrieve the decoded transaction history and net worth of a wallet

List NFTs held by a wallet and their metadata and trades

Look up NFT owners, traits, and sale prices by contract or token

Fetch ERC20 token prices, metadata, holders, and swaps

GET STARTED

Start building with EVM API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use EVM API for, with concrete tasks.

★ AI agent portfolio lookup via Jentic

An AI agent connected through Jentic reads a wallet's holdings without running a node or browsing Moralis docs. It searches by intent such as getting token balances, Jentic returns the matching Moralis operation with its input schema, and the agent fetches balances, net worth, and NFTs for an address. The developer's own Jentic One instance injects the API key at call time.

Call GET /wallets/{address}/tokens for token balances, then GET /wallets/{address}/net-worth for the wallet's value

Wallet activity and history

Analytics tools reconstruct what a wallet did. Moralis returns the complete decoded transaction history, native and ERC20 transfers, and approvals for an address, so an agent can trace activity, flag outstanding approvals, and summarize movements without decoding raw logs itself.

Call GET /wallets/{address}/history for decoded transactions, then GET /wallets/{address}/approvals to list ERC20 approvals

NFT holdings and valuation

NFT apps show what a collector owns and what it is worth. Moralis lists NFTs by wallet, returns collection and token metadata, owners, and traits, and reports sale prices by collection or token, so an agent can build a gallery and estimate floor-relative value.

Call GET /{address}/nft to list a wallet's NFTs, then GET /nft/{address}/price for collection sale prices

Token price and holder data

Dashboards track token prices and distribution. Moralis fetches ERC20 token prices individually or in bulk, returns token metadata by contract or symbol, and reports a holders summary and historical holders, so an agent can price a position and gauge how concentrated a token's ownership is.

Call GET /erc20/{address}/price for a token price, then GET /erc20/{tokenAddress}/holders for its holder summary

Key Endpoints

117 endpoints — the moralis evm api reads on-chain data from ethereum and other evm blockchains through a single rest interface.

METHOD

PATH

DESCRIPTION

GET

/wallets/{address}/tokens

Get token balances with prices by wallet

GET

/wallets/{address}/net-worth

Get wallet net worth

GET

/wallets/{address}/history

Get decoded transaction history of a wallet

GET

/{address}/nft

Get NFTs by wallet address

GET

/nft/{address}/price

Get NFT sale prices by collection

GET

/erc20/{address}/price

Get ERC20 token price

GET

/erc20/{tokenAddress}/holders

Get a holders summary by token address

GET

/transaction/{transaction_hash}

Get transaction by hash

GET

/wallets/{address}/tokens

Get token balances with prices by wallet

GET

/wallets/{address}/net-worth

Get wallet net worth

GET

/wallets/{address}/history

Get decoded transaction history of a wallet

GET

/{address}/nft

Get NFTs by wallet address

GET

/nft/{address}/price

Get NFT sale prices by collection

GET

/erc20/{address}/price

Get ERC20 token price

GET

/erc20/{tokenAddress}/holders

Get a holders summary by token address

GET

/transaction/{transaction_hash}

Get transaction by hash

Why Jentic?

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

Setup

Wiring the Moralis EVM API by hand means learning its X-API-Key header, choosing among more than a hundred read operations across wallets, NFTs, and tokens, and handling chain selection yourself. Through Jentic you install once, import Moralis from the API Directory, store the key once, and your agent calls the data operations it needs.

Permission scoping

Moralis puts the wallet or contract address in the URL path (/wallets/{address}/tokens), so a rule can pin your agent to read operations on one address. The surface is read-oriented, and you choose which operations it may call, so anything outside the balances and history reads you pick is not reachable unless you add it.

Credential isolation

Your Moralis API 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 wallet token balances' or 'list NFTs for a wallet', and Jentic returns the matching Moralis operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using EVM API through Jentic.

What authentication does the Moralis EVM API use?

The Moralis EVM API authenticates with an API key sent in the X-API-Key header, per its OpenAPI spec. Through Jentic, your key is stored encrypted by your own Jentic One instance and injected into the X-API-Key header at execution time, so it never enters the agent's prompt or logs.

Can I read a wallet's token balances with the Moralis EVM API?

Yes. The wallet operations return native and ERC20 token balances with prices, the complete decoded transaction history, outstanding approvals, and the net worth of an address, so an agent can assemble a portfolio view from a single address.

What are the rate limits for the Moralis EVM API?

The OpenAPI spec does not state numeric rate limits, and usage is typically metered in compute units per plan. Check the Moralis documentation at https://docs.moralis.io for current throughput and compute-unit costs.

How do I look up NFTs for a wallet through Jentic?

Search Jentic by intent such as listing a wallet's NFTs, and it returns the Moralis operation with its input schema. Pass the address, read the holdings, and pull metadata or sale prices, with your key injected at call 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 Moralis EVM API?

Yes. Moralis puts the wallet or contract address in the URL path, such as /wallets/{address}/tokens, so a rule can pin your agent to read operations on one address so it fetches balances and history and nothing else. The API is read-oriented, and you choose which operations it may call, with every call logged by your self-hosted instance.

Is there a Moralis EVM API MCP server?

You do not need an MCP server to give your agent the Moralis EVM API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the wallet, NFT, and token operations on demand without loading another server's tool definitions into its context.

Moralis EVM API

AI ReadinessFoundational (C+)58/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceBankingapiKey117 EndpointsREST

For Agents

Read EVM on-chain data: wallet token balances, transfers, net worth, decoded transaction history, NFT holdings and metadata, and token prices across chains.

Use for: I need to get the token balances for a wallet, I want to read the transaction history of an address, Get the net worth of a wallet, List the NFTs owned by a wallet

Not supported: Does not send transactions, custody funds, or deploy contracts. Use for reading EVM wallet, token, and NFT on-chain data only.

The Moralis EVM API reads on-chain data from Ethereum and other EVM blockchains through a single REST interface. It returns native and ERC20 token balances, transfers, approvals, and prices for a wallet, the full decoded transaction history and net worth of an address, and NFT holdings, metadata, owners, trades, and sale prices by wallet, contract, or token. Block and transaction lookups and multi-token price queries let an agent assemble a portfolio or trace activity without running its own node.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

67%

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

14%

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: BSignals: 4

48%

Example Density

How richly the API is illustrated with examples.

90%

Example Validity

Percentage of examples that conform to their schemas.

26%

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

53%

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.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

80%

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

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the EVM API to your agent

Capabilities

Start building with EVM API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Moralis EVM API

Jentic AI Readiness Score

EVM 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