# AnserX Tracking API & MCP

URL: https://docs.lastscanned.com/carriers/anserx

Query live **AnserX** (`anserx`) package status and scan history in a single synchronous `GET` request or MCP tool call.

## Overview & Quick Facts

| Property | Value |
|---|---|
| **Carrier slug (`?carrier=`)** | `anserx` |
| **Brand aliases** | AnserX, Anser X, BTY, oms.anserx.com |
| **Category** | China cross-border e-commerce logistics (to Mexico and elsewhere) |
| **Single-package REST endpoint** | `GET https://api.lastscanned.com/v1/track/{trackingNumber}` |
| **Batch REST endpoint** | `GET https://api.lastscanned.com/v1/track?numbers=BTYCN0092384464YQ,BTYCN0092384464YQ` |
| **MCP server (`https://mcp.lastscanned.com`)** | `track_package`, `track_packages`, `list_carriers` |
| **Authentication & pricing** | `Authorization: Bearer lsk_live_...` · 1 free keyless lookup/day per IP |

## Tracking Number Formats & Auto-Detection

| Pass | Rule / Regex | Check Digit | Examples |
|---|---|---|---|
| **Pass 1 (`matches`)** | `/^BTYCN\d{10}YQ$/` | none | `BTYCN0092384464YQ` |
| **Pass 2 (`mayMatch`)** | none | none | none |

`BTYCN…YQ` numbers belong to AnserX alone, so `?carrier=anserx` is optional.

## Synchronous `GET` Request & Normalized JSON Response

```bash
curl -s "https://api.lastscanned.com/v1/track/BTYCN0092384464YQ?carrier=anserx" \
  -H "Authorization: Bearer $LASTSCANNED_API_KEY"
```

```json
{
  "carrier": "anserx",
  "trackingNumber": "BTYCN0092384464YQ",
  "status": "delivered",
  "statusDescription": "Parcel has been delivered",
  "service": null,
  "deliveredAt": null,
  "deliveredAtLocal": "2026-03-01T13:32:36",
  "signedBy": null,
  "destination": {
    "city": null,
    "state": null,
    "country": "MX"
  },
  "events": [
    {
      "timestamp": null,
      "localTime": "2026-03-01T13:32:36",
      "status": "delivered",
      "description": "Parcel has been delivered",
      "location": "Guadalajara, 45650",
      "code": "BTY_LASTMILE_DELIVERED"
    },
    {
      "timestamp": null,
      "localTime": "2026-02-27T17:57:33",
      "status": "out_for_delivery",
      "description": "Parcel currently being delivered",
      "location": "Guadalajara, 45650",
      "code": "BTY_LASTMILE_DELIVERING"
    },
    {
      "timestamp": null,
      "localTime": "2026-02-24T16:51:01",
      "status": "in_transit",
      "description": "The courier has received this parcel for delivery and will set a delivery time shortly",
      "location": "MX",
      "code": "BTY_LASTMILE_TRANSIT"
    },
    {
      "timestamp": null,
      "localTime": "2026-02-13T12:20:10",
      "status": "in_transit",
      "description": "Arrived at destination port",
      "location": "MX",
      "code": "BTY_LINE_ARRIVED"
    },
    {
      "timestamp": null,
      "localTime": "2026-02-08T09:24:20",
      "status": "in_transit",
      "description": "Hand over to airline",
      "location": "CN",
      "code": "BTY_LINE_HANDOVER"
    },
    {
      "timestamp": null,
      "localTime": "2026-02-04T19:05:19",
      "status": "label_created",
      "description": "Shipment information received",
      "location": "CN",
      "code": "BTY_ORDER_CREATED"
    }
  ]
}
```

## Notes

- **Route**: the JSON behind `oms.anserx.com/tracking`; plain GET, no account.
- **Time zone**: China-side scans and last-mile scans use different clocks and the feed gives no zone, so only `localTime` is set.
- **Status**: from the carrier's codes (`BTY_ORDER_CREATED`, `BTY_WAREHOUSE_*`, `BTY_LINE_*`, `BTY_EXCC_*`, `BTY_LASTMILE_TRANSIT/DELIVERING/DELIVERED`).

## Related Resources

- **Regex & check digits**: [Tracking number formats & auto-detection](/formats)