Install Jentic One Beta

Connect the PayPhone API to your agent

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

Submit a card sale to PayPhone by posting the transaction to the Sale endpoint

Retrieve a sale by PayPhone's transaction id to confirm whether it settled

Retrieve a sale by your own client transaction id to reconcile it against an order

Drive a checkout that takes a card payment and then verifies the outcome before fulfilment

Reconcile settled sales against internal records using the client transaction id you supplied

GET STARTED

Start building with PayPhone API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PayPhone API for, with concrete tasks.

★ Card checkout in an Ecuadorian store

Take a card payment at checkout through PayPhone and confirm the result before completing the order. The agent submits the sale with the amount and the buyer's card details captured by the storefront, then reads the transaction back to check that it was approved so the order is only fulfilled on a settled payment.

Submit a sale for the cart amount to PayPhone, capture the returned transaction id, then read the transaction back and proceed only when its status shows the payment approved.

Order reconciliation by client transaction id

Match PayPhone sales to internal orders using the merchant's own client transaction id. The agent supplies its order reference when charging, then later looks the sale up by that same reference to reconcile payments without storing PayPhone's ids everywhere in the order system.

Read a sale by the client transaction id that was sent when charging, and compare its status and amount against the matching internal order.

Payment status verification for support

Answer a customer's payment question by checking the live status of a sale. The agent takes the PayPhone transaction id from the order and returns the current status so a support flow can tell the buyer whether the charge went through.

Look up the sale by its PayPhone transaction id and return the current status so a support agent can respond to the customer.

Key Endpoints

3 endpoints — the payphone api is the card-payment interface for payphone, a payment gateway used across ecuador.

METHOD

PATH

DESCRIPTION

POST

/api/Sale

Submit a card sale to PayPhone for processing

GET

/api/Sale/{transactionId}

Retrieve a sale by PayPhone's transaction id to check its status

GET

/api/Sale/client/{clientTransactionId}

Retrieve a sale by the merchant's own client transaction id

POST

/api/Sale

Submit a card sale to PayPhone for processing

GET

/api/Sale/{transactionId}

Retrieve a sale by PayPhone's transaction id to check its status

GET

/api/Sale/client/{clientTransactionId}

Retrieve a sale by the merchant's own client transaction id

Why Jentic?

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

Setup

Wiring PayPhone by hand means provisioning a bearer token, pointing requests at the pay.payphonetodoesposible.com host, and learning how the sale and lookup operations fit together. Through Jentic you install once, import the PayPhone API from the Jentic API Directory, save your token, and your agent calls it.

Permission scoping

PayPhone exposes a small set of operations, and because Jentic One is self-hosted, your own rules decide which the agent may call. You can allow submitting a sale while leaving the transaction lookups out until a task needs them, so every operation the agent can reach is one you chose.

Credential isolation

Your PayPhone bearer token is held encrypted by your own Jentic One instance and attached to each request only at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent, such as charging a card or checking a payment, and Jentic returns the matching PayPhone operation with typed inputs so the agent calls the right one without reading the raw specification.

FAQs

Specific to using PayPhone API through Jentic.

What authentication does the PayPhone API use?

Requests are authorized with an HTTP bearer token sent in the Authorization header. Through Jentic, that token is held encrypted by your own Jentic One instance and attached to each request at execution time, so it never appears in an agent's prompt or logs.

Can I check whether a PayPhone sale was approved?

Yes. After submitting a sale you receive PayPhone's transaction id, and you can read the sale back by that id, or by the client transaction id you supplied, to see its current status before fulfilling an order.

What are the rate limits for the PayPhone API?

The OpenAPI description does not specify rate limits. Check PayPhone's developer documentation for the limits that apply to your merchant account before running high-volume payment workloads.

Is there an MCP server for the PayPhone API?

You don't need an MCP server to use the PayPhone API with your agent. Through Jentic, your agent discovers the payment operations by intent and calls them directly, with your bearer token injected at run time by your own Jentic One instance.

How do I connect the PayPhone API to my agent through Jentic?

To run it on your own infrastructure, install Jentic One from its GitHub repo, then import the PayPhone API from the Jentic API Directory and save your bearer token. Your agent can then submit and read sales with credentials injected at execution time.

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

Yes. Because Jentic One is self-hosted, your own rules decide which PayPhone operations the agent may call, so you can allow only submitting a sale, for example, while leaving the read operations out unless a task needs them. Your bearer token stays encrypted on your own instance and is attached only when a permitted request runs.

Payphone App PayPhone API

Name: PayPhone API
Brand: PayPhone API
Availability: InStock

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsPayment Processingbearer3 EndpointsREST

For Agents

Charge cards and reconcile the resulting sales through PayPhone's payment gateway, looking transactions up by PayPhone's id or your own client transaction id.

Use for: Charge a customer's card through PayPhone, Check whether a PayPhone sale was approved, Look up a transaction by PayPhone's transaction id, Find a sale using my own client transaction id

Not supported: Handles card sales and their status lookups through PayPhone. Does not cover payouts, refunds beyond the documented operations, invoicing, accounting, or tax filing.

The PayPhone API is the card-payment interface for PayPhone, a payment gateway used across Ecuador. It lets a merchant charge a card and then track that charge to settlement: one operation submits a sale, and two read operations return the sale by PayPhone's transaction id or by the merchant's own client transaction id. Requests carry a bearer token and are sent to the pay.payphonetodoesposible.com host. It suits online stores and billing flows that need to take card payments and reconcile them against their own order records.

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: D+Signals: 4

47%

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

60%

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 PayPhone API to your agent

Capabilities

Start building with PayPhone API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Payphone App PayPhone API

Jentic AI Readiness Score

PayPhone 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