Pinelabs One

Pinelabs Merchant App

Category: Commerce
Primary Subcategory: Payment Processing & Gateways

Integration details

Description

Pine Labs ONE empowers merchants with a simple, intelligent, and convenient way to manage their business. Track transactions and payment activity in real time. Get business insights and payment information instantly. Access quick and easy in-app support. Get assistance with transactions, settlements, refunds, and payment-related queries. Available in English and Hindi. Pine Labs ONE — simplifying payments, insights, and merchant support through AI-powered assistance.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Commerce
Primary Subcategory: Payment Processing & Gateways
Secondary Subcategories: None listed
Brand: Pine Labs
Access: Account required
First tracked: 2026-09-17
Tool count: 38
Geography: US

ChatGPT Plugin Discovery Score

ChatGPT Plugin discovery is coming soon

ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.

No spam. Unsubscribe any time.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Payment Processing & Gateways

View Category

Listed in alphabetical order

Primary Subcategory

airpayComing soonGet notified

CashfreeComing soonGet notified

FintocComing soonGet notified

GoCardlessComing soonGet notified

Juspay GeniusComing soonGet notified

Pinelabs OneComing soonGet notified

Tools

38 tools agents can invoke

Create/provision an autonomous PineAI agent/task from a user's natural-language query. Use this when the user says 'create an agent', 'provision an agent', 'make an autonomous agent', 'automate this report', or asks ChatGPT to set up an agent that performs a task on its own. This creates a scheduled PineAI task backed by the selected existing agent. If the user names an agent, pass that name or key in agentId; this tool resolves it to the backend UUID. If the user has not chosen a backing agent, leave agentId empty; this tool uses backend autonomous_agent even if it is hidden from getAgents(). After user confirmation or OAuth login completes, continue with the already collected values and call this tool; do not restart the collection flow.
Create a new PineAI chat session. Use this after listChatSessions() and getActivationStatus(). The backend supports creating a session with title only; agentId is optional. If the user names an agent, pass the name/key in agentId and this tool resolves it.
Create/provision a new AI schedule for automated reports/tasks. Use the user's natural-language query as the task the agent must run each time. If the user gives an agent name or key instead of a UUID, pass it in agentId; this tool resolves it. If the user does not name a backing agent, leave agentId empty; this tool uses backend autonomous_agent even if it is hidden from getAgents(). Supports frequencies: hourly, daily, weekly, monthly, once. Channels: push_notification, whatsapp, both. For weekly schedules, provide dayOfWeek (0=Sunday to 6=Saturday). For monthly schedules, provide dayOfMonth (1-28). IMPORTANT: Ask the user only for missing schedule details: title, query/task, frequency, time, channel, and start date. Do not ask for agentId unless the user wants a specific backing agent.
Delete a schedule permanently. This cannot be undone. IMPORTANT: Confirm with the user before deleting. Ask 'Are you sure you want to delete this schedule?'
Enable/activate a specific PineAI agent definition/template by agentKey or display name. Use this when user wants to turn on an agent like 'enable the FAQ agent' or 'activate data agent'. Get the agentKey from getAgents() first.
Check whether PineAI is activated for this merchant and which agents are currently enabled. Use this when user asks 'is AI activated?', 'what's enabled?', or before trying to use an agent.
List available PineAI agent definitions/templates with their IDs, names, descriptions, and enabled status. Use this when the user asks 'what agents are available?' or wants to choose a backing agent before creating a schedule/autonomous task. Do not use this for 'show me all agents running' or provisioned autonomous agents; use listRunningAgents() or listSchedules() instead. Returns agentId (UUID needed for schedules/sessions), agentKey (short identifier), name, description, and whether enabled.
Get an overview of what this application does, its key features, and supported operations. Use this when user asks 'what can you do?', 'what is this app?', or needs help understanding the available capabilities.
List all available tools and their descriptions. Use this when user asks 'what tools are available?', 'help', or wants to know all possible actions.
Fetch terminal issue categories for raising a service ticket. STEP 2 of the service ticket workflow (after getStoreList). IMPORTANT: Present the returned categories as a NUMBERED LIST to the user and ASK them to pick one. Do NOT proceed until the user selects a category. After user picks a category, call getPosTerminals with the storeId from Step 1.
Get the last N transactions for the merchant. Response fields: transactionId, transactionDate, transactionAmount, storeName, storeAddress, reportType, subReportType, merchantId, posId, paymentMode. Use this when the user asks about their recent transactions.
Get merchant profile and core details. Response fields: merchantId, merchantName, paymentModel, merchantCategory, programs. Use this when user asks 'who am I', 'my merchant details', or about their profile.
Get payout/settlement summary for a date range. Returns all settlement aggregate fields including settledAmount. Use this when user asks about settlements over a period.
Fetch POS terminals for a specific store. Returns posId, hardware model, and active status. STEP 3 of the service ticket workflow (after user selected a category). IMPORTANT: Present the returned POS terminals as a NUMBERED LIST to the user and ASK them to select the affected terminal(s). Do NOT proceed until the user selects at least one POS terminal. After user picks terminal(s), ask for a brief description of the issue, then call raiseServiceTicket.
Get global run history across ALL schedules. Shows recent executions from all automated tasks. Use when user asks 'what ran recently?' or wants an overview of all schedule activity.
Get a count of active and paused schedules. Quick overview without full details. Use when user asks 'how many schedules do I have?' or wants a quick status summary.
Get execution run history for a specific schedule. Shows status, result, errors, and timestamps. Use when user asks about a schedule's past runs or wants to check if a schedule ran successfully.
Get chat message history for a PineAI session. Shows all messages exchanged in the conversation. Use when user wants to review past chat messages or conversation history.
Get details of a specific settlement by UTR number. Response fields: utrNumber, totalTransactionCount, totalTransactionAmount, actualTransactionAmount, totalChargebackRecoveryAmount, totalLoanRecoveryAmount, totalMdrAmount, totalGstAmount, totalLateSettlementFee, totalSettledAmount, totalMarAmount, splitFundAmount, totalPlatformFee, otherDeductions, additionalMdrAmount, totalConvenienceFee, totalGstOnCCF, totalCashbackAmount, totalMerchantCashback, totalMerchantConvenienceFee, partnerFeeTax. Use this when user asks about a specific payout or UTR.
Get settlement list with details for a date range. Response fields: totalAmount, actualTransactionAmount, totalDeductionAmount, totalTransactionsCount, totalSettlementsCount, settledDate, utrNumber. Use this when user wants to see a list of settlements/payouts.
Get detailed information about a specific store by its ID. Response fields: storeId, storeName, terminals (each with posId, hardwareId, hardwareModel, isActive). Use this when user asks about a particular store or outlet.
List all stores for the merchant. Response fields: totalCount, stores (each with storeId, storeName, terminals: posId, hardwareId, hardwareModel, isActive). Also STEP 1 of the service ticket workflow. IMPORTANT: When used for service tickets, present stores as a NUMBERED LIST and ASK the user: 'Which store is this ticket for?' Do NOT proceed until the user selects a store.
Get transaction performance summary for a specific store over a date range. Returns all aggregate fields including transaction totals and counts. Use this when user asks about a store's sales performance or revenue.
Get full details and status of a specific service ticket by ticket number. Returns status, description, history of status changes, tracking, and feedback. Use this when a user asks about an existing ticket or wants to check ticket status.
Get today's payout/settlement summary. Returns all settlement aggregate fields including settledAmount. Use this when user asks about today's payouts or settlements.
Get transaction aggregates (totals) for a date range, grouped optionally by store, payment mode, or status. Returns all aggregate fields including counts, total amounts, and breakdowns. Use this when user asks about total sales, revenue, or transaction counts.
Get full details of a specific transaction by its ID. Response fields: transactionId, transactionDate, transactionType, amount, subreportType, reportType, isAggregator, and merchantDetails (merchantId, merchantName, storeId, storeName, posid, hardwareId). Use this when user asks about a particular transaction.
Get transactions for a specific date range. Response fields: transactionId, transactionDate, transactionAmount, storeName, storeAddress, reportType, subReportType, merchantId, posId, paymentMode. Use this when user asks about transactions between specific dates.
List existing PineAI chat sessions. Use this as the first step in the chat flow before creating a new session, matching the PineOne backend flow. Returns session ids, titles, agent ids, timestamps, and pagination.
Show all running/provisioned autonomous PineAI agents for the authenticated merchant. Autonomous agents are implemented as active AI schedules. Use this when the user asks 'show me all agents running', 'which agents are running?', 'show running autonomous agents', or similar. Do not use getAgents() for this request.
List AI schedules/autonomous PineAI tasks for the authenticated merchant. Can optionally filter by status and/or agentId. Returns schedule details including title, frequency, time, channel, state, query, and backing agent. Use this when user asks to see their schedules, automated tasks, provisioned agents, scheduled agents, or autonomous agents.
List service tickets with optional pagination and date filters. Use this when the user wants to see their existing tickets. Returns ticket number, status, subject, created date, and category for each ticket.
Pause an active schedule. The schedule will stop running until resumed. Use when user wants to temporarily stop a scheduled report/task.
Raise a service ticket for a terminal issue. This is STEP 4 — the FINAL step. Only call this AFTER the user has selected a store, issue category, and POS terminal(s) in previous steps. All 6 parameters are required strings. posIds must be comma-separated numeric IDs as a single string. Generate the subject from the issue category name (e.g. 'GPRS Connectivity Issue'). Use the user's description they provided. Use the merchant's name as createdBy. Example call: raiseServiceTicket('TERMINAL_GPRS_CON_ISSUE', '2986', '10001234,10005678', 'GPRS Connectivity Issue', 'Terminal unable to connect to network', 'Nikesh')
Resume a paused schedule. The schedule will start running again on its configured frequency. Use when user wants to reactivate a paused schedule.
Search settlements with filters like payout status. Response fields: utrNumber, settledDate, totalAmount, totalTransactionsCount. Use this when user wants to find settlements by status (e.g., 'PAID', 'PENDING', 'FAILED').
Search transactions with filters like status, payment mode, transaction type. Response fields: transactionId, transactionDate, transactionAmount, storeName, storeAddress, reportType, subReportType, merchantId, posId, paymentMode. Use this when user wants to find specific transactions by status or payment type.
Send a message to a PineAI chat session and get the AI assistant's response. Use this to interact with a PineAI agent in a conversational manner. Requires a sessionId from createChatSession.

Pinelabs One FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Pinelabs One alternatives on ChatGPT?

As of 2026-09-17, Pinelabs One competes with airpay, Cashfree, Fintoc, GoCardless, Juspay Genius, Paylindo, PayPal, Paytm Payment Gateway, Pine Labs Payment Assistant, Razorpay, Rootline, Rubikpara AI Asistan, Stripe, Yuno in ChatGPT Payment Processing & Gateways, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.