Install Jentic One Beta

Connect the LAAS API V1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LAAS API V1, 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%2Fmrsool.co%2Fmrsool" | 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%2Fmrsool.co%2Fmrsool" | 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 LAAS API V1 API.

Calculate the price of a delivery before placing it

Place a single delivery order or submit orders in bulk

Retrieve a delivery order and download its air waybill

Cancel a delivery order that is no longer needed

Replay delivery events from the webhook log and simulate a status change in staging

GET STARTED

Start building with LAAS API V1 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LAAS API V1 API for, with concrete tasks.

★ AI Agent Delivery Dispatch

Let an AI agent arrange last-mile delivery on demand. The agent discovers the pricing and order operations through Jentic, stores the Mrsool key once, and places a delivery order after checking the quoted price, without bespoke HTTP wiring. Webhook events flowing back let the agent follow the order to completion.

Calculate the price for a pickup and drop-off, place the delivery order, and return the tracking reference

On-Demand Delivery Pricing

Quote delivery cost before committing an order. The API returns a price for a given pickup and drop-off so a checkout or dispatch flow can show the fee and decide whether to proceed.

Calculate the delivery price for a pickup and drop-off pair and return the quoted amount

Bulk Order Fulfillment

Dispatch many deliveries in one call for batch fulfillment. The bulk order operation accepts a set of deliveries so a warehouse or marketplace can hand off an entire wave of orders at once.

Submit a batch of delivery orders in a single bulk request and return the created order references

Shipment Tracking

Follow a delivery from dispatch to drop-off. The API retrieves an order's current record and its air waybill, and the webhook log lets a tracking view replay every status event Mrsool has sent for the order.

Retrieve a delivery order, download its air waybill, and replay its status events from the webhook log

Key Endpoints

8 endpoints — the mrsool laas api (logistics as a service) creates and tracks delivery orders across mrsool's courier network.

METHOD

PATH

DESCRIPTION

POST

/api/v1/orders

Create a delivery order

POST

/api/v1/orders/calculate_price

Calculate a delivery price

GET

/api/v1/orders/{order_id}

Retrieve a delivery order

POST

/api/v1/orders/{order_id}/cancel

Cancel a delivery order

GET

/api/v1/orders/{order_id}/air_waybill

Retrieve an order's air waybill

POST

/api/v1/orders

Create a delivery order

POST

/api/v1/orders/calculate_price

Calculate a delivery price

GET

/api/v1/orders/{order_id}

Retrieve a delivery order

POST

/api/v1/orders/{order_id}/cancel

Cancel a delivery order

GET

/api/v1/orders/{order_id}/air_waybill

Retrieve an order's air waybill

Why Jentic?

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

Setup

Wiring the Mrsool LAAS API by hand means learning its bearer-token auth, sequencing price checks before order creation, and consuming webhook events yourself. Through Jentic you install once, import the API from the API Directory, store the token, and your agent calls the operation it needs.

Permission scoping

You decide which Mrsool operations your agent may call. A rule can grant pricing and order placement while withholding cancellation, so the agent dispatches deliveries without the ability to void them, and the rule bounds operations rather than a single order.

Credential isolation

Your Mrsool API 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 'calculate a delivery price' or 'create a delivery order', and Jentic returns the matching Mrsool operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using LAAS API V1 API through Jentic.

What authentication does the Mrsool LAAS API use?

The Mrsool LAAS API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected when a call runs, so it never enters the agent's prompt or logs.

Can the Mrsool LAAS API give me a price before I place an order?

Yes. The calculate-price operation returns a delivery cost for a given pickup and drop-off, so an agent can quote the fee and decide whether to proceed before creating the order.

What are the rate limits for the Mrsool LAAS API?

The OpenAPI spec does not publish specific rate limits. Check the Mrsool documentation for current limits, and have your agent back off and retry when it receives a throttling response.

How do I create a delivery with the Mrsool LAAS API through Jentic?

Search Jentic for an intent like 'create a delivery order', and it returns the matching Mrsool operation with its input schema. Import the connector once, store your token, and your agent places orders without hand-written HTTP code. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Mrsool MCP server?

You don't need an MCP server to give your agent the Mrsool LAAS API. Jentic connects it directly from the Jentic API Directory: import the API, store your token once, and your agent calls the order and pricing operations. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.

Can I limit what my agent is allowed to do with the Mrsool LAAS API?

Yes. You choose the operations the agent may call, so a rule can allow pricing and order creation while withholding cancellation unless you add it. A rule bounds which operations run rather than which individual order is affected, and every call is logged.

Mrsool LAAS API V1

AI ReadinessFoundational (D-)43/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceShipping Logisticsbearer8 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create, price, cancel, and track delivery orders across Mrsool's courier network, and replay delivery webhook events.

Use for: I want to create a delivery order, Calculate the delivery price for an order, Cancel an existing delivery order, Download the air waybill for an order

Not supported: Does not warehouse inventory or handle payments. Use it to price, create, track, and cancel Mrsool delivery orders only.

The Mrsool LAAS API (Logistics as a Service) creates and tracks delivery orders across Mrsool's courier network. It calculates delivery prices, places single or bulk orders, retrieves an order and its air waybill, and cancels an order that is no longer needed. A webhook log endpoint lets you replay the delivery events Mrsool has sent, and a test-status operation simulates status changes in the staging environment.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

90%

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

42%

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

13%

Example Density

How richly the API is illustrated with examples.

88%

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

23%

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.

55%

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

52%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LAAS API V1 to your agent

Capabilities

Start building with LAAS API V1 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mrsool LAAS API V1

Jentic AI Readiness Score

LAAS API V1

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