Install Jentic One Beta

Connect the M-PESA Ethiopia API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the M-PESA Ethiopia 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%2Fsafaricom.et%2Fsafaricom-et" | 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%2Fsafaricom.et%2Fsafaricom-et" | 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 M-PESA Ethiopia API.

Create payment

Get payment status

Integrate M-PESA Ethiopia API into automated workflows

Query and filter M-PESA Ethiopia API records by parameters

Monitor M-PESA Ethiopia API operational status and events

GET STARTED

Start building with M-PESA Ethiopia API

Explore with Jentic One

View OpenAPI Document

Data Retrieval and Monitoring

Query M-PESA Ethiopia API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary M-PESA Ethiopia API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call M-PESA Ethiopia 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 apiKey tokens manually.

Search Jentic for 'create payment', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — m-pesa mobile money platform for ethiopia.

METHOD

PATH

DESCRIPTION

POST

/payments

Create payment

GET

/payments/{id}

Get payment status

POST

/payments

Create payment

GET

/payments/{id}

Get payment status

Why Jentic?

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

Setup

Wiring the M-PESA Ethiopia API by hand means managing its X-API-Key header, attaching it to each call against api.safaricom.et, and handling your own retries. Through Jentic you install once, import the M-PESA Ethiopia API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The M-PESA Ethiopia API takes payment details in the request body rather than pinning to a resource path, so scope the agent to the operations it needs, such as checking a payment's status by id, and leave out creating payments unless the agent needs them.

Credential isolation

Your M-PESA Ethiopia 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 'create a payment' or 'check payment status', and Jentic returns the matching M-PESA Ethiopia API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using M-PESA Ethiopia API through Jentic.

What authentication does the M-PESA Ethiopia API use?

The M-PESA Ethiopia API uses an API key passed in the `X-API-Key` 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 create payment with the M-PESA Ethiopia API?

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

What are the rate limits for the M-PESA Ethiopia 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 create payment through Jentic?

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

How many endpoints does the M-PESA Ethiopia API have?

The M-PESA Ethiopia API exposes 2 endpoints covering payments operations.

Can I limit what my agent is allowed to do with the M-PESA Ethiopia API?

Yes. Because you run Jentic One yourself, your own rules decide which M-PESA Ethiopia API operations and credentials the agent may use. The API has just two operations, creating a payment via POST /payments and checking a payment's status by id via GET /payments/{id}, so you can allow the read-only status check while withholding payment creation until the agent genuinely needs it. Your API key is injected only for the operations you permit, so the agent never sees the raw secret or calls an endpoint you have not scoped it to.

Safaricom Et M-PESA Ethiopia API

Name: M-PESA Ethiopia API
Brand: M-PESA Ethiopia API
Availability: InStock

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey2 EndpointsREST

For Agents

Programmatically create payment, get payment status. Covers 2 operations with apiKey authentication.

Use for: I need to payment, I want to payment status, Get the current status of M-PESA Ethiopia API resources, List all records from M-PESA Ethiopia API

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

M-PESA mobile money platform for Ethiopia. The API exposes 2 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

100%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

30%

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.

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

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the M-PESA Ethiopia API to your agent

Capabilities

Start building with M-PESA Ethiopia API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Safaricom Et M-PESA Ethiopia API

Jentic AI Readiness Score

M-PESA Ethiopia 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