For Agents
Programmatically get countries, create deliveries. Covers 12 operations with basic authentication.
Use for: I need to countries, I want to deliveries, Search for delivery information, Find all modify delivery dropoff
Not supported: Does not handle payments, communications, or crm - use for analytics only.
Shippify provides powerful logistics tools with the most advanced technology on the market to deliver and track your shipments. The API allows creating deliveries, getting quotes, managing routes, and tracking shipments. The API exposes 12 endpoints secured with basic authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Shippify 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%2Fshippify.co%2Fshippify" | 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%2Fshippify.co%2Fshippify" | 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 Shippify API.
Get countries
Create deliveries
Modify delivery dropoff
Change delivery status
Monitor Shippify API operational status and events
Patterns agents use Shippify API for, with concrete tasks.
★ Analytics Operations
Use the Shippify API to perform analytics operations programmatically. The API provides 12 endpoints covering core functionality including get countries, create deliveries, get delivery information.
Call GET /v1/country to get countries
Automated Deliveries Management
Automate deliveries operations by combining multiple Shippify API endpoints. Agents can create deliveries and then get delivery information in a single workflow.
Call POST /v1/deliveries to create deliveries, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Shippify 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 'get countries', load the operation schema, and execute with Jentic-managed credentials
12 endpoints — shippify provides powerful logistics tools with the most advanced technology on the market to deliver and track your shipments.
METHOD
PATH
DESCRIPTION
/v1/country
Get countries
/v1/deliveries
Create deliveries
/v1/deliveries/{id}/complete
Get delivery information
/v1/deliveries/dropoff
Modify delivery dropoff
/v1/deliveries/{id}/status
Change delivery status
/v1/deliveries/token/{id}
Get delivery tracking link
/v2/pricing/quotes/available
Get delivery quotation
/v2/integrations/deliveries/labels
Print delivery labels
/v1/country
Get countries
/v1/deliveries
Create deliveries
/v1/deliveries/{id}/complete
Get delivery information
/v1/deliveries/dropoff
Modify delivery dropoff
/v1/deliveries/{id}/status
Change delivery status
/v1/deliveries/token/{id}
Get delivery tracking link
/v2/pricing/quotes/available
Get delivery quotation
/v2/integrations/deliveries/labels
Print delivery labels
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>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Shippify API by hand means handling its basic auth, pointing at the api.shippify.co host, and threading credentials through delivery creation and status calls yourself. Through Jentic you install once, import the Shippify API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Shippify puts the delivery id in the URL path (/v1/deliveries/{id}/...), so a rule can pin your agent to one delivery for actions like completing it or updating its status. You choose the operations it may call, so anything else is left out unless you add it.
Credential isolation
Your Shippify 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 a delivery' or 'get a delivery quote', and Jentic returns the matching Shippify 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.
Specific to using Shippify API through Jentic.
What authentication does the Shippify API use?
The Shippify 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 get countries with the Shippify API?
Yes. Use the GET /v1/country endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Shippify 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 get countries through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get countries'. Jentic returns the matching Shippify API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Shippify API have?
The Shippify API exposes 12 endpoints covering deliveries, pricing, routes operations.
Can I limit what my agent is allowed to do with the Shippify API?
Yes. Because you self-host Jentic One, your own rules decide which Shippify operations and credentials the agent may use. Since Shippify carries the delivery id in the URL path, such as /v1/deliveries/{id}/status and /v1/deliveries/{id}/complete, you can pin the agent to a single delivery for actions like updating its status or completing it. You also choose the exact operations it may call, so anything you do not grant, such as creating deliveries or printing labels, stays out of reach.
GET STARTED