Install Jentic One Beta

Connect the rpc.aex402.com to your agent

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

Proxy JSON-RPC calls to Solana and EVM chains through per-chain endpoints

Create OpenAI-compatible chat completions and list available models

Generate, list, and revoke wallet-signed API keys

Check prepaid credit balance and top up from a confirmed payment

Spawn and list autonomous trading agents backed by burner wallets

GET STARTED

Start building with rpc.aex402.com API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use rpc.aex402.com API for, with concrete tasks.

★ Agent-Paid Multi-Chain RPC

An on-chain agent needs RPC access to several networks without holding accounts at each node provider. The AEX402 API routes JSON-RPC to Solana and EVM chains such as Ethereum and Base through per-chain endpoints, settling per call with x402, so the agent points a wallet at one proxy and reaches many chains on prepaid credit.

Send a JSON-RPC balance query to the Base endpoint through the proxy and return the result

Pay-Per-Call AI Inference

A developer wants OpenAI-compatible inference billed per call instead of a monthly plan. The AEX402 API serves chat completions and a models list on an OpenAI-compatible surface, paid with x402 micropayments, so an agent can run inference against it with the same client it already uses for OpenAI-style APIs.

List the available models, then create a chat completion against the chosen model

Wallet-Signed Key Management

A team provisions API keys tied to a wallet rather than an account. The AEX402 API generates wallet-signed keys, lists their prefixes, and revokes them, and reports the prepaid credit balance, so an agent can rotate keys and watch spend without a traditional login.

Generate a wallet-signed API key, then check the prepaid credit balance tied to the wallet

Key Endpoints

27 endpoints — the aex402 api is a multi-chain rpc proxy and an openai-compatible ai inference proxy, both paid with x402 micropayments.

METHOD

PATH

DESCRIPTION

POST

/v1/chat/completions

Create an OpenAI-compatible chat completion

GET

/v1/models

List available AI models

POST

/eth

Ethereum mainnet JSON-RPC proxy

POST

/base

Base mainnet JSON-RPC proxy

POST

/v1/api-keys

Generate a wallet-signed API key

GET

/credits

Check prepaid credit balance

POST

/agents

Spawn an autonomous trading agent

POST

/v1/chat/completions

Create an OpenAI-compatible chat completion

GET

/v1/models

List available AI models

POST

/eth

Ethereum mainnet JSON-RPC proxy

POST

/base

Base mainnet JSON-RPC proxy

POST

/v1/api-keys

Generate a wallet-signed API key

GET

/credits

Check prepaid credit balance

POST

/agents

Spawn an autonomous trading agent

Why Jentic?

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

Setup

Wiring AEX402 by hand means handling x402 micropayments, wallet-signed key generation, and per-chain RPC routing yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.

Permission scoping

You choose which AEX402 operations your agent may call, so it can proxy RPC and run inference while the trading-agent and key-revocation operations stay out of the set unless you add them.

Credential isolation

Your AEX402 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 'proxy an RPC call to an EVM chain' or 'create a chat completion', and Jentic returns the matching AEX402 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using rpc.aex402.com API through Jentic.

What authentication does the AEX402 API use?

The AEX402 API accepts a bearer token in the Authorization header and session or wallet API-key headers, per its OpenAPI spec. Several endpoints, such as health, credit balance, and the chain RPC proxies, are described as free. Paid operations settle with x402 micropayments. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.

Can I use AEX402 for both RPC and AI inference?

Yes. The API routes JSON-RPC to Solana and EVM chains through per-chain endpoints you can point a wallet at, and it serves OpenAI-compatible chat completions and a models list from the same service. An agent can reach both the chain proxies and the inference proxy through one integration.

What are the rate limits for the AEX402 API?

The OpenAPI spec does not state fixed numeric rate limits, and it exposes a status endpoint reporting the current pricing and limit configuration. Check the AEX402 documentation at https://rpc.aex402.com/llms.txt for the current limits.

How do I proxy an RPC call through Jentic?

Import the AEX402 API from the Jentic directory and give your agent an intent such as 'proxy an RPC call to an EVM chain'. Jentic returns the matching proxy operation with its input schema, your agent sends the JSON-RPC request, and your stored key is injected at execution 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 AEX402 API?

Yes. Write a rule that allows only the RPC-proxy and inference operations, so your agent can query chains and run completions while the trading-agent and key-revocation operations stay out of the set unless you add them, and every call it makes is logged.

Is there an AEX402 MCP server?

You don't need an MCP server to give your agent the AEX402 API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, so no extra server's tool definitions sit in the agent's context.

Aex402 rpc.aex402.com

AI ReadinessFoundational (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureNetworkingapiKey, bearer27 EndpointsREST

For Agents

Proxy JSON-RPC to Solana and EVM chains and run OpenAI-compatible inference, paid per call with x402, with wallet-signed key management.

Use for: Proxy an RPC call to the Base network, Create a chat completion through the AI proxy, List the AI models available, Generate a wallet-signed API key

Not supported: Does not custody long-term funds, run a wallet interface, or settle fiat payments. Use for proxying multi-chain RPC and AI inference with x402 micropayments only.

The AEX402 API is a multi-chain RPC proxy and an OpenAI-compatible AI inference proxy, both paid with x402 micropayments. It routes JSON-RPC calls to Solana and many EVM chains, including Ethereum, Base, and HyperEVM, through per-chain endpoints you can point a wallet at, and it serves OpenAI-style chat completions and a models list. It also manages wallet-signed API keys and can spawn autonomous trading agents backed by their own burner wallets.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

88%

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

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

35%

Response Coverage

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

87%

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

33%

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.

52%

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

45%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the rpc.aex402.com to your agent

Capabilities

Start building with rpc.aex402.com API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Aex402 rpc.aex402.com

Jentic AI Readiness Score

rpc.aex402.com

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