Support and diagnostics
Read onlyWhat it covers#
Three read tools: one answers dashboard usage questions with the official guides at tilopay.com/guias, another tests the credentials and one endpoint of each API group to know which part responds when something fails, and the third analyses a code snippet or stack trace you pass it and returns a diagnosis, root cause, fix and risks. That last one does not read repositories and does not run code.
Tools#
Tilopay connection diagnostics
Read onlytilopay_diagnostics
Verifies the user credentials and tests one endpoint of each group (sales and transactions, catalog, recurring, stored cards). Useful when a tool fails, to know which part of the API is responding.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
environment | string (production | test) | — | Environment for the transactions test (production by default) |
Returns
{ checks, failed }
checks is a list with check, ok and detail for each test: credentials, transactions, catalog, recurring and stored cards. failed is the number of failing tests. Credentials come back masked.
Help from Tilopay guides and tutorials
Read onlytilopay_help_guides
Answers questions about using the Tilopay dashboard with the official guides at tilopay.com/guias. It returns excerpts and the links to those guides.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
question | string | yes | The merchant's question, as written |
Returns
{ articles }
Up to 3 articles with title, url and excerpt, taken from tilopay.com/guias. With no match it returns an empty articles list and a text with the available guides.
Debug code
Read onlytilopay_debug_code
Analyses a code snippet or stack trace sent by the user and returns a diagnosis, root cause, a concrete fix and risks. It does not read repositories and does not run code.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | yes | Code snippet, log or stack trace as the user sent it |
error | string | — | Error message or observed behaviour, if any |
language | string | — | Language or stack (e.g. typescript, php, react). Detected when not given |
context | string | — | What the code should do or when it fails |
Returns
{ report, truncated, redacted, model }
report is the diagnosis in text (diagnosis, root cause, fix and risks). truncated says whether the code was cut down to 12,000 characters; redacted, whether possible credentials were hidden before the analysis; model, the model used. It does not read repositories and does not run the code.
Last verified: 2026-09-02 · Owner: equipo-integraciones