Install Jentic One Beta

Connect the TigoPesa API to your agent

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

Generate access token

System health check

Authorize a payment

Validate MFS account

Deposit remittance

GET STARTED

Start building with TigoPesa API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use TigoPesa API for, with concrete tasks.

★ Payments Operations

Use the TigoPesa API to perform payments operations programmatically. The API provides 8 endpoints covering core functionality including generate access token, system health check, authorize a payment.

Call POST /v1/oauth/generate/accesstoken to generate access token

Automated Authentication Management

Automate authentication operations by combining multiple TigoPesa API endpoints. Agents can system health check and then authorize a payment in a single workflow.

Call GET /v1/tigo/systemstatus to system health check, then verify the result

AI Agent Integration via Jentic

AI agents discover and call TigoPesa API 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 bearer tokens manually.

Search Jentic for 'generate access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — tigopesa mobile money api for payment authorization, mfs account validation, remittance deposits, and transaction management.

METHOD

PATH

DESCRIPTION

POST

/v1/oauth/generate/accesstoken

Generate access token

GET

/v1/tigo/systemstatus

System health check

POST

/v1/tigo/payment-auth/autorize

Authorize a payment

POST

/v1/tigo/mfs/validateMFSAccount

Validate MFS account

POST

/v1/tigo/mfs/depositRemittance

Deposit remittance

POST

/v1/tigo/mfs/reverseTransaction

Reverse a transaction

GET

/v1/payment-auth/transactions/{MasterMerchantId}{transactionRefId}

Get payment auth transaction status

GET

/v1/tigo/mfs/depositRemittance/transactions/{PaymentAggregatorId}{transactionRefId}

Get remittance transaction status

POST

/v1/oauth/generate/accesstoken

Generate access token

GET

/v1/tigo/systemstatus

System health check

POST

/v1/tigo/payment-auth/autorize

Authorize a payment

POST

/v1/tigo/mfs/validateMFSAccount

Validate MFS account

POST

/v1/tigo/mfs/depositRemittance

Deposit remittance

POST

/v1/tigo/mfs/reverseTransaction

Reverse a transaction

GET

/v1/payment-auth/transactions/{MasterMerchantId}{transactionRefId}

Get payment auth transaction status

GET

/v1/tigo/mfs/depositRemittance/transactions/{PaymentAggregatorId}{transactionRefId}

Why Jentic?

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

Setup

Wiring the TigoPesa API by hand means calling its token endpoint to mint a bearer token, choosing between the production and sandbox hosts, and building the payment and remittance calls yourself. Through Jentic you install once, import the TigoPesa API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The TigoPesa payment and remittance operations take their target in the request body rather than a path resource, so scoping is operations-only: you limit the agent to the operations it needs, such as checking system status or validating an account, rather than pinning it to one account. Money-moving operations like depositing a remittance or reversing a transaction are only available if you add them.

Credential isolation

Your TigoPesa credential 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 'validate a mobile money account' or 'check system status', and Jentic returns the matching TigoPesa API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using TigoPesa API through Jentic.

What authentication does the TigoPesa API use?

The TigoPesa API uses a Bearer token in the Authorization header. 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 generate access token with the TigoPesa API?

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

What are the rate limits for the TigoPesa API?

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 generate access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'generate access token'. Jentic returns the matching TigoPesa API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the TigoPesa API have?

The TigoPesa API exposes 8 endpoints covering authentication, mfs, payments operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TigoPesa operations and credentials the agent can use, and it can only call the operations you import. TigoPesa takes its target in the request body rather than a path resource, so scoping is operations-only: you can allow read-only calls like checking system status or validating an MFS account while withholding money-moving operations. Depositing a remittance, authorizing a payment, or reversing a transaction are available to the agent only if you add them.

Tigo TigoPesa API

Name: TigoPesa API
Brand: TigoPesa API
Availability: InStock

Official vendor OpenAPI document · agent-readyPaymentsBilling Subscriptionsbearer8 EndpointsREST

For Agents

Programmatically generate access token, system health check. Covers 8 operations with bearer authentication.

Use for: I need to generate access token, I want to system health check, Search for authorize a payment, Find all validate mfs account

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

TigoPesa mobile money API for payment authorization, MFS account validation, remittance deposits, and transaction management. The API exposes 8 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Connect the TigoPesa API to your agent

Capabilities

Start building with TigoPesa API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tigo TigoPesa API