Community OpenAPI document · agent-readyFinanceBankingbearer9 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Check PulliPay cash and cashback wallet balances, read BNPL and 4x installment summaries, and create cash wallet top-ups for a signed-in customer.
Use for: What is my PulliPay cash wallet balance?, Check whether I have cashback available in PulliPay, Get the unified overview of all my PulliPay balances, I want to top up my PulliPay cash wallet
Not supported: Does not handle merchant checkout, card acquiring, or bank account transfers. Use for reading PulliPay wallet and BNPL balances and creating cash wallet top-ups only.
The PulliPay API reads a PulliPay customer's cash wallet, cashback wallet, and unified balance overview, and starts cash wallet top-ups. It also returns summaries of the customer's buy-now-pay-later credit: a monthly BNPL summary and a 4x installment summary. Onboarding is covered too, with signup by phone and national ID plus one-time-password send and verify steps.
Install Jentic One Beta
Connect the PulliPay API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PulliPay 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.
1
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%2Fpullipay.com%2Fpullipay" | sh2
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%2Fpullipay.com%2Fpullipay" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 PulliPay API.
Read the cash wallet balance and the cashback wallet balance separately
Pull a unified overview of all PulliPay balances in one call via /overview/balances
Create a cash wallet top-up with an amount, currency, optional source, and callback_url
Summarise the customer's monthly buy-now-pay-later position with the BNPL summary
Review the 4x installment plan summary for split purchases
Register a customer with phone and national_id, then send and verify a one-time password
Use Cases
Patterns agents use PulliPay API for, with concrete tasks.
★ Agent balance check through Jentic
A personal finance agent answers questions like 'how much can I spend this month?' by calling the PulliPay overview, cash wallet, and cashback wallet balance operations through Jentic. The bearer token is injected by the developer's own Jentic One instance, so the agent reads balances without holding the token itself.
Call GET /overview/balances, then GET /wallets/cashback/balance, and report the combined cash and cashback position to the user
Wallet top-up
When a customer wants to add funds, the create top-up operation accepts the required amount and currency plus an optional source and a callback_url that PulliPay can notify when the top-up completes. Pair it with the cash wallet balance read to confirm the new balance afterwards.
POST /wallets/cash/topups with amount 250 and currency 'SAR', then GET /wallets/cash/balance to confirm the updated balance
BNPL and installment monitoring
Buy-now-pay-later users need to see what they owe. The monthly BNPL summary and the 4x installment summary give an agent the data to remind a customer of upcoming obligations or explain their current credit position.
GET /credit/bnpl/monthly/summary and GET /credit/installments/4x/summary, then summarise the outstanding amounts for the user
Phone-based onboarding
New customers sign up with a phone number and national_id (with an optional invite_code), then confirm the phone through the OTP send and verify operations, where send takes the phone and a purpose. This lets an onboarding flow register and verify a customer in sequence.
POST /auth/signup with phone and national_id, POST /auth/otp/send with the phone and purpose, then POST /auth/otp/verify with the phone and the received otp
Key Endpoints
9 endpoints — the pullipay api reads a pullipay customer's cash wallet, cashback wallet, and unified balance overview, and starts cash wallet top-ups.
METHOD
PATH
DESCRIPTION
GET
/overview/balances
Unified overview of balances
GET
/wallets/cash/balance
Cash wallet balance
POST
/wallets/cash/topups
Create a cash wallet top-up
GET
/wallets/cashback/balance
Cashback wallet balance
GET
/credit/bnpl/monthly/summary
Monthly BNPL summary
GET
/credit/installments/4x/summary
4x installment summary
POST
/auth/signup
Sign up a customer
GET
/overview/balances
Unified overview of balances
GET
/wallets/cash/balance
Cash wallet balance
POST
/wallets/cash/topups
Create a cash wallet top-up
GET
/wallets/cashback/balance
Cashback wallet balance
GET
/credit/bnpl/monthly/summary
Monthly BNPL summary
GET
/credit/installments/4x/summary
4x installment summary
POST
/auth/signup
Sign up a customer
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
PulliPay API
- Non-Ready (F)30/100
82
Foundational Compliance64
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability75
Security8
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
82
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
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).
30%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
64
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
56%
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.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
26%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
8
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
8%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring PulliPay by hand means obtaining a JWT bearer token through its signup and OTP flow and attaching it to each wallet and credit call yourself. Through Jentic you install once, import PulliPay from the API Directory, store the token once, and your agent calls it.
Permission scoping
PulliPay paths carry no resource ids, so rules bound which operations your agent may call rather than which wallet. You choose the operations it may call, so a money-moving one like the cash wallet top-up is not included unless you add it.
Credential isolation
Your PulliPay bearer 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 'check my wallet balance' or 'show my BNPL summary', and Jentic returns the matching PulliPay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PulliPay API through Jentic.
What authentication does the PulliPay API use?
The PulliPay API declares an HTTP bearer scheme (BearerAuth) with a JWT bearer format in its OpenAPI spec, applied globally. Through Jentic, the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Can I top up a PulliPay cash wallet through the API?
Yes. POST /wallets/cash/topups creates a top-up. The body requires amount and currency, and accepts an optional source and a callback_url for completion notification. Read GET /wallets/cash/balance afterwards to confirm the new balance.
What are the rate limits for the PulliPay API?
The OpenAPI spec does not specify rate limits. Check PulliPay's own developer documentation for current limits before running high-volume balance polling.
How do I check wallet balances with the PulliPay API through Jentic?
Install Jentic One, import the PulliPay API from the Jentic API Directory, and store your bearer token. Your agent searches for 'check my wallet balance', Jentic returns the GET /overview/balances operation with its schema, and the agent calls it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a PulliPay MCP server?
You don't need an MCP server to give your agent PulliPay. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, with operations discovered on demand instead of loading a full tool list into its context.
Can I limit what my agent is allowed to do with the PulliPay API?
Yes. Write a rule that allows only GET /overview/balances, GET /wallets/cash/balance, and GET /wallets/cashback/balance, and your agent can report balances while a top-up request is outside what it may call. Add POST /wallets/cash/topups to the rule only when you want it to move money.
GET STARTED