Skip to integration guide

Enterprise integration

RemitBot.ai
Integration guide

Payment controls for agent-driven workflows. Use the customer portal to coordinate onboarding and manage credentials for your organization.

Your product endpoint

Use this address after your organization receives production access and integration approval. API calls require a product-specific credential and verified subscription access.

POST https://remitbot.ai/api/v1/products/remitbot/evaluate
Authorization: Bearer <your product API key>
Content-Type: application/json

Your onboarding team configures the server policy for your contracted integration. Confirm activation and the required policy identifiers before sending production requests.

Evaluate a payment request

Check an agent identifier, counterparty, purpose, rail, currency and per-request amount against your organization’s server-maintained policy.

{
  "agentId": "your-agent-id",
  "counterpartyId": "your-counterparty-id",
  "purpose": "your-approved-purpose",
  "rail": "your-configured-rail",
  "amountMinor": 10000,
  "currency": "USD"
}

Example identifiers and values only. Required fields must match your configured policy. Additional fields and caller-supplied policy or approval overrides are rejected.

Handle the result

allow, approval_required, hold or block. The amount cap applies to this request; it is not a cumulative spending reservation. The caller remains responsible for identity authentication and settlement. Responses include requestId, product, decision, reason, policyVersion and executionPerformed: false. Hold the proposed action on errors, timeouts or unknown outcomes.

Credentials and request limits

Keep keys in your server-side secrets manager. Send them only in the Authorization header, never in a URL or browser code. Keys expire after 90 days and can be revoked through Customer access once credential management is activated.

The initial operational limit is 60 requests per minute per key with a maximum 16 KB request body. These are technical limits, not subscription allowances.

400
Invalid request
401
Missing or invalid API key
403
Subscription access unavailable
413
Request body too large
429
Rate limit reached
503
Service or integration unavailable

Do not retry rejected actions automatically. For 429 responses, use bounded backoff; for 503 responses, confirm service availability with support.