Install Jentic One Beta

Connect the idexo API to your agent

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

Provision a new blockchain wallet via POST /wallets

Retrieve a specific wallet's details by ID through GET /wallets/{id}

List wallets associated with the authenticated account via GET /wallets

Operate wallet lifecycle steps without exposing private-key handling to client applications

Use a single API key to manage all wallets across the integrator account

GET STARTED

Start building with idexo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use idexo API for, with concrete tasks.

★ User-Linked Wallet Provisioning

When a user signs up for a Web3-aware product, the agent calls POST /wallets to create a hosted wallet linked to that user. The integrator stores the returned wallet ID alongside its own user record. This avoids forcing the user to install a wallet extension on first contact and is typically live within a day because the surface is only three endpoints.

Call POST /wallets at user signup and persist the returned wallet ID against the user's account record

Wallet Lookup for Customer Support

Customer support staff query a user's wallets to debug issues. The agent calls GET /wallets/{id} for the wallet ID stored on the user record and returns the address and metadata. This avoids exposing internal infrastructure to support staff while still giving them enough to triage.

Call GET /wallets/{id} with the wallet ID from the support ticket and return the address and creation timestamp

Account Wallet Inventory

Audit or report on every wallet the account has provisioned. GET /wallets returns the list scoped to the authenticated account, enabling periodic exports for finance or compliance review without scraping the dashboard.

Call GET /wallets and export the returned list of wallet IDs and addresses to a CSV for compliance review

AI Agent Onboarding to Web3

An onboarding agent uses Jentic to find idexo operations matching 'create a blockchain wallet for a user', loads the /wallets schema, and provisions a wallet during the user's first conversation with the product. The agent confirms creation in chat and stores the ID for future operations.

Use Jentic search 'create a blockchain wallet for a user' to load the idexo /wallets schema and execute POST /wallets for the new user

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for idexo api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/wallets

Create a new hosted wallet

GET

/wallets

List wallets for the authenticated account

GET

/wallets/{id}

Retrieve a specific wallet by ID

POST

/wallets

Create a new hosted wallet

GET

/wallets

List wallets for the authenticated account

GET

/wallets/{id}

Retrieve a specific wallet by ID

Why Jentic?

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

Setup

Wiring the idexo API by hand means passing your key in the Authorization header and mapping its hosted-wallet provisioning and lookup routes yourself. Through Jentic you install once, import the idexo API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

idexo puts the wallet id in the URL path (/wallets/{id}), so a rule can pin your agent to reading one wallet. You choose the operations it may call, so creating new wallets is not included unless you add it.

Credential isolation

Your idexo 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 'provision a hosted wallet' or 'look up a wallet by id', and Jentic returns the matching idexo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using idexo API through Jentic.

Why is there no official OpenAPI spec for idexo API?

idexo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call idexo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the idexo API use?

The idexo API uses an API key passed in the Authorization header. Keys are issued from the idexo dashboard and scope all wallet operations to your account. Through Jentic, the key is stored encrypted in your Jentic One instance and injected at execution time, so the raw key never enters the agent's prompt context.

Can I provision a wallet for each new user with the idexo API?

Yes. POST /wallets creates a hosted wallet that you can associate with your own user record. The response includes the wallet ID and address - store the ID and use GET /wallets/{id} later to retrieve the wallet without re-creating it.

What are the rate limits for the idexo API?

idexo applies per-account rate limits tied to the subscription tier. The OpenAPI spec does not encode hard thresholds. Build agents to handle 429 responses with backoff and to cache wallet lookups locally rather than calling GET /wallets/{id} on every page load.

How do I create a wallet through Jentic?

Run pip install jentic and import the SDK, then await client.search('create a blockchain wallet for a user') to find the idexo /wallets operation. Load the schema and execute POST /wallets to create the wallet, then persist the returned ID. Run Jentic One, the self-hosted execution layer, for an API key.

Which blockchains does the idexo API support?

The OpenAPI spec exposes a chain-agnostic /wallets surface - the specific chains supported depend on the idexo platform configuration available to your account. Check the idexo dashboard for the active chain list before relying on a particular chain in production.

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

Yes. Jentic One is self-hosted, so your own rules decide which idexo operations and credentials the agent may use. You can allow only the read routes, GET /wallets and GET /wallets/{id}, and leave out POST /wallets so the agent can look up wallets but never create them. Because the wallet id sits in the path at /wallets/{id}, a rule can pin the agent to reading a single wallet rather than the whole account.

idexo API

Name: idexo API
Brand: idexo API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticDeveloper ToolsPackage RegistryapiKey3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Provision and look up blockchain wallets through three REST endpoints, letting agents add wallet management to a product without running chain nodes.

Use for: Create a new blockchain wallet for a user, Retrieve a wallet by its ID, List all wallets created by my account, Provision a wallet at user sign-up

Not supported: Does not handle on-chain transaction signing, NFT minting, or token transfers - use for hosted wallet provisioning and lookup only.

Jentic publishes the only available OpenAPI specification for idexo API, keeping it validated and agent-ready. idexo provides REST endpoints for blockchain identity and wallet management, letting developers create and look up wallets without operating their own chain infrastructure. The current surface is intentionally narrow - three endpoints under /wallets - making idexo a quick way to add wallet provisioning to a product without dealing directly with private-key handling on the client side.

Jentic One on Github View OpenAPI Document

Connect the idexo API to your agent

Capabilities

Start building with idexo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

idexo API