Yuno

Create a payment link in Yuno. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__paymentLinkCreate

Create a recipient in Yuno. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__recipientCreate

Create a subscription in Yuno. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__subscriptionCreate

Delete an installment plan in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__installmentPlanDelete

Delete a recipient in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__recipientDelete

Return the complete input/output JSON Schema and a worked example for any tool on this server. Registered schemas are compacted; call this before building complex payloads (e.g. paymentCreate).

pay__describeTool

Pause a subscription in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__subscriptionPause

Refund a payment in Yuno. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__paymentRefund

Resume a subscription in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__subscriptionResume

Retrieve all installment plans in Yuno for an account. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__installmentPlanRetrieveAll

Retrieve payment methods for a checkout session in Yuno. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__checkoutSessionRetrievePaymentMethods

Retrieve a customer by ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__customerRetrieve

Retrieve a customer by external merchant_customer_id. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__customerRetrieveByExternalId

Retrieve all enrolled payment methods for a customer. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__paymentMethodRetrieveEnrolled

Retrieve an installment plan in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__installmentPlanRetrieve

Retrieve a payment by ID in Yuno. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__paymentRetrieve

Retrieve a payment link in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__paymentLinkRetrieve

Retrieve an enrolled payment method by customer and payment method ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__paymentMethodRetrieve

Retrieve payments by merchant order ID in Yuno. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__paymentRetrieveByMerchantOrderId

Retrieve a recipient in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__recipientRetrieve

Retrieve a subscription in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__subscriptionRetrieve

Search across the Yuno API Documentation knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Yuno API Documentation, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. `head -200 /api-reference/create-customer.mdx`).

docs__search_yuno_api_documentation

Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

docs__submit_feedback

Unenroll a saved payment method for the user. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__paymentMethodUnenroll

Update a customer by ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__customerUpdate

Update an installment plan in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__installmentPlanUpdate

Update a recipient in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__recipientUpdate

Update a subscription in Yuno by its ID. Call pay__describeTool with the tool name for its full input schema before building a payload.

pay__subscriptionUpdate

Return the execution plan for a query WITHOUT running it. Use this to check how a query will be executed, or to sanity-check an expensive-looking query before running it. Same database rules as read_query: pass `database` or qualify tables as `db.table`. The plan is returned in full and is not truncated.

Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` 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 (e.g. `/quickstart.mdx`, `/api-reference/create-customer.mdx`) to `head` or `cat`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **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 /api-reference && ls` or `ls /api-reference`). Do NOT assume that `cd` in one call affects the next call. Examples: - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /api-reference/` — show matches with 3 lines of context around each hit - `head -80 /quickstart.mdx` — read the top 80 lines of a specific page - `head -80 /quickstart.mdx /installation.mdx /guides/first-deploy.mdx` — read multiple pages in one call - `cat /api-reference/create-customer.mdx` — read a full page when you need everything - `cat /openapi/spec.json | jq '.paths | keys'` — list OpenAPI endpoints Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/quickstart.mdx` becomes `/quickstart` and `/api-reference/overview.mdx` becomes `/api-reference/overview`.

Run a read-only SQL query against the analytics data warehouse. Accepts SELECT, WITH, SHOW, DESCRIBE, and EXPLAIN of a read. Anything that writes or changes schema is rejected. The connection may have NO default database. Either pass `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.

Describe one table and show a few sample rows. Returns the column names and types, then up to five rows. This is the cheapest way to learn a table's shape before writing a query against it — prefer it to SELECT * with a LIMIT. Both database and table are required and must be plain identifiers.