# Fracht Shipment Reference Carrier Pattern Matcher

> Fracht Shipment Reference Carrier Pattern Matcher is a paid API for AI agents from fracht.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).

Matches a shipment reference string against caller-supplied carrier regex patterns to identify which carrier the reference belongs to, returning matched and unavailable fields with source and derivation metadata.

## Facts

- Endpoint: POST https://fracht.halowerk.com/v1/tracking-parse
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fracht-shipment-reference-carrier-pattern-matcher-520da813
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XwjikJGS-oHrinRVEHkxX

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 fracht-shipment-reference-carrier-pattern-matcher-520da813 -d '<json body>'
```

Example prompt: I have a shipment reference '1Z999AA10123456784' — can you match it against these carrier patterns: [{carrier: 'UPS', pattern: '1Z[A-Z0-9]{16}'}, {carrier: 'FedEx', pattern: '[0-9]{12}'}] and tell me which carrier it belongs to?

## When to prefer this

Choose this endpoint when you need to identify a carrier from a shipment reference using your own custom carrier pattern definitions rather than a fixed registry lookup. It is ideal for freight platforms with proprietary carrier lists, multi-carrier logistics systems that need flexible pattern matching, or when testing and validating new carrier detection rules against real reference strings. Prefer this over a fixed carrier lookup when carrier patterns need to be caller-controlled and extensible.

## Known failure modes

- No pattern matches the reference — matched carrier returned as null with unavailable_fields populated
- Reference string too short (under 3 chars) or too long (over 100 chars) — validation error
- Invalid pattern regex syntax in caller-supplied patterns — parse error or rejection
- Patterns array exceeds 500 items — request rejected
- Missing required fields (reference or patterns) — 400-level error
- Payment failure via x402 protocol — 402 response with payment requirements

## How this service works

Matches a shipment reference against caller-supplied carrier patterns. Missing facts are returned as null and named in unavailable_fields where applicable. Derived values disclose their method; source-backed values disclose source, time window and age. 

## Output

Returns the matched carrier name (if any pattern matches), parsed components of the shipment reference, a list of unavailable fields returned as null, derivation method for any derived values, and source, time window, and age metadata for source-backed values.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "patterns": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "carrier",
     "pattern"
    ],
    "properties": {
     "carrier": {
      "type": "string",
      "maxLength": 512,
      "minLength": 1,
      "description": ""
     },
     "pattern": {
      "type": "string",
      "maxLength": 512,
      "minLength": 1,
      "description": ""
     }
    },
    "additionalProperties": false
   },
   "maxItems": 500
  },
  "reference": {
   "type": "string",
   "maxLength": 100,
   "minLength": 3,
   "description": ""
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fracht-shipment-reference-carrier-pattern-matcher-520da813/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fracht.halowerk.com](https://www.zero.xyz/host/fracht.halowerk.com/llms.txt)