Build and test your Yuno integration from your assistant. Create payments, customers, subscriptions and payment links as you integrate, ask questions about your payment data in plain language — transactions, approval and conversion rates, provider performance — and search the official Yuno API documentation without leaving the chat. Sign in with your Yuno account; payment operations use your organization's own Yuno API keys.
database or qualify tables as db.table. The plan is returned in full and is not truncated./ that contains ONLY the Yuno API Documentation documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its .mdx path to head or cat — a page at the URL path /some/page lives at /some/page.mdx. To search the docs with exact keyword or regex matches, use rg. To understand the docs structure, use tree or ls. Paths are specific to this site — never guess them. Discover real paths with tree / -L 2, ls /, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use rg -il "keyword" / to find where it is covered. Workflow: Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run --help on any command for usage. Each call is STATELESS: the working directory always resets to / and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with && or pass absolute paths (e.g., cd /some-directory && ls or ls /some-directory). Do NOT assume that cd in one call affects the next call. Examples (replace the placeholder paths with real ones from tree or search): - tree / -L 2 — see the top-level directory layout - rg -il "rate limit" / — find all files mentioning "rate limit" - rg -C 3 "apiKey" /some-directory/ — show matches with 3 lines of context around each hit - head -80 /some/page.mdx — read the top 80 lines of a specific page - head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx — read multiple pages in one call - cat /some/page.mdx — read a full page when you need everything - cat /openapi/openapi/subscriptions/update-subscription.json | jq '.paths | keys' — list OpenAPI endpoints OpenAPI specs for this site are mounted at: /openapi/openapi/subscriptions/update-subscription.json, /openapi/openapi/subscriptions/create-subscription.json, /openapi/openapi.yaml, /openapi/openapi.json, /openapi/openapi/promotions/create-promotion-quote.json, /openapi/openapi/payments/update-dispute.json, /openapi/openapi/payments/retrieve-payment-by-merchant-order-id.json, /openapi/openapi/payments/retrieve-payment-by-id.json, /openapi/openapi/payments/retrieve-payment-by-id-v2.json, /openapi/openapi/payments/refund-payment.json, /openapi/openapi/payments/disputes.json, /openapi/openapi/payments/create-payment.json, /openapi/openapi/payments/capture-authorization.json, /openapi/openapi/payments/cancel-payment.json, /openapi/openapi/payments/cancel-or-refund-payment-with-transaction.json, /openapi/openapi/payments/cancel-or-refund-a-payment.json, /openapi/openapi/payment-methods-direct-workflow/enroll-payment-method-api.json, /openapi/openapi/conversion-rate/get-conversion-rate.json, /openapi/openapi/checkout-sessions/create-one-time-use-token.json, /openapi/openapi/pci-proxy/manage-destinations.json, /openapi/openapi/fx-rates/get-fx-rates.json, /openapi/openapi/checkout-sessions/create-one-time-use-token-sdk-checkout.json, /openapi/openapi/recipients-for-marketplace/list-recipients.json, /openapi/openapi/recipients-for-marketplace/get-recipient-by-merchant-id.json, /openapi/openapi/webhooks/manage-webhooks.json, /openapi/openapi/recipients-for-marketplace/update-split-marketplace.json, /openapi/openapi/reports/create-a-report.json, `/openapi/openapi/reporting/report…head or cat the page path (append .mdx to the path returned from search — e.g. a result at /some/page is read with head -200 /some/page.mdx).database, or qualify every table as db.table. Identifiers that collide with reserved words need backticks. Results are truncated for very large outputs; the row count reported is the number of rows fetched. The structured result carries a query_id. Quote it when you report a slow or failed query — it is what an operator needs to look the statement up.
