# Drayage Port Scheduler MCP

> Drayage Port Scheduler MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.2/call, status unknown (last checked 2026-10-20).

Schedules and optimizes drayage and port logistics operations, coordinating container pickup, delivery, and port appointment timing.

## Facts

- Endpoint: POST https://api.m2mcent.com/drayage-port-scheduler-mcp/api/process?utm_source=zero.xyz
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/drayage-port-scheduler-mcp-15e2836c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_InGUCddp9Iev7Lbl3hVPs

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 drayage-port-scheduler-mcp-15e2836c -d '<json body>'
```

Example prompt: Can you schedule a drayage pickup for my 40-foot container arriving at the Port of Los Angeles on Thursday — I need it routed to a warehouse in Compton by Friday afternoon, and I want the port appointment optimized around gate hours?

## When to prefer this

Choose this endpoint when you need to automate or optimize drayage scheduling tied to specific port appointments, gate hours, and container logistics. It is ideal for freight agents, logistics platforms, and supply chain automation workflows that need to coordinate truck dispatch with port terminal operations rather than performing simple address-to-address routing.

## Known failure modes

- Invalid or incomplete container/port data in the data field causes processing failure
- Port appointment windows unavailable or fully booked for the requested timeframe
- Unrecognized port terminal or location identifiers
- Malformed JSON in the data string input
- Scheduling conflict with existing appointments returns error or fallback options
- Service timeout for complex multi-container optimization requests

## 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 structured drayage schedule including optimized port appointment timing, routing details, dispatch recommendations, and coordination data for container pickup and delivery operations.

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/drayage-port-scheduler-mcp-15e2836c/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)