Igtbdigital Wallet Action APIs

Name: Wallet Action APIs
Brand: Wallet Action APIs
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontnone4 Endpoints

Install Jentic One Beta

Connect the Wallet Action APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Wallet Action APIs, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Wallet Action APIs.

Draft / Initiate to Create a wallet

Update Wallet Request Status

Integrate Wallet Action APIs into automated workflows

Query and filter Wallet Action APIs records by parameters

GET STARTED

Start building with Wallet Action APIs

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically draft / initiate to create a wallet, draft / initiate to update existing wallet.. Covers 4 operations.

Use for: I need to draft / initiate to create a wallet, I want to draft / initiate to update existing wallet., Search for draft / initiate to delete existing wallet, Find all wallet request status

Not supported: Does not handle payments, communications, or crm - use for e-commerce only.

Use Cases

Patterns agents use Wallet Action APIs for, with concrete tasks.

★ E-Commerce Operations

Use the Wallet Action APIs to perform e commerce operations programmatically. The API provides 4 endpoints covering core functionality including draft / initiate to create a wallet, draft / initiate to update existing wallet., draft / initiate to delete existing wallet.

Call POST /v1/wallets to draft / initiate to create a wallet

Automated Wallet Management

Automate wallet operations by combining multiple Wallet Action APIs endpoints. Agents can draft / initiate to update existing wallet. and then draft / initiate to delete existing wallet in a single workflow.

Call PUT /v1/wallets/{walletId} to draft / initiate to update existing wallet., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Wallet Action APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Search Jentic for 'draft / initiate to create a wallet', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — wallet catalog is basically an feature containing different wallet types.

METHOD

PATH

DESCRIPTION

POST

/v1/wallets

Draft / Initiate to Create a wallet

PUT

/v1/wallets/{walletId}

Draft / Initiate to Update existing Wallet.

DELETE

/v1/wallets/{walletId}

Draft / Initiate to Delete existing Wallet

PUT

/v1/wallets/{channelSeqId}/state

Update Wallet Request Status

POST

/v1/wallets

Draft / Initiate to Create a wallet

PUT

/v1/wallets/{walletId}

Draft / Initiate to Update existing Wallet.

DELETE

/v1/wallets/{walletId}

Draft / Initiate to Delete existing Wallet

PUT

/v1/wallets/{channelSeqId}/state

Update Wallet Request Status

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

This API declares no authentication, so there is no secret to pass. If the live endpoint later requires a credential, it is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a wallet' or 'update a wallet', and Jentic returns the matching Wallet Action APIs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Wallet Action APIs through Jentic.

What authentication does the Wallet Action APIs use?

The Wallet Action APIs uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I draft / initiate to create a wallet with the Wallet Action APIs?

Yes. Use the POST /v1/wallets endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Wallet Action APIs?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I draft / initiate to create a wallet through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'draft / initiate to create a wallet'. Jentic returns the matching Wallet Action APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Wallet Action APIs have?

The Wallet Action APIs exposes 4 endpoints covering wallet operations.

Can I limit what my agent is allowed to do with the Wallet Action APIs?

Yes. Because you run Jentic One yourself, your own rules decide which of the four operations the agent may call, so you can grant read or update access while withholding destructive ones like DELETE /v1/wallets/{walletId} or the state change on /v1/wallets/{channelSeqId}/state. Since the wallet id sits in the URL path (/v1/wallets/{walletId}), a rule can pin the agent to a single wallet, letting it update that wallet and nothing else. The operator controls the operations and credentials the agent is permitted to use.