Pinelabs One

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.