Install Jentic One Beta

Connect the Tap Payments API to your agent

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

Create a Charge

Retrieve a Charge

List all Charges

Query and filter Tap Payments API records by parameters

Monitor Tap Payments API operational status and events

GET STARTED

Start building with Tap Payments API

Explore with Jentic One

View OpenAPI Document

Automated Charges Management

Automate charges operations by combining multiple Tap Payments API endpoints. Agents can retrieve a charge and then list all charges in a single workflow.

Call GET /charges/{chargeId} to retrieve a charge, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tap Payments 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 'create a charge', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — tap payments is a payment gateway serving the middle east and north africa.

METHOD

PATH

DESCRIPTION

POST

/charges

Create a Charge

GET

/charges/{chargeId}

Retrieve a Charge

POST

/charges/list

List all Charges

POST

/authorize

Create an Authorize

POST

/refunds

Create a Refund

GET

/refunds/{refundId}

Retrieve a Refund

POST

/refunds/list

List All Refunds

POST

/charges

Create a Charge

GET

/charges/{chargeId}

Retrieve a Charge

POST

/charges/list

List all Charges

POST

/authorize

Create an Authorize

POST

/refunds

Create a Refund

GET

/refunds/{refundId}

Retrieve a Refund

POST

/refunds/list

List All Refunds

Why Jentic?

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

Setup

Wiring the Tap Payments API by hand means setting up its bearer auth with your secret key, targeting the api.tap.company/v2 host, and handling retries on charge and refund calls yourself. Through Jentic you install once, import the Tap Payments API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Tap Payments API puts the charge id and refund id in the URL path (/charges/{chargeId}, /refunds/{refundId}), so a rule can pin your agent to read those records: you choose the operations it may call, so money-moving ones like creating a charge or issuing a refund are not included unless you add them.

Credential isolation

Your Tap Payments 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 'create a charge' or 'look up a refund', and Jentic returns the matching Tap Payments API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tap Payments API through Jentic.

What authentication does the Tap Payments API use?

The Tap Payments 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 create a charge with the Tap Payments API?

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

What are the rate limits for the Tap Payments 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 a charge through Jentic?

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

How many endpoints does the Tap Payments API have?

The Tap Payments API exposes 7 endpoints covering charges, authorize, refunds operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Tap Payments operations and credentials your agent may use. Because the API puts the charge id and refund id in the URL path (/charges/{chargeId}, /refunds/{refundId}), you can pin the agent to read-only lookups like retrieving a charge or a refund while excluding money-moving operations such as creating a charge or issuing a refund. Those operations run only if you explicitly add them to what the agent is allowed to call.

Tap Company Tap Payments API

Name: Tap Payments API
Brand: Tap Payments API
Availability: InStock

Official vendor OpenAPI document · agent-readyPaymentsPayment Processingbearer7 EndpointsREST

For Agents

Programmatically create a charge, retrieve a charge. Covers 7 operations with bearer authentication.

Use for: I need to a charge, I want to a charge, Search for all charges, Find all an authorize

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

Tap Payments is a payment gateway serving the Middle East and North Africa. The API supports creating charges, authorizations, refunds, and managing customers and payment tokens. The API exposes 7 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Connect the Tap Payments API to your agent

Capabilities

Start building with Tap Payments API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tap Company Tap Payments API