ShipEngine API
62
AI ReadinessAI-Aware (B-)62/100
Official vendor OpenAPI document · agent-readyE CommerceStorefrontapiKey96 EndpointsREST
For Agents
Programmatically list account settings, create an account image. Covers 96 operations with apiKey authentication.
Use for: I need to account settings, I want to an account image, Search for account images, Find all account image by id
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
ShipEngine's easy-to-use REST API lets you manage all of your shipping needs without worrying about the complexities of different carrier APIs and protocols. We handle all the heavy lifting so you can focus on providing a first-class shipping experience for your customers at the best possible prices. Each of ShipEngine's features can be used by itself or in conjunction with each other to build pow. The API exposes 96 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the ShipEngine API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ShipEngine 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.
1
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%2Fshipengine.com%2Fshipengine" | sh2
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%2Fshipengine.com%2Fshipengine" | 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.
Capabilities
What an agent can do with ShipEngine API.
List Account Settings
Create an Account Image
Get Account Image By ID
Update Account Image By ID
Delete Account Image By Id
Parse an address
Use Cases
Patterns agents use ShipEngine API for, with concrete tasks.
★ E-Commerce Operations
Use the ShipEngine API to perform e commerce operations programmatically. The API provides 96 endpoints covering core functionality including list account settings, create an account image, list account images.
Call GET /v1/account/settings to list account settings
Automated account Management
Automate account operations by combining multiple ShipEngine API endpoints. Agents can create an account image and then list account images in a single workflow.
Call POST /v1/account/settings/images to create an account image, then verify the result
AI Agent Integration via Jentic
AI agents discover and call ShipEngine 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 apiKey tokens manually.
Search Jentic for 'list account settings', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
96 endpoints — shipengine's easy-to-use rest api lets you manage all of your shipping needs without worrying about the complexities of different carrier apis and protocols.
METHOD
PATH
DESCRIPTION
GET
/v1/account/settings
List Account Settings
POST
/v1/account/settings/images
Create an Account Image
GET
/v1/account/settings/images
List Account Images
GET
/v1/account/settings/images/{label_image_id}
Get Account Image By ID
PUT
/v1/account/settings/images/{label_image_id}
Update Account Image By ID
DELETE
/v1/account/settings/images/{label_image_id}
Delete Account Image By Id
PUT
/v1/addresses/recognize
Parse an address
POST
/v1/addresses/validate
Validate An Address
GET
/v1/account/settings
List Account Settings
POST
/v1/account/settings/images
Create an Account Image
GET
/v1/account/settings/images
List Account Images
GET
/v1/account/settings/images/{label_image_id}
Get Account Image By ID
PUT
/v1/account/settings/images/{label_image_id}
Update Account Image By ID
DELETE
/v1/account/settings/images/{label_image_id}
Delete Account Image By Id
PUT
/v1/addresses/recognize
Parse an address
POST
/v1/addresses/validate
Validate An Address
Jentic AI Readiness Score
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.
S
ShipEngine API
- AI-Aware (B-)62/100
46
Foundational Compliance70
Developer Experience & Jentic Compatibility57
AI-Readiness & Agent Experience86
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
46
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
72%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
10%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
70
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
16%
Example Density
How richly the API is illustrated with examples.
91%
Example Validity
Percentage of examples that conform to their schemas.
74%
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.
57
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
80%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
49%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
97%
Summary Coverage
Coverage of summaries across operations/tags/info.
86
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
86%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the ShipEngine API by hand means placing your key in the API-Key header, pointing at the api.shipengine.com host, and threading it through account, address, and label calls yourself. Through Jentic you install once, import the ShipEngine API from the API Directory, store the key once, and your agent calls it.
Permission scoping
ShipEngine puts the label image id in the URL path (/v1/account/settings/images/{label_image_id}), so a rule can pin your agent to one image resource. You choose the operations it may call, so a destructive one like deleting an image is not included unless you add it.
Credential isolation
Your ShipEngine API key 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 'validate an address' or 'list account settings', and Jentic returns the matching ShipEngine operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using ShipEngine API through Jentic.
What authentication does the ShipEngine API use?
The ShipEngine API uses an API key passed in the `API-Key` header. 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 list account settings with the ShipEngine API?
Yes. Use the GET /v1/account/settings endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the ShipEngine 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 list account settings through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list account settings'. Jentic returns the matching ShipEngine API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the ShipEngine API have?
The ShipEngine API exposes 96 endpoints covering account, addresses, batches operations.
Can I limit what my agent is allowed to do with the ShipEngine API?
Yes. Jentic One is self-hosted by you, so your own rules decide which ShipEngine operations and credentials your agent can use. You pick the exact endpoints it may call, so a destructive action like DELETE /v1/account/settings/images/{label_image_id} stays out unless you explicitly add it. Because ShipEngine puts the label image id in the URL path, a rule can also pin the agent to a single image resource rather than every account image.
GET STARTED