Install Jentic One Beta

Connect the OnlineXpress B2C API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OnlineXpress B2C 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%2Fonlinexpress.co.in%2Fonlinexpress" | 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%2Fonlinexpress.co.in%2Fonlinexpress" | 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 OnlineXpress B2C API.

Book a forward or reverse courier shipment

Create many shipments at once with a bulk request

Track a shipment by its order id

Validate a delivery pincode before booking

Cancel one or more shipments

GET STARTED

Start building with OnlineXpress B2C API

Explore with Jentic One

View OpenAPI Document

Bulk Shipment Creation

A store processing a day's orders books them together with a single bulk create request rather than one call per parcel. This keeps dispatch fast at volume, and each resulting shipment can then be tracked by its order id as it moves through the courier network.

Submit a bulk create request for a batch of orders and collect the tracking references for each

Order Tracking and Cancellation

A support tool checks delivery progress by tracking a shipment by its order id and cancels shipments that are no longer needed, such as a cancelled or undeliverable order. Reverse shipments cover returns, so the same API handles outbound delivery and the pickup leg.

Track a shipment by its order id and, if the order was cancelled, cancel the shipment and confirm the new status

Key Endpoints

6 endpoints — the onlinexpress b2c api books and manages courier shipments for business-to-consumer delivery in india.

METHOD

PATH

DESCRIPTION

POST

/shipments

Create a forward or reverse shipment

POST

/bulkcreate

Bulk create shipments

GET

/track/{order_id}

Track a shipment by order id

GET

/pincodes/{pin}

Validate a delivery pincode

POST

/cancelorder

Cancel one or more shipments

POST

/shipments

Create a forward or reverse shipment

POST

/bulkcreate

Bulk create shipments

GET

/track/{order_id}

Track a shipment by order id

GET

/pincodes/{pin}

Validate a delivery pincode

POST

/cancelorder

Cancel one or more shipments

Why Jentic?

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

Setup

Wiring the OnlineXpress B2C API by hand means calling its login operation for a bearer token, refreshing it, and sequencing the shipment, tracking, and cancellation calls yourself. Through Jentic you install once, import OnlineXpress from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

A rule can give your agent just the shipment-booking and tracking operations and leave cancellation and bulk creation out unless you add them. You choose which operations it may call.

Credential isolation

Your OnlineXpress credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'book a shipment' or 'track an order', and Jentic returns the matching OnlineXpress operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using OnlineXpress B2C API through Jentic.

What authentication does the OnlineXpress B2C API use?

The OnlineXpress B2C API uses a bearer token in the Authorization header, per its OpenAPI spec, which you obtain from its login operation; the shipment, tracking, and cancellation operations then carry that token. Through Jentic the credentials are held encrypted by your own Jentic One instance and injected at call time.

Can I track a shipment with the OnlineXpress B2C API?

Yes. The tracking operation returns a shipment's current status by its order id, and you can validate a delivery pincode before booking to confirm it is serviceable. Shipments are booked forward or reverse, individually or in bulk.

Can I cancel a shipment with the OnlineXpress B2C API?

Yes. The cancellation operation accepts one or more shipments to cancel. Pair it with tracking to confirm the shipment status before and after the cancellation.

Can I limit what my agent is allowed to do with the OnlineXpress B2C API?

Yes. Write a rule that allows only the shipment-booking and tracking operations, so the agent books and tracks parcels while cancellation and bulk creation stay out of its reach unless you add them. Every call the agent makes is logged.

How do I book a shipment with the OnlineXpress B2C API through Jentic?

Search by intent in Jentic with a query like 'book a courier shipment', add the OnlineXpress B2C API from the Jentic API Directory, and your agent validates the pincode then creates the shipment and returns the tracking reference. To run it on your own infrastructure, install Jentic One from its GitHub repo.

OnlineXpress B2C API

AI ReadinessNon-Ready (F)38/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceShipping Logisticsbearer6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Book forward and reverse courier shipments individually or in bulk, track by order id, validate pincodes, and cancel shipments for B2C delivery in India.

Use for: Book a courier shipment for a customer order, Create shipments in bulk from a day's orders, Track a shipment by its order id, Check whether a pincode is serviceable

Not supported: Does not handle payments, warehousing, or return refunds. Use for booking, tracking, and cancelling courier shipments only.

The OnlineXpress B2C API books and manages courier shipments for business-to-consumer delivery in India. It creates forward and reverse shipments individually or in bulk, tracks a shipment by its order id, validates delivery pincodes, and cancels shipments. A login call issues the bearer token that authorises the shipment operations.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

94%

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).

60%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: FSignals: 4

11%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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: A-Signals: 1

75%

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: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the OnlineXpress B2C API to your agent

Capabilities

Start building with OnlineXpress B2C API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

OnlineXpress B2C API

Jentic AI Readiness Score

OnlineXpress B2C API

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