canonical: https://jentic.com/apis/shipandco.com/shipandco

# Shipandco Ship&co Shipping API

Ship&co API enables you to create shipments, retrieve shipping rates, manage carriers, track packages, and manage addresses and warehouses. The API exposes 23 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a shipment, list shipments. Covers 23 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create a shipment
- List shipments
- Get a shipment
- Delete a shipment
- Register a carrier

## Use cases

### Developer Tools Operations

Use the Ship&co Shipping API to perform developer tools operations programmatically. The API provides 23 endpoints covering core functionality including create a shipment, list shipments, get a shipment.

Example prompt: Call POST /shipments to create a shipment

### Automated Shipments Management

Automate shipments operations by combining multiple Ship&co Shipping API endpoints. Agents can list shipments and then get a shipment in a single workflow.

Example prompt: Call GET /shipments to list shipments, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Ship&co Shipping 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.

Example prompt: Search Jentic for 'create a shipment', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/shipments` | Create a shipment |
| GET | `/shipments` | List shipments |
| GET | `/shipments/{id}` | Get a shipment |
| DELETE | `/shipments/{id}` | Delete a shipment |
| POST | `/rates` | Get shipping rates |
| POST | `/carriers` | Register a carrier |
| GET | `/carriers` | List carriers |
| PUT | `/carriers/{id}` | Update a carrier |

## Key resources

- **Shipments** — Create, list, get, and delete shipments
- **Rates** — Retrieve shipping rates
- **Carriers** — Register, list, update, and delete carriers
- **NegotiatedRates** — Upload and delete negotiated carrier rates
- **Tracking** — Get tracking information

## AI readiness

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.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 76 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 64 / 100
- **View full report:** https://jentic.com/apis/shipandco.com/shipandco/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Ship&co Shipping API by hand means placing your key in the x-access-token header, pointing at the api.shipandco.com host, and threading it through shipment, rate, and carrier calls yourself. Through Jentic you install once, import the Ship&co Shipping API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Ship&co puts the shipment id in the URL path (`/shipments/{id}`), so a rule can pin your agent to one shipment. You choose the operations it may call, so a destructive one like deleting a shipment is not included unless you add it.
- **Credential handling:** Your Ship&co 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a shipment' or 'get shipping rates', and Jentic returns the matching Ship&co operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Ship&co Shipping API use?

The Ship&co Shipping API uses an API key passed in the `x-access-token` 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 create a shipment with the Ship&co Shipping API?

Yes. Use the POST /shipments endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Ship&co Shipping 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 a shipment through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a shipment'. Jentic returns the matching Ship&co Shipping API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Ship&co Shipping API have?

The Ship&co Shipping API exposes 23 endpoints covering shipments, rates, carriers operations.

### Can I limit what my agent is allowed to do with the Ship&co Shipping API?

Yes. Because Jentic One is self-hosted, you decide which Ship&co operations your agent may call, so you can grant read access to list and get shipments (GET /shipments, GET `/shipments/{id}`) while withholding a destructive call like deleting a shipment (DELETE `/shipments/{id}`) unless you explicitly add it. Ship&co puts the shipment id in the URL path, so your own rules can pin the agent to a single shipment rather than the whole account. Your API key is held by your instance and injected at execution time, so the agent acts only within the boundaries you set.