Install Jentic One Beta

Connect the Quickteller E-Wallet Transfer API to your agent

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

Open a wallet account for a userId in a given currency

Read the current balance of a wallet account by accountId

Transfer funds between two wallet accounts with an Idempotency-Key so retries are safe

GET STARTED

Start building with Quickteller E-Wallet Transfer API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Quickteller E-Wallet Transfer API for, with concrete tasks.

★ Agent-initiated wallet transfers through Jentic

A finance assistant agent can move money between Quickteller wallets when a user asks. Through Jentic the agent searches for 'transfer funds between wallets', gets the POST /transfers operation with its input schema, and sends fromAccountId, toAccountId, amount, and currency along with an Idempotency-Key, while the JWT bearer token is injected at execution time. The agent can check the source balance first so it does not attempt a transfer the wallet cannot cover.

Read the balance with GET /accounts/{accountId}/balance, then call POST /transfers with fromAccountId, toAccountId, amount 5000, currency NGN, and a fresh Idempotency-Key header

Safe retries for money movement

Payment clients regularly retry requests after timeouts, which is dangerous when the request moves money. Quickteller requires an Idempotency-Key header on POST /transfers, so a client that resends the same key after a network failure does not trigger a second transfer. The transfer response returns the transaction id and a status such as SUCCESS for confirmation.

Submit POST /transfers with a generated Idempotency-Key, and on a timeout resend the identical request with the same key, then confirm via GET /transactions/{transactionId}

Wallet reconciliation

Back-office teams reconcile wallet activity against their own ledgers. Quickteller returns a paginated list from GET /transactions filtered by the accountId query parameter with page and size controls, and GET /transactions/{transactionId} returns one transaction's details. Pairing these with GET /accounts/{accountId}/balance gives a closing balance for the period.

Page through GET /transactions with accountId set and size 50, sum the amounts, and compare the total with GET /accounts/{accountId}/balance

Key Endpoints

8 endpoints — the quickteller e-wallet transfer api registers users, opens wallet accounts in a chosen currency, and moves funds between wallet accounts in the quickteller ecosystem.

METHOD

PATH

DESCRIPTION

POST

/transfers

Transfer funds between accounts

GET

/accounts/{accountId}/balance

Get account balance

POST

/accounts

Create a wallet account

GET

/transactions

List transactions

GET

/transactions/{transactionId}

Get transaction details

POST

/auth/login

Authenticate a user

POST

/transfers

Transfer funds between accounts

GET

/accounts/{accountId}/balance

Get account balance

POST

/accounts

Create a wallet account

GET

/transactions

List transactions

GET

/transactions/{transactionId}

Get transaction details

POST

/auth/login

Authenticate a user

Why Jentic?

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

Setup

Wiring the Quickteller wallet API by hand means logging in for a JWT, attaching it as a bearer token, and generating a unique Idempotency-Key for every transfer. Through Jentic you install once, import Quickteller from the API Directory, store the token once, and your agent calls it.

Permission scoping

Transfers carry the source and destination account ids in the request body, so rules bound which operations your agent may call, not which wallet it moves money from. Limit it to the operations it needs, such as balance and transaction reads, so POST /transfers and account creation are not included unless you add them.

Credential isolation

Your Quickteller bearer token 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 'transfer funds between wallets' or 'check a wallet balance', and Jentic returns the matching Quickteller operation with its input schema, including the Idempotency-Key header, so the agent calls the right endpoint directly.

FAQs

Specific to using Quickteller E-Wallet Transfer API through Jentic.

What authentication does the Quickteller E-Wallet Transfer API use?

Per its OpenAPI spec, the API authenticates with an HTTP bearer token in JWT format sent in the Authorization header, declared at the top level of the spec. POST /auth/login takes a username and password and is the route for obtaining a token. Through Jentic the token is stored by your own instance and attached at call time, so it never enters the agent's context.

Does the Quickteller E-Wallet Transfer API prevent duplicate transfers?

Yes. POST /transfers requires an Idempotency-Key header, so resending a request with the same key after a timeout does not move funds a second time. The body requires fromAccountId, toAccountId, amount, and currency, with an optional narration.

What are the rate limits for the Quickteller E-Wallet Transfer API?

The OpenAPI spec does not specify rate limits. Check with Quickteller at https://www.quickteller.com for current limits, and test against the sandbox host https://sandbox.quickteller.com/v1 first.

Is there a Quickteller MCP server?

You don't need an MCP server to give your agent the Quickteller E-Wallet Transfer API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent calls the balance, transfer, and transaction operations it needs, discovered on demand.

Can I limit what my agent is allowed to do with the Quickteller E-Wallet Transfer API?

Yes. For example, write a rule that allows only GET /accounts/{accountId}/balance and the two transaction read operations, so the agent can report balances and history but cannot call POST /transfers or open accounts. Every call it makes is logged.

How do I transfer funds between Quickteller wallets through Jentic?

Search Jentic for 'transfer funds between wallets', load the POST /transfers operation, and execute it with fromAccountId, toAccountId, amount, currency, and an Idempotency-Key header. Confirm the result with GET /transactions/{transactionId}. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Quickteller E-Wallet Transfer API

AI ReadinessFoundational (D)45/100

See full scorecard

Community OpenAPI document · agent-readyPaymentsPayouts Transfersbearer8 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Open Quickteller wallet accounts, read balances, transfer funds between wallets with an idempotency key, and look up transaction history.

Use for: Transfer 5000 NGN from one Quickteller wallet to another, Check whether my wallet account has enough balance for a transfer, List all transactions on a wallet account this month, Get the details of a specific transfer transaction

Not supported: Does not handle card acceptance, bill payments, airtime, or bank account payouts. Use for Quickteller wallet accounts, balances, transfers, and transaction lookups only.

The Quickteller E-Wallet Transfer API registers users, opens wallet accounts in a chosen currency, and moves funds between wallet accounts in the Quickteller ecosystem. Each transfer takes a fromAccountId, toAccountId, amount, and currency, plus a required Idempotency-Key header so a retried request does not move money twice. Account balances, single transactions, and a paginated transaction history by accountId are available for reconciliation, with a sandbox host for testing.

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

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

30%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

44%

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

27%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

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 Quickteller E-Wallet Transfer API to your agent

Capabilities

Start building with Quickteller E-Wallet Transfer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Quickteller E-Wallet Transfer API

Jentic AI Readiness Score

Quickteller E-Wallet Transfer 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