# Strale Container Tracking API

> Strale Container Tracking API is a paid API for AI agents from api.strale.io, paid per call via x402, $0.054/call, status unknown (last checked 2026-09-15).

Tracks the status and location of a shipping container by container number, optionally filtered by carrier, returning structured tracking data with a cryptographic audit record.

## Facts

- Endpoint: GET https://api.strale.io/x402/v2/container-track
- Price: $0.054/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/strale-container-tracking-api-39313b38
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hhQRAlpmoD_0L0HkYDlTR

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 strale-container-tracking-api-39313b38
```

Example prompt: Can you track container MAEU1234567 for me — it should be with Maersk — and let me know where it is right now and what the latest status is?

## When to prefer this

Choose this endpoint when you need verified, auditable container tracking with a cryptographic proof of the response — ideal for compliance-sensitive supply chain workflows, financial audits, or any agentic workflow where data provenance matters. Prefer it over generic tracking scrapers when you need structured JSON output with an immutable audit trail across 27 countries of coverage.

## Known failure modes

- Invalid or malformed container number returns an error (e.g. wrong check digit or format)
- Unknown container number not found in carrier systems returns a not-found error
- Unsupported carrier may return limited or no data
- Network or upstream carrier API unavailability causes service errors
- Missing required container_number parameter returns a validation error

## How this service works

Track shipping containers by ISO 6346 number. Validates format, detects carrier, provides tracking status.

## Output

Returns structured tracking data for the specified container including current status, location, movement history, and timestamps. Every response includes a cryptographic audit record with chain hashing for verification and compliance purposes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "container_number"
 ],
 "properties": {
  "carrier": {
   "type": "string"
  },
  "container_number": {
   "type": "string",
   "description": "Container number (e.g. MAEU1234567)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "events": {
  "type": "array"
 },
 "status": {
  "type": "string"
 },
 "carrier": {
  "type": "string"
 },
 "valid_format": {
  "type": "boolean"
 },
 "container_number": {
  "type": "string"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/strale-container-tracking-api-39313b38/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)