API
[PENDING] REST endpoint paths, auth scheme, and versioning are issued during an enterprise program. They are not published on this page.
RemitBot is designed to sit between your agents and your payment rails. API, SDK, and MCP details below are summaries. Endpoint paths and sample code are placeholders until your program issues credentials.
SDK
[PENDING] SDK packages and install commands are provided to program participants.
MCP
A local check_payment server is in the RemitBot repository under packages/remitbot-mcp. It is not released and it is not listed in a registry. Hosted dual control, custom policies, and dashboards require a license.
Sample flow
- 01Your agent submits a payment intent (payer, payee, amount, rail, purpose).
- 02RemitBot checks identity, intent, limits, and counterparty.
- 03Disposition returns Approve, Hold, or Block.
- 04On Approve, settlement is handed to the rail you configured.
- 05An audit record is written for the decision.
// [PENDING] Sample request — not a live endpoint // POST /v1/payment-intents // Authorization: Bearer <issued-in-program>
Request a live demo
A live demo environment is available by request as part of an enterprise conversation. It is not a public self-serve sandbox.
Request a live demo