PackageX website screenshot

PackageX

PackageX provides vision-AI powered logistics execution — software that turns any camera or device into an intelligent scanning agent to automate receiving, inventory management, fulfillment and dispatch across warehouses, retail and building logistics. Its REST API and mobile Vision SDKs expose shipments, deliveries, tracking, addresses, containers, manifests, documents and vision inferences (shipping-label OCR, bill-of-lading parsing, item segmentation). Authentication is API-key based via the PX-API-KEY header, with separate sandbox and production environments. Customers include WeWork, Subaru, Ricoh, Medtronic, Toyota and On Running.

PackageX publishes 1 API contract indexed on the APIs.io network: Shipments API. Tagged areas include Company, Logistics, Shipping, Supply Chain, and Computer Vision.

The PackageX catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

PackageX’s developer surface includes documentation, getting-started guide, API reference, support, engineering blog, authentication, changelog, and 23 more developer resources.

50.6/100 developing ▬ flat Agent 30/100 agent ready Front door AI 6/6 dominant Heartbeat 77/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
1 published contract 1 Agent Skills
CompanyLogisticsShippingSupply ChainComputer VisionOCRPackage TrackingFulfillment

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Supply Chain Management
BC-520
Shipments
POST /v1/shipments POST /v1/shipments/{shipment}

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for PackageX It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/packagex/"><img src="https://apis.io/badge/packagex/card.svg" alt="PackageX on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
6 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/packagex/apis.yml: open an issue on github.com/api-evangelist/packagex to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
RPA and Document AI (RPA marketplaces, intelligent document processing) distribution 19.2 (thin) - -
ONVIF Video Analytics (video surveillance, edge cameras, computer vision) distribution 19.2 (thin) - -
Official SDKs on Packagist, pub.dev and Hex distribution 19.2 (thin) - -

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

PackageX Shipments API

The shipments API from PackageX — 2 operation(s) for shipments.

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Title shipments API

OPEN COLLECTION

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

PackageX API Rules

49 rules · 47 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Packagex Openapi Overlay

3 actions · documentation · packagex-openapi-original.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Packagex Authentication

apiKey · 1 scheme

SECURITY

Packagex Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Packagex Agentic Access

4 operations · 2 acting

4 operations · 2 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: packagex
name: PackageX
description: PackageX provides vision-AI powered logistics execution — software that turns any camera or device into an intelligent
  scanning agent to automate receiving, inventory management, fulfillment and dispatch across warehouses, retail and building
  logistics. Its REST API and mobile Vision SDKs expose shipments, deliveries, tracking, addresses, containers, manifests,
  documents and vision inferences (shipping-label OCR, bill-of-lading parsing, item segmentation). Authentication is API-key
  based via the PX-API-KEY header, with separate sandbox and production environments. Customers include WeWork, Subaru, Ricoh,
  Medtronic, Toyota and On Running.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://cdn.prod.website-files.com/68d230940fd846bdd01f1867/6989c29e1ae181a811f47ac1_OG.webp
url: https://raw.githubusercontent.com/api-evangelist/packagex/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bullpen-capital
- sierra-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Logistics
- Shipping
- Supply Chain
- Computer Vision
- OCR
- Package Tracking
- Fulfillment
tags_raw:
- Company
- Logistics
- Shipping
- Supply Chain
- Computer Vision
- OCR
- Package Tracking
- Fulfillment
- Computer-Vision
apis:
- aid: packagex:packagex-shipments-api
  name: PackageX Shipments API
  description: The shipments API from PackageX — 2 operation(s) for shipments.
  humanURL: https://docs.packagex.io/apis/getting-started/welcome
  baseURL: https://api.packagex.io
  tags:
  - Shipments
  tags_raw:
  - shipments
  properties:
  - type: OpenAPI
    url: openapi/packagex-shipments-api-openapi.yml
  - type: APIReference
    url: https://docs.packagex.io/apis/getting-started/welcome
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/packagex-capability-edges.yml
  name: PackageX Business Capability Map
- type: DeveloperPortal
  url: https://docs.packagex.io/apis/getting-started/welcome
- type: Documentation
  url: https://docs.packagex.io/apis/getting-started/welcome
- type: GettingStarted
  url: https://docs.packagex.io/apis/getting-started/welcome
- type: APIReference
  url: https://docs.packagex.io/apis/getting-started/welcome
- type: Support
  url: https://help.packagex.io/en/knowledge
- type: Blog
  url: https://packagex.io/blog
- type: GitHubOrganization
  url: https://github.com/packagex-io
- type: TermsOfService
  url: https://packagex.io/terms
- type: PrivacyPolicy
  url: https://packagex.io/privacy-policy
- type: StatusPage
  url: https://packagex.statuspage.io
- type: Authentication
  url: authentication/packagex-authentication.yml
- type: Packages
  url: packages/packagex-packages.yml
- type: SDKs
  url: packages/packagex-packages.yml
- type: X-MCPServerCandidate
  url: mcp/packagex-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/packagex-llms.txt
- type: Overlay
  url: overlays/packagex-openapi-overlay.yaml
- type: Conformance
  url: conformance/packagex-conformance.yml
- type: ErrorCatalog
  url: errors/packagex-problem-types.yml
- type: Lifecycle
  url: lifecycle/packagex-lifecycle.yml
- type: Deprecation
  url: lifecycle/packagex-lifecycle.yml
- type: ChangeLog
  url: changelog/packagex-changelog.yml
- type: Sandbox
  url: sandbox/packagex-sandbox.yml
- type: Conventions
  url: conventions/packagex-conventions.yml
- type: DataModel
  url: data-model/packagex-data-model.yml
- type: Webhooks
  url: asyncapi/packagex-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: AgenticAccess
  url: agentic-access/packagex-agentic-access.yml
- type: DomainSecurity
  url: security/packagex-domain-security.yml
- type: Website
  url: https://packagex.io
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 18
  pass: local-v1

PackageX API — frequently asked questions

Does PackageX have an API?

Yes. APIs.io lists 1 API from PackageX, including PackageX Shipments API.

Is there an OpenAPI specification for the PackageX API?

Yes. APIs.io indexes 1 OpenAPI specification for PackageX, each linked for download from this page.

How do I authenticate with the PackageX API?

PackageX uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Packagex Authentication.

Is the PackageX API ready for AI agents?

PackageX has a Kin Score of 50.6 out of 100 (developing) and an Agent Readiness score of 29.8 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/packagex"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/packagex/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/packagex/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.