Skip to main content
  • No automatic Core planner selects a settlement asset for two-step routes.
  • Estimates are ephemeral and have no ID. Creation live-validates their quote references and never silently replaces them.
  • Expired or rejected payment authorization cannot be refreshed in place.
  • Partial two-step failure has no dedicated automated recovery action.
  • QR images are decoded, but text-only screenshot OCR is not implemented.
  • Recipient updates create replacements and do not revoke the old record.
  • No generic arbitrary EVM transaction tool is exposed.
  • Partner identity and partner-query APIs are hidden.
  • Legacy low-level settlement workflows are outside the production surface.
  • A pending AgentKit verification session may need to be recreated after MCP restart.
  • Remote MCP can return a shareable action link with get_payment_link when one is available for that payment. Do not assume every route or connection offers one; use the returned bank or QR instructions when applicable.
  • The agent can track whether a collection was paid, not who paid it.
  • Spending grants apply only to hosted crypto-deposit funding; they cannot authorize fiat funding or swaps.