# AMR Fleet Dispatcher MCP

> AMR Fleet Dispatcher MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.35/call, status unknown (last checked 2026-10-15).

Dispatches and coordinates autonomous mobile robot (AMR) fleets by processing fleet commands and routing instructions

## Facts

- Endpoint: POST https://api.m2mcent.com/amr-fleet-dispatcher-mcp/api/process?utm_source=zero.xyz
- Price: $0.35/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/amr-fleet-dispatcher-mcp-a3d1099a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8EM6tgi-aFJeywNpOiVG_

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 amr-fleet-dispatcher-mcp-a3d1099a -d '<json body>'
```

Example prompt: Dispatch the AMR fleet to pick up inventory from zone B3 and deliver it to the packing station — send the task command now.

## When to prefer this

Choose this endpoint when you need to programmatically dispatch, route, or assign tasks to an autonomous mobile robot fleet in real time. Prefer this over generic task queues when the target system is an AMR fleet requiring direct dispatch coordination.

## Known failure modes

- Invalid or malformed data string returns an error response
- Unavailable robots or fleet conflicts may cause dispatch rejection
- Unrecognized command format leads to processing failure
- Network timeout if fleet management backend is unreachable
- Missing required data field returns validation error

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns a dispatch confirmation or result object indicating whether the fleet command was accepted, along with any routing assignments, task IDs, or status updates for the affected robots.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/amr-fleet-dispatcher-mcp-a3d1099a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)