Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Shipwire 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%2Fshipwire.com%2Fshipwire" | shStep 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%2Fshipwire.com%2Fshipwire" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Shipwire API.
Create order
List orders
Get order
Update order
Cancel order
Patterns agents use Shipwire API for, with concrete tasks.
GET STARTED
★ E-Commerce Operations
Use the Shipwire API to perform e commerce operations programmatically. The API provides 18 endpoints covering core functionality including create order, list orders, get order.
Call POST /orders to create order
Automated Inventory Management
Automate inventory operations by combining multiple Shipwire API endpoints. Agents can list orders and then get order in a single workflow.
Call GET /orders to list orders, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Shipwire API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.
Search Jentic for 'create order', load the operation schema, and execute with Jentic-managed credentials
18 endpoints — shipwire provides fulfillment and warehouse management apis for managing orders, inventory, shipments, returns, and warehouses.
METHOD
PATH
DESCRIPTION
/orders
Create order
/orders
List orders
/orders/{id}
Get order
/orders/{id}
Update order
/orders/{id}/cancel
Cancel order
/stock
List stock
/products
Create product
/products
List products
/orders
Create order
/orders
List orders
/orders/{id}
Get order
/orders/{id}
Update order
/orders/{id}/cancel
Cancel order
/stock
List stock
/products
Create product
/products
List products
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Shipwire API by hand means handling its basic auth, pointing at the api.shipwire.com host, and threading credentials through order, stock, and product calls yourself. Through Jentic you install once, import the Shipwire API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Shipwire puts the order id in the URL path (/orders/{id}), so a rule can pin your agent to one order for reads, updates, and cancel. You choose the operations it may call, so anything it should not touch is left out unless you add it.
Credential isolation
Your Shipwire 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 'create an order' or 'check stock levels', and Jentic returns the matching Shipwire operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using Shipwire API through Jentic.
What authentication does the Shipwire API use?
The Shipwire API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create order with the Shipwire API?
Yes. Use the POST /orders endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Shipwire API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create order through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create order'. Jentic returns the matching Shipwire API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Shipwire API have?
The Shipwire API exposes 18 endpoints covering inventory, orders, products operations.
Can I limit what my agent is allowed to do with the Shipwire API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Shipwire operations and credentials your agent may use. You can allow only the calls it needs, such as GET /orders and GET /stock for read-only checks while withholding POST /orders, PUT /orders/{id}, and POST /orders/{id}/cancel. Because Shipwire carries the order id in the URL path (/orders/{id}), a rule can pin the agent to a single order for reads, updates, and cancellations, and anything you do not grant stays out of reach.
For Agents
Programmatically create order, list orders. Covers 18 operations with basic authentication.
Use for: I need to order, I want to orders, Search for order, Find all order
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
Shipwire provides fulfillment and warehouse management APIs for managing orders, inventory, shipments, returns, and warehouses. The API exposes 18 endpoints secured with basic authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>