Agent Tools

Get the most recent accounting sync commit for the acting user's business and sync type. Use this when you need the latest sync status plus every intended and successful count exposed by Ramp's accounting latest-sync endpoint.

Get object-level failure details for an accounting sync commit by UUID. Use this when a customer asks about failed accounting sync rows, including rows from the accounting transactions table, reimbursements table, or bills tab.

Retrieve active accounting tracking category metadata for transaction coding, such as departments, classes or business units, locations, projects, customers, and cost centers. Use GetTrackingCategoryOptions for a category's options. If passing transaction_uuid, use an actual TransactionCanonical UUID from context or a prior lookup; omit it rather than passing a placeholder or natural-language reference.

List specific departments, projects, or other options for a tracking category. Pass `query_string` to narrow by name, synonym, or provider code. Do not call this tool when you already have the exact tracking_category_option_uuid from user-provided context, suggested codings, or another tool result; pass that UUID directly to the coding tool as the option_selection. If the user message includes `tracking_category_option_uuid=...`, do not call this tool just to confirm the option. If you're coding a specific transaction or reimbursement, pass its UUID so results respect conditional filtering (subsidiary, department, location, etc.); skip it for generic lookups, including bill/invoice contexts. Categories can have millions of options — paginate via `next_page_cursor` when needed, keeping all other inputs unchanged between pages.

Mark objects as ready to sync to your accounting provider

Enroll the current business in agent cards for agentic commerce.

Fund the business's x402 wallet from a Ramp Checking Account. Before calling, use ListBusinessAccounts to obtain the source account UUID; never guess it. Confirm the exact source account and positive USD amount with the user before creating this irreversible transfer. MCP and CLI callers must provide an idempotency key. Only active Increase USD accounts are supported.

Get a one-time payment token for a fund. Handles card enrollment and purchase instructions automatically.

List funds that can be used for agent card payments. Returns eligible funds with available balance.

Pay an x402 payment request from your business's stablecoin balance. Fill the inputs from the merchant's 402 payment challenge. Returns a ready-to-send payment header to attach when retrying the original request.

Provision your business's x402 wallet after the user explicitly confirms. Returns the same sign-ready Solana wallet on repeated calls. Do not call this tool until an owner or admin confirms that the wallet should be provisioned.

Withdraw the business's x402 wallet balance to a Ramp Checking Account. Before calling, use ListBusinessAccounts to obtain the destination account UUID; never guess it. Confirm the exact destination account and USDC amount with the user before creating this irreversible transfer. MCP and CLI callers must provide an idempotency key. Only active Increase USD accounts are supported.

Run read-only SQL for aggregate business analysis. First use the analyst catalog and read the domain docs for every table in the query; those docs define supported tables, columns, joins, and metric semantics.

Aggregate AI token usage or estimated cost over a time window, grouped by caller-selected dimensions (provider, model, configuration, department, user, or API-key tag group).

Summarize connected AI providers (admin keys and OpenRouter/LiteLLM gateway connections). Use GetAiTokenSpendCurrentSpend for actual vendor spend and GetAiTokenSpendAggregates for estimated token usage and cost.

Report the business's actual trailing-30-day Ramp spend on AI vendors (card, bill, and reimbursement spend) per provider. Requires transaction, reimbursement, or bill read access.

List the dimensions and values available for AI-spend aggregate queries: providers, models, model families/facets, departments, and API-key tag groups.

Discover available analyst tables and starter SQL for aggregate business analysis. Review the catalog before writing a query, then read domain docs for every table used.

Discover supported analyst metrics and starter SQL for aggregate business analysis.

Read domain documentation for analyst.spend_facts before using it in an analyst query.

Read domain documentation for an analyst table before using it in an analyst query.

Aggregate the acting user's own AI token usage and estimated token cost over a time window, optionally grouped by provider and model.

Approve or reject a submitted bill that is pending approval. The authenticated user must be the next required approver on the bill's approval chain. Rejection is additionally allowed for bill-pay admins as an override, even when they are not the next approver. Find bills awaiting the authenticated user's approval with get-bills-for-approval. Some bills require step-up verification that agents cannot complete; in that case the error includes a redirect_url that the human user must open in a browser to finish the action there. Approving advances the bill's approval chain, exactly as approving in the Ramp web app does: depending on the business's payment-release settings, a bill that becomes fully approved with payment details and a payment date already set may proceed to payment automatically. After an approval, the response reports the bill's resulting payment state: whether any of its payments has been initiated (payment_initiated — this includes earlier partial payments; a chain-completing approval may have just added one) and the earliest such payment date (payment_date) — so you can inform the user. This tool never schedules payments or edits payment details; payment scheduling and release are managed in the Ramp web app — hand the user the bill_url returned on success.

Approve or reject an employee reimbursement request for an out-of-pocket expense. Use this tool when the user wants to approve or reject a reimbursement. Reimbursements are employee-submitted requests for reimbursement of out-of-pocket expenses. Common usage patterns: "approve this reimbursement", "reject the expense", "yes, reimburse them", "no, don't reimburse this". This tool is specifically for employee reimbursements and is NOT for approving/rejecting card transactions or unified requests (spend allocations, purchase orders).

Approve or reject a pending unified request for spend allocation (fund), purchase order, or procurement approval. Use this tool when a user wants to approve or reject a specific request they have identified or referenced. Common usage patterns: "approve this request", "reject this request", "accept the request", "deny this", "authorize this", "yes approve it", "decline this request". This tool is specifically for unified requests (spend allocations, purchase orders, procurement approvals) and is NOT for approving expenses like corporate card transactions or reimbursements. The user must have proper approval authority for the request.

Approve or reject a transaction awaiting your review. Use this tool when the user wants to approve a transaction, send it back for revisions, or require the cardholder to repay the full amount. The acting user must have the proper approval authority for the transaction. If the user provides a written justification (e.g., “reject this because the receipt is missing”), pass that verbatim via `user_reason`—do not invent your own rationale.

Get bills that are pending approval from the current user. Use this tool when the user wants to see bills they need to approve or asks about pending approvals. This returns only bills where the authenticated user is the next required approver in the approval chain. Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Get employee reimbursements pending approval by the current user. Includes policy assessment data and recommended actions.

Get requests that require the current user's review and approval. This is the approval-queue wrapper over SearchUnifiedRequests. Use it when the user is specifically asking what they need to review or approve right now. For broader lookup by vendor, owner, status, or request name, prefer SearchUnifiedRequests instead. Only handles lookups, does not take any action.

Remind next approvers for bills awaiting approval. Use this tool when the user wants to nudge approvers for specific bill UUIDs. The bills should be awaiting approval; use get-bills-for-approval first if the user has not identified the bill UUIDs.

List agent account numbers

List bank accounts

Create a manually connected bank account

Get daily balance history for a specific Ramp Checking Account. Use when the user asks about balance history for a specific account, savings account trend, checking account balance over time, or the balance trend for a specific Ramp Checking Account. This tool only supports Ramp Checking Accounts, not Investment Accounts or Managed Portfolios.

Get the balance of investment accounts for the business. Use this when the user asks about investment account balances, brokerage cash, or the current balance of Ramp investment accounts. Returns all investment accounts the business has, along with balances, status, yield, and earnings.

Get the balance of managed portfolio accounts for the business. Use this when the user asks about managed portfolio balances, managed portfolio cash, or the current balance of Ramp managed portfolio accounts. Returns all managed portfolio accounts the business has, along with balances, market value, status, yield, and earnings.

Get the balance of Ramp Checking Accounts for the business. Returns the available balance, statement balance, and other details for all Ramp Checking Accounts associated with the user's business. This includes yield/earnings information and account status. This tool is intentionally limited to the stable user-facing fields for Ramp Checking Accounts. Do not infer deprecated pending balances or current month accrued yield values from other treasury payloads when responding to the user.

Get daily balance history across all Treasury accounts for a date range.

List all Ramp Checking Accounts (wallet accounts) for the user's business. Returns account details including balances, currency, yield rate, and status. Use this tool when the user asks about their checking accounts, wallet accounts, or wants to see an overview of their Ramp Checking Accounts.

List all Treasury accounts (Ramp Checking Accounts, Investment Accounts, Managed Portfolios).

List wallet transfers for the user's business Ramp Checking Accounts. Returns a list of transfers including deposits, withdrawals, and other transactions with details like amount, status, and dates.

Request funds for a banking account

Create a new draft bill for an existing vendor. Use search-vendors to resolve a vendor name to vendor_uuid first. This creates only a draft: it does not submit the bill, start approvals, schedule it, release it, or initiate a payment. Use update-draft-bill for later edits and submit-draft-bill only after the user confirms the completed draft is ready.

Create a pending vendor/payee record. Call SearchVendors first with include_draft=true. Reuse a suitable existing vendor, including a pending vendor, instead of creating a duplicate. Never create a duplicate to work around an existing vendor whose status is INACTIVE — an admin must re-enable that vendor instead.

Get aggregate dollar amounts for bills matching the given filters. Examples: total unpaid amount, total pending amount. Use when users ask things like "How much do we owe in bills?" or "What's our total outstanding bill amount?". Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Retrieve comments from a bill's comment thread. Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Get comprehensive details about a specific bill including payment status, approval status, and all metadata. This tool retrieves submitted bills only. For draft bills that have not yet been submitted, use get-draft-bill-details instead. Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Retrieve the full modification and approval history of a bill, including status changes, approval actions, and creation details. Returns a chronological event log — creation, submission, each approval-chain action with actor and timestamp, and deletion. Use it to answer questions like "who approved this bill?". Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Retrieve invoice file attachments (PDFs/images) for a submitted bill. Returns the source documents backing the bill: for each attachment, the filename, type, and a time-limited download URL (the URL expires after about 3 days). Draft bills are not supported: draft attachments are not retrievable through agent tools. get-draft-bill-details returns draft metadata and a link to the draft page in the Ramp web app, where attachments can be viewed. Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Returns the count of bills matching specified filters. Use this to answer questions like "How many bills are pending approval?" or "How many overdue bills do we have?". Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Get the current payment and approval status of a specific bill, including any required next actions. Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Get rich details for a draft bill. Returns compact draft-bill metadata by default. When requested, it also returns the draft's full editable field set inline, in the shape accepted by the draft update tool. Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Retrieve details of a recurring bill template including vendor, amount, recurrence schedule, and next payment date. Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Retrieve details for a specific vendor agreement/contract by UUID. Returns contract metadata, terms, line items, contract owners, documents, linked spend requests, and renewal history.

Get bulk vendor document upload progress and current document review state. Use this after `BulkUploadVendorDocuments` to inspect the batch job status, understand whether any documents still need manual review, and inspect the current document/vendor matching and extracted tax details.

List and filter bills with optional search, pagination, and status filters. Returns bills for the current user's business. When called with no parameters, returns the most recent bills. Supports optional text search across vendor name, invoice number, and payment ID. Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

List and filter vendor agreements/contracts across the business. Returns agreement details including dates, values, renewal status, line items, and days remaining. All filters are optional — omit all to list all agreements, or combine filters to narrow results.

Search for bills using natural language queries like vendor names, amounts, or invoice numbers. Submitted and active draft bills may both be returned unless include_drafts=False. To look up only a draft bill, use get-draft-bill-details instead. Check each result: when is_draft is true, follow up with get-draft-bill-details; otherwise use get-bill-details. Bills in Ramp have two stages: draft bills (created/uploaded but not yet submitted; use the draft-bill tools) and bills (submitted; they move through approval, then scheduling, then payment). A draft keeps the same ID after submission, but draft-only tools stop working on it once submitted.

Search for vendors (payees) within the business by name. This tool searches for vendor records using both fuzzy SQL matching (trigram similarity + substring) and semantic (vector) search. Use this to find vendor IDs when you need to: - Look up a vendor by partial name - Find the correct vendor UUID for further analysis - Discover vendors similar to a given name The search is scoped to the current business context.

Submit a ready draft bill for approval. The draft must be complete (vendor, amount, payment method, and vendor contact set) - read it with get-draft-bill-details first and fill gaps with update-draft-bill. Submission is accepted asynchronously: the bill keeps the same ID as the draft, so verify completion with get-bill-status using the same ID. Once created, the bill enters its approval chain automatically. Some submissions require identity verification that agents cannot complete; in that case the error includes a redirect_url that the human user must open in a browser to finish submitting in the Ramp web app. Payment scheduling and release are done in the Ramp web app, not through tools. Submit only when the user has reviewed the draft and their current message clearly asks to submit that specific draft. A request to create, edit, or review a draft is not authorization to submit it.

Update a draft bill: its fields, line items, accounting category coding, and draft payment details. Call get-draft-bill-details first and echo its `version` back on this call; if the draft changed in between, the update is rejected and the error includes the current version to retry with. Omitted fields are left unchanged; set a nullable field to null only to intentionally clear it. `provisional_bill_id` takes the draft bill's UUID. Tracking-category and option ids may be passed as UUIDs from get-tracking-categories / get-tracking-category-options. Draft bills that have already been submitted can no longer be edited. Draft bills with retainage (withholding) are not supported by this tool.

Activate a card by its last four digits. Activates an unactivated card for the user. If the card is a physical card awaiting delivery confirmation, call this tool first without confirm_delivery to detect the state, then call again with confirm_delivery=True after the user confirms the physical card has arrived.

Retrieve funds (cards or budgets) and their balances, restrictions, locks, owners, or permitted spend. For a named person's funds, resolve their UUID with GetOrgChart and pass user_uuids. For the current user's funds, use MY_FUNDS. Search by fund name with search_by_fund_display_name or look up a known UUID with fund_uuid. When balance_info is returned, treat its remaining balance as authoritative for cleared charges and pending authorizations. Do not subtract those amounts again. Never infer that a booking is included merely because it is confirmed: a postpaid booking with no charge or pending authorization is a future charge and has not yet reduced the remaining balance.

Issue one-off funds (spend allocations) directly, bypassing approval flows. Use this tool when an admin wants to create new funds for one or more users with a specific amount, interval, and optional restrictions. This creates virtual-card-only spend allocations outside of spend programs. The acting user must have the SPEND_ISSUE_SPEND_BYPASS_APPROVAL permission.

Increase the spending limit on a fund (spend allocation) or card. Supports temporary (resets at the next interval) and permanent increases. Call only when the user's current message clearly requests an increase for the specific fund or card and specifies temporary or permanent. A declined transaction, budget question, or currency correction is not authorization to increase a limit. Do not infer or default the increase type.

List non-terminated cards for the current user or a visible target cardholder, including activation status, lock state, and shipping metadata. IMPORTANT: For the current user's unlock request, call this tool first to check spendability and locks. If cardholder_user_uuid targets another user, never open the acting user's feed. For locks, follow remediation_action. Use LockOrUnlockCard only when can_lock_or_unlock=true. GET_ATTENTION_FEED means resolve the task there, not through LockOrUnlockCard; re-list until blocking_task_count=0 and is_spendable=true. Do not use GetUserFunds for card unlock requests; funds and cards are different.

Lock or unlock a card the acting user is authorized to manage. Locking prevents all transactions on it until unlocked. Lock only when the user's current message clearly requests locking the specific card. Do not infer a lock request from suspicious activity. Unlocking does not require additional confirmation. If this returns FraudLockDetected, use UnlockFraudLockedCard instead.

Lock or unlock a fund (spend allocation) at the fund level, affecting all members. Lock only when the user's current message clearly requests locking the specific fund. Do not infer a fund lock from a declined transaction or budget discussion. Unlocking does not require additional confirmation.

Lock or unlock a specific member's access to a fund (spend allocation). Lock only when the user's current message clearly requests locking the specific member's access to the specific fund. Do not infer a member lock from a declined transaction or suspicious activity. Unlocking does not require additional confirmation. If this returns FraudLockDetected, use UnlockFraudLockedCard instead.

Unlock a card that was locked due to a suspicious transaction. Requires the user to confirm they recognize the flagged transaction.

Update spending category restrictions (whitelist or blacklist) on a single fund. Manages spend types (e.g., Restaurants, Travel), not individual merchants.

Update merchant restrictions (whitelist or blacklist) on a fund (spend allocation). - Add or remove merchants from the allowed merchants list (whitelist) - Add or remove merchants from the blocked merchants list (blacklist) Use this when a user wants to: - Allow specific merchants on a fund (add to whitelist) - Block specific merchants on a fund (add to blacklist) - Remove merchants from the allowed or blocked lists

Retrieve flight, hotel, and car rental booking summaries for the user. Returns confirmed bookings and pending requests, with unsuccessful requests available via include_failed; check the status field and call GetBookingDetails for one entry's detailed state.

Get a detailed explanation of why a card transaction was declined. Returns the reason, remediation actions, user notification, and transaction details. Only valid for already-declined transactions.

Retrieve the company's office locations and addresses. Use this to find office addresses when searching for hotels near an office or determining travel destinations. The two shapes are complementary: ``office_locations`` has coordinates but no street address, and ``company_address`` has a street address but no coordinates.

Fetch trips for the acting user with optional filters.

List merchants

Search for flights and return policy-tagged offers ready to quote. Before first use in a conversation, load and follow the ramp-book-flight skill when available. Tell the tool what to search (route + dates), or give it a job_id - never both. The default call blocks for ranked, policy-tagged offers; set wait_for_results=false only to start asynchronously and receive a job_id immediately instead, then use the same job_id on a later call to retrieve the final results. A call with job_id reads cached results and never starts another provider search. Use job_id alone to read the first page, add cursor to read the next page, add preferences to change the filtered or ranked view, or add sort_key to change its order; omit cursor when making either change so the new view starts at its first page. For a round trip, start the search with return_date. The first response contains OUTBOUND offers with is_round_trip=true and round-trip totals. Choose an outbound offer, then call with its job_id and outbound_offer_id to get matching RETURN offers. The chosen return offer's id identifies the complete outbound-and-return itinerary for booking. To filter return offers (e.g. by airline), pass the same job_id and outbound_offer_id with the new preference - do not start a new search, which discards the selected outbound flight and reruns the entire provider query. A completed outbound response includes web_search_url for the cached search in Ramp Travel. Fare options are nested under their flight, and a nested fare option id can be selected for return offers. Search preferences are cabin_class, airlines, max_stops, only_split_tickets, preferred_departure_time_window, preferred_arrival_time_window, and avoid_red_eye_flights; omitted preferences retain their prior values, and applied_preferences reports what each response used. Do NOT use this tool to change, modify, cancel, or rebook an existing booking.

Search for merchants by name. Returns matching merchant IDs, UUIDs, names, categories, and domains.

Create a new department in the company. Department names are unique within the business (case-insensitive). If a department with the requested name already exists, it is returned instead of creating a duplicate.

List all departments in the company. Returns the departments available in the user's business, which can be used as inputs to workflows that require department references. Each department includes organizational metadata: its owners (managers), active member count, and managing external firm, if any.

Get org chart for a user, including reporting chain and direct reports. This tool provides comprehensive org chart visibility including: - The user's position in the organization - Their direct reports (team members) - Their reporting chain (managers up the hierarchy) Use this tool whenever the user asks anything about their manager, team, or direct reports.

Get the current user's details. Returns multiple results for users that are part of multiple businesses. When authenticated via an agent key, also returns the active agent key identity.

List and search users across the entire business. Returns all users in the organization matching the given filters. Supports searching by name (partial match, case-insensitive), filtering by department or location, and pagination. Results include active and inactive users — check the is_inactive field to distinguish. Use department_ids or location_ids (lists of UUIDs from the departments or locations tools) to narrow results.

Rename an existing department in the company. Department names must be unique within the business (case-insensitive).

Match a user name to a Ramp user in the context of a transaction, for adding as an attendee. Returns users from the business ranked by relevance to the given transaction (recent attendees and teammates appear first). If no transaction ID is provided, the user's most recent transaction is used as context. The search is case-insensitive and matches partial names.

Get an answer to a question about the expense policy or funds (amount, restrictions, etc). Use this tool when the user asks about expense policy rules, spending limits, fund restrictions, or whether certain purchases are allowed under company policy.

Return the authenticated user's homepage attention feed. Use this tool to see what needs the user's attention right now: pending approvals, missing receipts, overdue reviews, signatures, and similar action items that appear on the Ramp homepage. By default, the tool returns the default homepage sections with compact LIST-hydrated task rows. To fetch more from a section, pass that section's section_type and next_cursor back in sections. For own-card GET_ATTENTION_FEED remediation, use this as the canonical task feed. blocking_effects describes a task type's possible sanction, not proof that an item caused the active lock. Use browser_handoff for user action in Ramp. For an available CompleteTransactionRevision, inspect or edit the transaction and call it with a nonblank reason. Re-read both tools and continue relevant overdue tasks; success requires the task absent, blocking_task_count=0, and is_spendable=true. Pending verification is not an unlock.

Report a capability that is missing from the available Ramp tools. Use this when the user's request cannot be completed with the available Ramp tools. Describe the user's goal and the capability that would be needed.

Publish the active policy for a standalone Agent Wallet

Post a comment on a Ramp object (transaction, bill, reimbursement, etc). If there is any ambiguity as to whether the user's message is meant to be posted to the thread, ask them for confirmation first: 'Do you want me to post that as a comment reply on your [XYZ] transaction/reimbursement/bill/etc?'. How can you determine if the user's message is meant to be a reply to a comment? - If the only other messages in the conversation history are notifications about comments or mentions in Ramp, that is a very strong signal that the user's most recent message is meant to be a reply to the comment thread. In this case, you may use this tool immediately to post the comment without confirmation. - If a recent assistant message is a notification about a comment or mention, that is a strong signal that the user's most recent message is meant to be a reply to that comment. Even if their reply seems irrelevant or unrelated to Ramp, you may ask "Would you like me to post that as a comment on your...?" - prefer asking the user instead of refusing to serve the request at all.

Tool for searching Ramp's help center documentation using RAG (Retrieval Augmented Generation). This tool performs semantic search across help center articles using embeddings. Trusted business-scoped calls receive the complete matched articles; unscoped and external Developer API calls receive focused snippets. The tool: 1. Fetches relevant articles from the help center 2. Chunks articles into smaller semantic units 3. Uses embedding similarity to find the most relevant sections 4. Returns top K results with their source articles Some internal articles have no public URL (an empty ``url``). Never construct or guess a URL for those articles. IMPORTANT: If you have other tools that can actually perform the action a user is asking about, you should use those tools instead of or in addition to providing help center information. For example, if a user says "how can I upload a receipt", you should tell them they can upload a receipt in the chat directly, even if you also find a help center article that explains how to upload receipts in the web app. Use this tool when you need to: - Find specific information within help articles - Get concise, focused answers from documentation - Minimize token usage while maintaining relevance - Answer questions about Ramp products and features

Get comprehensive details about a specific purchase order. Use this with the exact purchase order UUID returned by SearchPurchaseOrders or supplied by page context. Never pass a purchase order number, placeholder, or guessed value.

Get detailed information about a specific unified request the acting user can view. Use this when the user asks for more detail about a specific spend request, purchase order, fund request, or other unified request - for example its current status, approval chain, comments, activity timeline, or agent-generated reports. This works both after SearchUnifiedRequests or GetRequestsToReview and for any other unified request the user can already access via page context, tagged objects, or a known unified_request_id.

Delete an abandoned procurement draft owned by the acting user.

Create or update a procurement draft and return the current visible form state.

Refresh and canonically revalidate a procurement draft's visible form state

List published procurement spend programs the agent can draft against.

Submit a procurement draft after explicit user confirmation.

Close one or more purchase orders with a specified reason. Use after confirming the user wants the listed POs closed. Purchase orders must not already be closed or archived. The user must have permission to close every purchase order in the request.

Reopen multiple closed purchase orders. Use only after confirming the user wants the listed POs reopened. This does not archive or delete POs; reopening restores each PO to its computed active lifecycle status when allowed. The user must have permission to reopen every purchase order in the request.

Search for purchase orders using structured purchase order filters.

Search for unified requests using free-text and structured request filters. Use this to find existing purchase orders, fund requests, procurement requests, or approval-only requests by vendor, request name, owner, requester, status, type, exact request number, approval date, department, or whether they require action. Use GetRequestsToReview when the user is specifically asking what they need to approve right now. Use GetUnifiedRequestDetails once one request has been identified.

Cancel the payment on a reimbursement that has been approved but not yet paid out.

Create a draft reimbursement from a receipt UUID. Pass amount/currency_code/transaction_date/merchant to skip OCR.

Delete a reimbursement by UUID. Deletion is permanent and only allowed for reimbursements the acting user is permitted to delete (their own drafts, or others' if they have write access). Reimbursements that have progressed too far in the payment lifecycle cannot be deleted; use CancelReimbursementPayment for approved-but-unpaid reimbursements.

Duplicate an existing reimbursement as a new draft.

Edit reimbursement fields (amount, currency, date, merchant, memo, funds, accounting categories, split line items, custom records, trip, attendees). Omitted fields stay unchanged; null/[] clear when editable.

Estimate the reimbursement amount for a given mileage distance based on the user's company rates.

Estimate the per diem reimbursement amount for a trip given start/end dates and optional meal deductions.

Get approved and failed reimbursements that would be affected by a bank account currency change.

Retrieve receipts attached to a reimbursement.

Search and retrieve reimbursements with filters for users, text search, amount ranges, tags, date ranges, approval status, and policy assessments.

Get reimbursement history for the current user. `limit` takes precedence over `up_to_days` so if you want to get all reimbursements in a given time frame, do not specify `limit`. `include_rejected` controls whether to include rejected reimbursements in the results. By default, rejected reimbursements are excluded. `include_drafts` controls whether to include draft reimbursements in the results. By default, drafts are excluded. `use_submitted_date_ordering` controls the ordering of results. By default (False), results are ordered by transaction_date. Set to True to order by submitted_date instead. If the user did not ask for a specific number of reimbursements or a time frame, assume they want to see the latest 10 reimbursements. Read each amount from `amount_decimal`, which is already in `currency`'s major unit and needs no arithmetic. Ignore `amount_cents`; it is the same amount in minor units, kept only for backwards compatibility.

Revert a rejected reimbursement back to draft state so it can be edited and resubmitted. This does NOT submit the reimbursement — it only moves it from REJECTED to DRAFT. After resubmitting, use EditReimbursement to make changes and SubmitReimbursement to submit again.

Search reimbursements across a business, optionally filtering to a specific user's reimbursements.

Search reimbursements with text-based filters and structured filters. Supports filtering by: - User name (e.g., 'John Smith') — resolved automatically, defaults to current user if not specified - Accounting coding selections (tracking categories) like Department, Cost Center, Class, GL Account - Merchant name, spend allocation name (resolved from text automatically) - Reimbursement status (DRAFT, PENDING, APPROVED, etc.) - Date range and text search The tool resolves text queries to internal IDs automatically via the search tag service. Results are scoped to the current user's business.

Submit a draft out-of-pocket reimbursement for approval. If the submission fails, the agent should follow up with the user based on the error returned from the endpoint. If it is due to outstanding missing items, the agent should recheck missing_items via the GetReimbursements tool and provide suggestions for the user. If only nonsupported missing items are present (trip, attendee, mileage_locations), the agent should provide the reimbursement_link URL as a clickable link in the response.

Complete a revision-requested transaction as its cardholder. Use this after the cardholder has addressed the requested changes and explicitly asks to mark the transaction revision complete. The completion refreshes the corresponding task and starts Task Platform's sanction-lifting workflow.

Edit a transaction field (memo, funds, accounting categories, trip, attendees). Returns the updated transaction, remaining missing items, and a transaction_link for fields the API cannot edit.

Fetch trips that could be relevant to the current transaction. Returns ongoing, upcoming, and recently completed trips for the acting user.

View all details, memos, funds, and receipts for a specific transaction. Read the amount from `amount_decimal`, which is already in `currency`'s major unit and needs no arithmetic. Ignore `amount_cents`; it is the same amount in minor units, kept only for backwards compatibility.

Check what receipts, memos, or accounting items are missing from a specific transaction.

Get AI-suggested memo/note options for a specific transaction.

Search and retrieve individual card transactions and workflow details for the user's business, including reconciliation dates (cleared_at, settlement_date, accounting_date, synced_at) and, via details_to_include_in_response=['submitted_items'], the selected accounting categories. Use analyst tools instead for aggregate spend analysis, totals, trends, or group-bys when analyst tools are available. Declined transactions are excluded by default; pass state='declined' to include them.

Flag a transaction as having no receipt. Should be called whenever the user says "OOPS" or if the user says something along the lines of "I did not receive a receipt ...". If the user already flagged the transaction as having no receipt, then you may need to call the ProvideNoReceiptReason tool.

List all available spend categories. Returns category IDs and names.

Submit a reason explaining why a transaction has no receipt.

Request that a cardholder repay a transaction. This is the REVIEWER / APPROVER action: the acting user must be an approver or manager for the transaction, not the cardholder themselves. The tool marks the transaction as repayment-required and notifies the cardholder, who can then accept, reject, or complete repayment through their own flow. This tool does NOT execute payment (ACH, payroll, debit-card, etc.). It only creates the repayment request so the cardholder sees an actionable task. Use when a reviewer or manager says things like: - "Request repayment on this transaction" - "Mark this as needing repayment" - "Require the employee to pay back this charge" - "Flag this transaction for repayment" If the user is the cardholder wanting to repay their OWN transaction, use RepayTransaction instead — that tool provides the self-service repayment URL.

Split a transaction into line items, or update an existing split

Set a fund's maximum amount for one transaction. Use this for decline action INCREASE_TRANSACTION_AMOUNT_LIMIT or requests about a per-transaction, single-transaction, or max-expense limit. Use LimitIncrease for the period total. Set any positive value to raise or lower the cap. AP-card and bill-pay funds are unsupported. Provide exactly one of spend_allocation_id or card_id.

Compatibility route for callers that have not migrated to SetTravelerLoyaltyProgram.

Create a new trip for the acting user. Do not call this solely as a prerequisite for booking a flight or hotel; SubmitFlightBooking and SubmitHotelBooking automatically select or create a trip when trip_id is omitted. If the user explicitly asks to create a named trip in addition to booking, call this once and pass the returned trip_uuid as trip_id to every related SubmitFlightBooking and SubmitHotelBooking call.

Get itinerary, stay, or rental details plus request status, amount, payment timing, cancellation state, associated spend, error, and approval information for one result from GetBookings.

Resolves locations (airports/cities) available for booking a flight from user intent. Preserve the user's location wording in ``query``. When the user names a city or metro area such as "NYC", set ``location_type=city``. A returned city ``search_code`` searches all supported airports in that metro; do not ask the user to choose one airport when a city result is available. Call this before SearchFlights for every departure or arrival location that the user did not provide as an exact airport IATA code. If the results contain multiple plausible locations, present the choices and wait for the user to clarify; never choose a location on their behalf. Do not infer a location from profile data, an area code, or a broad description such as "somewhere warm." Returns locations where flights can be booked from or to, which may include: - Individual airports (e.g., JFK, SFO, LAX) - City groups with multiple airports (e.g., NYC includes JFK, LGA, EWR) - Major travel destinations with flight availability Pass a result's ``search_code`` straight into SearchFlights departure/arrival. Cities search every airport in the metro area; airports search just that airport.

Fetch available room-rate options for one selected hotel from SearchHotels. Use this after the user picks a hotel from SearchHotels results and before booking. Every current room group and its rates for the stay are returned in all_rates; the returned rate.id values are the exact IDs to pass to SubmitHotelBooking. These rates are current options, not quotes - wait for the traveler to select one exact rate. When the result's all_rates_out_of_policy is true, every rate at this hotel is out of policy for the stay: tell the traveler, prefer offering an in-policy hotel from the SearchHotels results, and proceed with this hotel only if the traveler explicitly chooses to - booking will then require an oop_reason at SubmitHotelBooking.

Retrieve traveler profile information including name, email, phone, date of birth, gender, known traveler number (KTN/TSA), redress number, and loyalty programs. For delegated bookings, first resolve the traveler with GetAllReducedUsers/list-users, then pass that UUID as traveler_user_id. Omit traveler_user_id for self-booking.

List saved loyalty programs from the user's traveler profile. Use this directly for loyalty-only list/show/check requests; do not call GetTravelerProfile first.

Remove a saved loyalty program from the user's traveler profile.

Search hotels using the canonical Ramp web inventory and policy flow. Before first use in a conversation, load and follow the ramp-book-hotel skill when available. Provide location_query (city, neighborhood, address, landmark, or office) plus check_in_date and check_out_date. API calls run synchronously by default and return ranked hotels - each with at most one summary rate - plus policy_summary, total_count, and web_search_url. Results are paginated from a cached result set: pass the returned next_cursor as cursor to fetch more hotels without triggering a new provider search; never construct or edit a cursor. Put chain requests in filters.chain_names and reserve hotel_name for one exact property; a specific hotel_name uses the targeted direct-hotel path. Passing wait_for_results=false explicitly opts into an asynchronous kickoff that returns status='searching' with a search_id to resume by passing that search_id on a later call. To book from these results, pass the selected hotel id to GetHotelRates, then the selected rate id to SubmitHotelBooking with the same traveler and stay dates.

Set one loyalty program on the user's traveler profile by program name and loyalty number. If it already exists, update its loyalty number. After success, continue the active workflow when it requires refreshed data; otherwise tell the user it is saved.

Book a selected flight offer. Two-step flow: call without confirm for the authoritative preview (itinerary, price, in-policy status, and required approvals) without booking. When no fund is supplied, the preview uses the recommended eligible fund, if one exists, to determine required approvals. Then call with confirm=true and the previewed expected_total_amount (copied verbatim, digits and decimal point only, no currency symbol) only after a new, explicit user-authored response approves that latest preview. If the fare changes, preview the new total and obtain fresh approval before confirming. flight_offer_uuid is the literal id from search: the outbound flight for one-way, the return flight for round trips (it carries both legs), or a fare option's id to book that fare. On confirmation, pass exactly one funding choice: spend_allocation_id with an eligible fund UUID from the preview, or request_new_fund=true with reason set to the trip purpose. If the chosen flight is out of policy, you MUST collect an oop_reason from the traveler and pass it here. Before previewing or confirming, call GetTravelerProfile (passing the same traveler_user_id from search for delegated booking); if has_profile is false, collect the traveler's identity details and call UpdateTravelerProfile first. For changes or cancellations, use the Ramp web app.

Preview or confirm cancellation of an existing flight booking. Always call with ``confirm=false`` first. That call is read-only and returns the complete itinerary, fresh authoritative terms, and a ``preview_id``. Only after a new, explicit user-authored approval of that latest preview may you call again with ``confirm=true`` and the exact ``preview_id``. Earlier cancellation intent, standing approval, or instructions not to ask questions are not confirmation. Atlas- and Duffel-booked flights are supported. Confirmation refetches the canonical details used by the Ramp web flow and refuses to cancel if any term changed. The action always cancels the entire booking; partial passenger or leg cancellation is not supported.

Book a selected hotel rate. Two-step flow: call without confirm for the authoritative preview (price, policy, and required approvals) without creating a booking. When no fund is supplied, the preview uses the recommended eligible fund, if one exists, to determine required approvals. Then call with confirm=true and the previewed expected_total_amount (copied verbatim, digits and decimal point only, no currency symbol) only after a new, explicit user-authored response approves that latest preview. If the rate changes, preview the new total and obtain fresh approval before confirming. Use the exact hotel_id from SearchHotels and rate_id from GetHotelRates. On confirmation, pass exactly one funding choice: spend_allocation_id with an eligible fund UUID from the preview, or request_new_fund=true with reason set to the trip purpose. If the chosen hotel rate is out of policy, you MUST collect an oop_reason from the traveler and pass it here. Before previewing or confirming, call GetTravelerProfile (passing the same traveler_user_id for delegated booking); if has_profile is false, collect the traveler's identity details and call UpdateTravelerProfile first. If the user wants to change or cancel an existing reservation, direct them to the Ramp web app.

Preview or confirm cancellation of an existing hotel booking. Always call with ``confirm=false`` first. That call is read-only and returns fresh authoritative terms plus a ``preview_id``. Only after a new, explicit user-authored approval of that latest preview may you call again with ``confirm=true`` and the exact ``preview_id``. Earlier cancellation intent, standing approval, or instructions not to ask questions are not confirmation. Confirmation refetches the canonical details and refuses to cancel if any material hotel cancellation term changed. This tool always cancels the entire hotel booking; use the flight cancellation tool for flights.

Compatibility route for callers that still update a saved loyalty program by ID.

Update traveler identity and contact profile details. Never use for loyalty-only requests; use dedicated traveler loyalty program tools instead. For delegated bookings, first resolve the traveler with GetAllReducedUsers/list-users, then pass that UUID as traveler_user_id. Omit traveler_user_id for self-booking.