requery_payment, which
is marked clearly. Everything is scoped to the project and environment carried by the token
— an assistant can never reach another project’s data.
List tools are cursor-paginated: they accept per_page (default 20, maximum 100) and
cursor.
Payments
inspect_payment defaults to the active attempt. Its payload is provider-specific and
unstable — read it, do not build logic on it.
Payouts
Customers
Your connected gateways
Credentials are never returned.
What your project can accept
These answer “where and how can I take money”, scoped to your configuration and environment.What your project can pay out
Reference data
Documentation
These let an assistant answer integration questions from the documentation instead of
guessing.
Actions
It only accepts a failed intent, and it is the same operation as
POST /payment/intents/{id}/requery. Use it to recover a payment that
failed on the Orchestrate side while the provider actually took the money — not as a routine
retry.