RemitBot.ai

Developers

API, SDK, and MCP — credentials issued in an enterprise program.

RemitBot sits between your agents and your payment rails. API, SDK, and MCP integration specifications below summarize the production architecture; environment credentials and endpoint routes are provisioned per enterprise program.

API

REST endpoint routes, authentication credentials, and schema versions are provisioned during enterprise onboarding.

SDK

TypeScript and Python SDK packages and installation credentials are distributed directly to provisioned enterprise program teams.

MCP

An enterprise Model Context Protocol (MCP) payment-check server is available for governed agent environments alongside hosted dual-control and policy dashboards.

Sample flow

  1. 01Your agent submits a payment intent (payer, payee, amount, rail, purpose).
  2. 02RemitBot checks identity, intent, limits, and counterparty.
  3. 03Disposition returns Approve, Hold, or Block.
  4. 04On Approve, settlement is handed to the rail you configured.
  5. 05An audit record is written for the decision.
// Illustrative payment-intent check (provisioned enterprise route)
// POST /v1/payment-intents
// Authorization: Bearer <enterprise-program-token>

Request a live demo

A guided enterprise evaluation environment is available by request as part of an enterprise architecture review.

Request a live demo