# RemitBot.ai Dual Control Path

> RemitBot.ai Dual Control Path is a paid API for AI agents from remitbot.ai, paid per call via x402, $0.025/call, status unknown (last checked 2026-10-17).

Approves, limits, and traces agent-to-agent payments with dual-control verification across enterprise rails

## Facts

- Endpoint: GET https://remitbot.ai/api/x402/dual-control-path?utm_source=zero.xyz
- Price: $0.025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/remitbot-ai-dual-control-path-949a8036
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7C9csnl7qrlpmNxzFNpIn

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability remitbot-ai-dual-control-path-949a8036
```

Example prompt: Run a dual-control check through RemitBot on an outgoing agent-to-agent payment so I get back an approval disposition and a remittance receipt I can attach to the audit trail.

## When to prefer this

Choose this endpoint when you need enterprise-grade dual-control approval and an auditable remittance receipt for agent-to-agent payments, especially when compliance, traceability, and policy enforcement across payment rails are required before funds move.

## Known failure modes

- Enterprise program not approved — application required before access is granted
- Invalid or missing HTTP method in request body returns schema validation error
- Non-enterprise caller rejected due to program eligibility requirements
- Network or rail unavailability returns failed disposition
- Rate limiting or quota exceeded for the calling agent

## How this service works

RemitBot helps enterprises approve, limit, and trace agent-to-agent payments across rails. Enterprise programs by application. Built by StratEdge Workflow Systems.

## Output

Returns a JSON object confirming the service name, network (Base), ticker (REMIT), a disposition string (e.g. APPROVE_WITH_TRAIL), a boolean dual-control verification status, a protocol token address, a remittance receipt ID, and a link to the nodes portal.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "POST"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type",
    "example"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ticker": "REMIT",
  "network": "base",
  "service": "RemitBot.ai",
  "success": true,
  "disposition": "APPROVE_WITH_TRAIL",
  "nodesPortal": "https://remitbot.ai/nodes",
  "protocolToken": "0x8976b35b26C14fEAe130dbc0D601f3Adf4e10b07",
  "remittanceReceipt": "REMIT-8976B35B26C1",
  "dualControlVerified": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/remitbot-ai-dual-control-path-949a8036/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from remitbot.ai](https://www.zero.xyz/host/remitbot.ai/llms.txt)