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

# Stamps.com USPS Shipping API

Stamps.com provides USPS shipping APIs for rate calculation, label creation, tracking, address validation, and pickup scheduling. The API exposes 11 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get shipping rates, create shipping label. Covers 11 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get shipping rates
- Create shipping label
- Void shipping label
- Track shipment
- Validate address
- Cleanse address

## Use cases

### Analytics Operations

Use the Stamps.com USPS Shipping API to perform analytics operations programmatically. The API provides 11 endpoints covering core functionality including get shipping rates, create shipping label, get label details.

Example prompt: Call POST /rates to get shipping rates

### Automated Account Management

Automate account operations by combining multiple Stamps.com USPS Shipping API endpoints. Agents can create shipping label and then get label details in a single workflow.

Example prompt: Call POST /labels to create shipping label, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Stamps.com USPS 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 'get shipping rates', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /rates | Get shipping rates |
| POST | /labels | Create shipping label |
| GET | /labels/{labelId} | Get label details |
| POST | /labels/{labelId}/void | Void shipping label |
| GET | /tracking/{trackingNumber} | Track shipment |
| POST | /addresses/validate | Validate address |
| POST | /addresses/cleanse | Cleanse address |
| POST | /pickups | Schedule pickup |

## Key resources

- **Account** — Operations related to Account
- **Addresses** — Operations related to Addresses
- **Insurance** — Operations related to Insurance
- **Labels** — Operations related to Labels
- **Pickups** — Operations related to Pickups

## Why Jentic

- **Setup:** Wiring the Stamps.com USPS Shipping API by hand means setting up its API key in the Authorization header, mapping the rate, label, address-validation and tracking calls, and handling void and pickup flows yourself. Through Jentic you install once, import the Stamps.com USPS Shipping API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The API puts the label id in the URL path (/labels/{labelId}, /labels/{labelId}/void), so a rule can pin your agent to one label for reads and status. You choose the operations it may call, so destructive ones like voiding a label are not included unless you add them.
- **Credential handling:** Your Stamps.com 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 'get shipping rates' or 'buy a shipping label', and Jentic returns the matching Stamps.com USPS Shipping API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Stamps.com USPS Shipping API use?

The Stamps.com USPS Shipping API uses an API key passed in the `Authorization` 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 get shipping rates with the Stamps.com USPS Shipping API?

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

### What are the rate limits for the Stamps.com USPS 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 get shipping rates through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get shipping rates'. Jentic returns the matching Stamps.com USPS Shipping API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Stamps.com USPS Shipping API have?

The Stamps.com USPS Shipping API exposes 11 endpoints covering account, addresses, insurance operations.

### Can I limit what my agent is allowed to do with the Stamps.com USPS Shipping API?

Yes. Jentic One runs self-hosted, so your own rules decide which of the API's operations your agent may call and which credentials it may use. You can allow read and status calls such as GET /labels/{labelId} and GET /tracking/{trackingNumber} while withholding write operations, and because the label id sits in the URL path you can pin the agent to a specific label. Destructive operations like POST /labels/{labelId}/void or POST /pickups are excluded unless you explicitly add them.