add_contact
ChatGPTSaves someone to the user's Versine contacts by name and mobile number or email (give exactly one of those), so you can pay or ask them by contact ID. Someone on Versine is saved as themselves; anyone else is saved for the user, and paying them sends a link to claim the money. Adding someone never trusts them. Someone already saved stays as they are. Counts as a lookup, like paying someone by number. Needs this assistant to be allowed to send or request money.
ask_to_settle
ChatGPTCreate a request for payment to a recipient identified by the input schema. Someone the user doesn’t let assistants ask on their own waits for the user to approve it in the Versine app (approval_required, with an approval_id); nobody is asked until then. A successful request record is not a completed payment or proof the recipient received a notification. Reuse the original idempotency_key and identical input for a retry of the same operation; it also returns what the user decided.
ask_to_settle_group
ChatGPTCreate requests for payment to several people on Versine at once, one per item. All or nothing: if anyone can’t be asked, nobody is, and each item says why (group_refused for those who could have been), so you can fix them or leave them out and call again. Anyone the user doesn’t let assistants ask on their own waits for the user to approve them in the Versine app (approval_required, one approval_id for all of them); the rest are asked at once. A request record is not a completed payment or proof the recipient received a notification. Reuse the original idempotency_key and identical input for a retry of the same operation.
cancel_request
ChatGPTCancels a request for money this assistant sent (ask_to_settle or ask_to_settle_group) that nobody has paid or declined yet, by its request_id: the person can't pay it anymore. Canceling one that's already canceled changes nothing.
find_contact
ChatGPTFinds people in the user's Versine contacts by name, mobile number or email (give exactly one). Answers only with the user's own contacts (at most 10), as list_contacts shows them; it never says whether a number or email belongs to someone else. A number or email counts as a lookup, like paying someone by number. If the user has no contacts yet, the answer has import_contacts_url: suggest they import their phone's contacts in the Versine app, and give them that link to open on their phone.
get_balance
ChatGPTRead the connected Versine account's dollar balance: what the user can spend now.
get_permissions
ChatGPTRead what this assistant may do for the user. This read does not change permissions or guarantee a later payment will succeed.
get_request_approval
ChatGPTRead an approval that ask_to_settle, ask_to_settle_group or schedule_request returned (approval_id), to see whether the user approved it, and each person’s request or schedule once they did. Only this assistant’s own approvals.
get_status
ChatGPTRead a payment's current status by payment_id. completed confirms completion; pending means sent; awaiting_approval means waiting; scheduled means a one-time payment set up for later, waiting for its time; canceled, for one of those, that the user canceled it before then. Use this to resolve an uncertain outcome or check a payment after approval.
list_activity
ChatGPTList recent account activity and the status of payment and request records. Use this to find a record or reconcile an uncertain outcome.
list_contacts
ChatGPTFind people in the user's Versine contacts, with the contact IDs used for payments and requests. A trusted flag describes the contact, not a completed payment. needs_us_phone marks someone who can't be paid until the user gives you their US mobile number; it only matters when the user wants to pay them. If the user has no contacts yet, the answer has import_contacts_url: suggest they import their phone's contacts in the Versine app, and give them that link to open on their phone.
list_my_actions
ChatGPTLists what this assistant did with Versine, newest first, as the user sees it on this assistant's page in the app: each request it made, and whether it was allowed, waited for the user, or was refused.
list_request_schedules
ChatGPTLists the user's scheduled and repeating requests for money (schedule_request), newest first: who, how much, how often, and when the next request is made.
list_scheduled_settle_ups
ChatGPTLists the user's scheduled payments, newest first: who each one pays, how much and how often (or once, at a later time), the next payment date and whether it's active or paused. It includes the ones this assistant proposed (schedule_settle_up) that the user hasn't set up yet, as waiting_for_user, one-time payments set up for later that haven't run yet, as scheduled, and payments to people not on Versine (paid by a link Versine texts or emails), which can't be paused here. Only the user can resume or stop one for good, in the Versine app.
pause_scheduled_settle_up
ChatGPTPauses one of the user's scheduled payments, by its ID from list_scheduled_settle_ups: nothing is paid until the user resumes it in the Versine app. This assistant can pause one on its own, since pausing only stops money; only the user can resume, change or stop one for good. Pausing one that's already paused changes nothing.
schedule_request
ChatGPTAsk one or more people on Versine for money later or on repeat: once at a set time, or every day, week or month. Versine sends each request when it is due; nothing moves until each person pays it themselves. All or nothing: if anyone can’t be scheduled, nobody is, and each person’s result says why. Anyone the user doesn’t let assistants ask on their own waits for the user to approve them in the Versine app (approval_required, one approval_id for all of them); the rest are scheduled at once. The user is told and can stop it in the Versine app, and the person asked can tell Versine to stop asking them. Reuse the original idempotency_key and identical input for a retry of the same operation.
schedule_settle_up
ChatGPTSchedules a settle-up for later: one payment at a later time (period once: in 3 hours, or Friday at 17:00 on the user's clock), or a schedule (Versine pays someone a fixed amount every day, week or month, like rent), starting now or at a time you give. Pay several people on the same timing in one proposal with items (each with their own amount): the user approves them all at once (they can take someone out before they do). All or nothing: if anyone can't be paid, nothing is proposed and skipped says who and why, so you can fix them or leave them out and call again. The recipient is one of the user's contacts, or someone by their US or Canadian mobile number (or email) and name (this assistant must be allowed to send money). Never a bank account: the user withdraws to their bank themselves. Someone not on Versine gets a text or email with a link to claim each payment's money: for a one-time payment Versine sends it at the time you give, and for a weekly or monthly schedule the first link goes when it starts (later payments go where they claimed the first); not daily. Some one-time payments (period once) are scheduled at once instead of proposed (status scheduled, with a payment_id): Versine pays them at their time, unless one needs the user's approval by then, when it waits for it (awaiting_approval); if this assistant may no longer pay at all, it fails and the user is told. The user can cancel one before its time. Follow it with get_status (payment_id) or list_scheduled_settle_ups. Anything else is a proposal: nothing is paid until the user reviews and approves it in the Versine app. With items, payments says which were scheduled and which went into the proposal. Tell the user which were scheduled and which wait for their approval. You can't change a proposal or a scheduled payment: to set up something different, call again with a new idempotency_key. Repeating the call with the same idempotency_key returns where it stands.
settle_up
ChatGPTSubmit one payment from the connected Versine account, subject to the user approving it through the Versine app. Returns the actual payment status and any required next step. Reuse the original idempotency_key and identical input for a retry of the same operation. Versine only pays US and Canadian phone numbers: a number outside the US and Canada, or a contact with no US or Canadian number and no email on file, is refused with recipient_phone_not_us (recipient_no_phone_or_email when the contact has neither). Then ask the user for their US or Canadian mobile number or email address, save it to the contact with update_contact, and try again.
settle_up_group
ChatGPTSubmit payments to several people at once from the connected Versine account, subject to the user approving them through the Versine app. All or nothing: if anyone can't be paid, nothing is sent, and each item's code says why (group_refused for those that could have gone); fix them or leave them out and call again. Reuse the original idempotency_key and identical input for a retry; if a call was interrupted, check list_activity before calling again. Versine only pays US and Canadian phone numbers: a number outside the US and Canada, or a contact with no US or Canadian number and no email on file, is denied with recipient_phone_not_us (recipient_no_phone_or_email when the contact has neither). Then ask the user for their US or Canadian mobile number or email address, save it to the contact with update_contact, and try again.
stop_request_schedule
ChatGPTStops a scheduled or repeating request this assistant made (schedule_request), by its schedule_id: no more requests are made. Requests it already sent stay open; cancel_request doesn't take those back. Stopping one that's stopped already changes nothing.
submit_feedback
ChatGPTTell the Versine team about anything that was hard, broken, confusing or missing, for you or for the user: a tool that failed or answered wrongly, a step the user couldn't finish, a refusal that didn't make sense, or something you wished a tool could do. Please send it whenever you or the user run into a difficulty, even a small one; it goes straight to the team and helps fix it. Set priority by how much it gets in the way. It doesn't reach the user's support inbox or change anything in their account.
update_contact
ChatGPTSaves a US or Canadian mobile number or an email address (or both) for one of the user's contacts who isn't on Versine, so they can be paid. Use it when settle_up refuses someone with recipient_phone_not_us (their only number isn't a US or Canadian number) or recipient_no_phone_or_email (nothing on file): ask the user for the number or email, save it here, then pay again. Only a number or email the user gave you. Versine only pays US and Canadian numbers; an email pays only the Versine account it belongs to. What was saved before stays. Not for someone on Versine (paid by their account), someone the user trusts, or a contact that already has 10 numbers (or 10 emails): those are invalid_state. Needs this assistant to be allowed to send or request money.
add_contact
Claudeask_to_settle
Claudeask_to_settle_group
Claudecancel_request
Claudefind_contact
Claudeget_balance
Claudeget_gifts
Claudeget_permissions
Claudeget_request_approval
Claudeget_status
Claudelist_activity
Claudelist_contacts
Claudelist_my_actions
Claudelist_request_schedules
Claudelist_scheduled_settle_ups
Claudepause_scheduled_settle_up
Claudeschedule_request
Claudeschedule_settle_up
Claudesettle_up
Claudesettle_up_group
Claudestop_request_schedule
Claudesubmit_feedback
Claudeupdate_contact
Claude