Install Jentic One Beta

Connect the FawryPay API to your agent

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

Exchange credentials for a short-lived access token via /auth/token

List payment resources available to a merchant account

Retrieve a single resource record by identifier

Bridge Egyptian card, wallet, and Fawry-agent payments into agent workflows

Reference Fawry resource metadata when assembling charge requests

GET STARTED

Start building with FawryPay API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use FawryPay API for, with concrete tasks.

★ Egyptian Checkout Integration

Merchants selling into Egypt use FawryPay to accept card payments, mobile wallets, and cash via Fawry's offline agent network. The API issues an access token through /auth/token and then exposes the resources a merchant has configured, which a backend reads before constructing payment requests. This lets a small storefront integrate Egypt's most-used payment rail without building agent-network logic from scratch.

Call POST /auth/token with merchant credentials, then GET /resources to list configured FawryPay payment methods for the account.

Resource Configuration Lookup

Operations teams managing multiple FawryPay merchant accounts need to inspect which resources are provisioned. The GET /resources and GET /resources/{id} endpoints return the configured payment products and identifiers so internal tooling can reconcile billing setups, surface configuration drift, or back-fill missing IDs in an order management system.

Authenticate and call GET /resources/{id} for each configured Fawry resource ID stored in the internal merchant database.

Agent-Driven Egyptian Payment Onboarding

An AI agent helping a Cairo-based merchant onboard onto FawryPay can use Jentic to discover the auth and resources operations, exchange credentials for a token, and validate that the merchant has at least one resource configured before a customer-facing checkout goes live. The agent runs the full validation in a single Jentic-managed session without storing the raw API key.

Use Jentic to search 'authenticate fawrypay merchant', execute POST /auth/token, then run GET /resources and confirm at least one resource entry is returned.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/auth/token

Exchange credentials for an access token

GET

/resources

List configured payment resources

GET

/resources/{id}

Retrieve a single payment resource by ID

POST

/auth/token

Exchange credentials for an access token

GET

/resources

List configured payment resources

GET

/resources/{id}

Retrieve a single payment resource by ID

Why Jentic?

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

Setup

Wiring the FawryPay API by hand means setting the X-API-Key header, calling /auth/token to obtain a scoped access token, and using it for resource lookups yourself. Through Jentic you install once, import FawryPay from the API Directory, store the key once, and your agent calls it.

Permission scoping

FawryPay puts the resource id in the URL path (/resources/{id}), so a rule can pin your agent to one resource. You choose the operations it may call, so it can authenticate and read the resources you allow and nothing beyond them.

Credential isolation

Your FawryPay X-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 'authenticate a FawryPay merchant', and Jentic returns the matching FawryPay operation with its input schema so the agent calls POST /auth/token without browsing the docs.

FAQs

Specific to using FawryPay API through Jentic.

Why is there no official OpenAPI spec for FawryPay API?

FawryPay does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FawryPay 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 FawryPay API use?

The FawryPay API uses an API key passed in the X-API-Key header to call POST /auth/token, which returns a short-lived access token used on subsequent requests. Through Jentic the raw X-API-Key is held in the vault so agents only ever see scoped tokens.

Can I list all payment resources on my FawryPay account?

Yes. GET /resources returns the payment resources configured for the authenticated merchant, and GET /resources/{id} returns a single resource by its identifier.

What are the rate limits for the FawryPay API?

FawryPay does not publish per-endpoint rate limits in the spec; production limits are set per merchant contract. Apply exponential backoff on 429 responses and contact FawryPay support for documented thresholds.

How do I authenticate against FawryPay through Jentic?

Run pip install jentic, then search 'authenticate fawrypay merchant', load the POST /auth/token operation, and execute it with credentials sourced from your Jentic One instance to receive an access token.

Does FawryPay support recurring billing?

This spec exposes authentication and resource lookup only; recurring billing is configured server-side by FawryPay and is not represented as endpoints in this OpenAPI definition.

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

Yes. Because Jentic One is self-hosted, your own rules decide which FawryPay operations the agent may call and which credentials it may use. You can allow only authentication via POST /auth/token and reads through GET /resources while blocking everything else, and since FawryPay puts the resource id in the URL path at GET /resources/{id}, a rule can pin the agent to a single resource. The agent can authenticate and read the resources you permit and nothing beyond them.

FawryPay API

Name: FawryPay API
Brand: FawryPay API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticPaymentsPayment ProcessingapiKey3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Authenticate against FawryPay and retrieve payment resource configurations needed to charge customers across Egypt's Fawry network.

Use for: I need to authenticate with FawryPay and obtain an access token, List the payment resources available on my FawryPay merchant account, Retrieve a specific FawryPay resource by its ID, Check whether my FawryPay API key is still valid

Not supported: Does not handle subscriptions, refunds, or dispute management - use for FawryPay merchant authentication and resource lookup only.

Jentic publishes the only available OpenAPI specification for FawryPay API, keeping it validated and agent-ready. FawryPay is an Egyptian electronic payment gateway that lets merchants accept card, wallet, and cash-at-agent payments across Egypt. The API exposes a token-based authentication flow followed by resource lookups so backends can authorise transactions and reference payment configurations. It targets local commerce, billers, and SaaS platforms that need access to Fawry's nationwide acceptance network.

Jentic One on Github View OpenAPI Document