Install Jentic One Beta

Connect the InPost ShipX API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the InPost ShipX API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feasypack24.net%2Feasypack24" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feasypack24.net%2Feasypack24" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with InPost ShipX API.

Find InPost parcel lockers and pickup-drop-off points, optionally filtered by postal code

Create locker-to-locker, hub-to-locker, and label-less shipments for an organization

Generate a shipping label for a created shipment

Track a parcel by its tracking number and read its current delivery status

Edit a shipment's reference after it has been created

GET STARTED

Start building with InPost ShipX API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use InPost ShipX API for, with concrete tasks.

★ Agent-driven checkout fulfillment

An AI agent handling order fulfillment can call the InPost ShipX API through Jentic to look up the locker a customer chose at checkout, create the shipment for the store's organization, and generate the label to hand to the warehouse. Jentic returns the create-shipment operation from a natural-language query, so the agent builds the shipment without reading the ShipX reference first.

Find the InPost point matching the customer's chosen locker, create a locker-to-locker shipment for the organization, and generate its shipping label.

Parcel tracking and status updates

Track a parcel by its tracking number and map its current state against the full list of tracking statuses the API publishes. Stores use this to push accurate delivery updates to customers and to flag parcels stuck in a locker before a return is auto-triggered.

Look up the parcel by its tracking number, compare its state against the published tracking statuses, and report whether it has been collected.

Locker selection at checkout

Search for InPost parcel lockers and pickup-drop-off points near a delivery address, optionally narrowing by postal code, so a storefront can show the customer the closest collection options. The points lookup is a public endpoint, so the map can load before the shopper signs in.

Search the points endpoint for lockers near the delivery postal code and return the three closest collection points.

Key Endpoints

13 endpoints — the inpost shipx api creates and manages parcel shipments routed through inpost's automated parcel lockers and pickup-drop-off points.

METHOD

PATH

DESCRIPTION

GET

/v1/points

Search for parcel lockers and pickup-drop-off points

POST

/v1/organizations/{organization_id}/shipments

Create a shipment for an organization

GET

/v1/organizations/{organization_id}/shipments

List an organization's shipments

PUT

/v1/shipments/{shipment_id}/attributes

Edit a shipment's reference

GET

/v1/shipments/{shipment_id}/label

Generate a shipping label for a shipment

GET

/v1/tracking/{tracking_number}

Track a parcel by its tracking number

GET

/v1/statuses

List the available shipment tracking statuses

GET

/v1/points

Search for parcel lockers and pickup-drop-off points

POST

/v1/organizations/{organization_id}/shipments

Create a shipment for an organization

GET

/v1/organizations/{organization_id}/shipments

List an organization's shipments

PUT

/v1/shipments/{shipment_id}/attributes

Edit a shipment's reference

GET

/v1/shipments/{shipment_id}/label

Generate a shipping label for a shipment

GET

/v1/tracking/{tracking_number}

Track a parcel by its tracking number

GET

/v1/statuses

List the available shipment tracking statuses

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the InPost ShipX API by hand means handling its bearer token, choosing the staging or production ShipX host, and coding the different locker-to-locker and hub-to-locker shipment variants yourself. Through Jentic you install once, import the API from the API Directory, store the token once, and your agent calls it.

Permission scoping

ShipX puts the organization and shipment ids in the URL path, so a rule can bound your agent to the operations it needs, such as point lookup and tracking. You choose which operations it may call, so the create-shipment and label operations are not included unless you add them.

Credential isolation

Your InPost token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a parcel shipment' or 'track a parcel', and Jentic returns the matching InPost ShipX operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using InPost ShipX API through Jentic.

Is there an InPost ShipX API MCP server?

You do not need an MCP server to give your agent the InPost ShipX API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the point lookup, shipment, label, and tracking operations. Operations are discovered on demand, so no extra server definitions load into the agent's context.

What authentication does the InPost ShipX API use?

The shipment, label, and organization operations require a bearer token per the OpenAPI spec, while the point lookup, tracking, and status endpoints are public and need no credential. Through Jentic the token is stored encrypted in your own Jentic One instance and supplied only when an authenticated call runs, so it never reaches the agent's context.

Can I track a parcel with the InPost ShipX API?

Yes. The tracking endpoint returns the current state of a parcel by its tracking number, and a separate statuses endpoint lists every state a shipment can move through so you can interpret the result. Both are public, so tracking lookups work without a token.

What are the rate limits for the InPost ShipX API?

The OpenAPI spec does not specify rate limits. Limits depend on your InPost organization agreement, so confirm the per-second and daily caps for your account in the InPost ShipX developer documentation at https://docs.inpost.pl.

Can I limit what my agent is allowed to do with the InPost ShipX API?

Yes. Write a rule that permits only the read operations, point lookup and tracking, when the agent should quote and track deliveries, and add the create-shipment and label operations only for workflows that actually dispatch parcels, with every call logged.

How do I create an InPost shipment through Jentic?

Search Jentic for 'create a parcel shipment' to surface the shipment operations, load the input schema, pass the organization, sender, and chosen point, and execute, then call the label operation for the returned shipment. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Easypack24 InPost ShipX API

AI ReadinessFoundational (C)56/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceShipping Logisticsbearer13 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create and track InPost parcel shipments: search lockers and pickup points, create shipments for an organization, edit references, generate labels, and track parcels by tracking number.

Use for: Find the nearest InPost parcel lockers for a delivery address, Create a locker-to-locker shipment for my organization, Generate a shipping label for an existing shipment, Track a parcel using its tracking number

Not supported: Does not handle payment collection, warehouse inventory, or returns refunds. Use for InPost parcel shipments, labels, and tracking only.

The InPost ShipX API creates and manages parcel shipments routed through InPost's automated parcel lockers and pickup-drop-off points. It finds nearby points, creates locker-to-locker, hub-to-locker, and label-less shipment variants for an organization, edits a shipment's reference, generates shipping labels, and tracks a parcel by its tracking number. It also returns the full set of tracking statuses a shipment can move through. It is aimed at online stores and logistics tools that offer InPost delivery at checkout and need to automate label generation and tracking.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

85%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

44%

Example Density

How richly the API is illustrated with examples.

79%

Example Validity

Percentage of examples that conform to their schemas.

23%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

72%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

77%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: D-Signals: 1

41%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the InPost ShipX API to your agent

Capabilities

Start building with InPost ShipX API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Easypack24 InPost ShipX API

Jentic AI Readiness Score

InPost Public Developers Documentation

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness