Install Jentic One Beta

Connect the Droppery REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Droppery REST 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%2Fdroppery.io%2Fdroppery" | sh

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%2Fdroppery.io%2Fdroppery" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Droppery REST API.

List the dropshipping product catalog via GET /products

Retrieve a single product's details via GET /products/{productId}

Read live inventory counts via GET /products/{productId}/inventory

Place a dropshipping order via POST /orders

Look up an order's status via GET /orders/{orderId}

GET STARTED

Start building with Droppery REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Droppery REST API for, with concrete tasks.

★ Storefront Catalog Sync

Pull the Droppery product list into a Shopify or WooCommerce storefront and refresh inventory regularly so listings reflect supplier stock. The agent calls GET /products on a schedule and GET /products/{productId}/inventory for hot SKUs to avoid overselling on low-stock items.

Call GET /products to list the catalog, then for each productId call GET /products/{productId}/inventory and update the storefront listing with current stock

Order Forwarding to Droppery

Forward storefront orders to Droppery for fulfilment immediately after checkout. POST /orders accepts the product line items and shipping address, and the agent then polls GET /orders/{orderId} for status and GET /orders/{orderId}/tracking for carrier details to surface in the buyer's order page.

On checkout-completed, POST /orders with line items and shipping address, store the returned orderId, and poll GET /orders/{orderId}/tracking until a tracking number is available

Agent-Driven Dropshipping via Jentic

Wire Droppery into agent workflows that source, price, and fulfil products without exposing supplier credentials. Through Jentic the agent searches by intent, loads the schema for the right operation, and executes - the X-API-Key never enters the agent's prompt context.

Search Jentic for 'place a dropshipping order', load the Droppery /orders schema, and execute with line items supplied by the parent storefront agent

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for droppery rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/products

List products

GET

/products/{productId}

Get a product

GET

/products/{productId}/inventory

Get product inventory

POST

/orders

Create an order

GET

/orders/{orderId}

Get an order

GET

/orders/{orderId}/tracking

Get order tracking

GET

/products

List products

GET

/products/{productId}

Get a product

GET

/products/{productId}/inventory

Get product inventory

POST

/orders

Create an order

GET

/orders/{orderId}

Get an order

GET

/orders/{orderId}/tracking

Get order tracking

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Droppery API by hand means handling its X-API-Key auth and building the product and order calls yourself. Through Jentic you install once, import Droppery from the API Directory, store the key once, and your agent calls it.

Permission scoping

Droppery puts the product and order ids in the URL path (/products/{productId}, /orders/{orderId}), so a rule can pin your agent to reading catalog and order data. You choose the operations it may call, so placing an order is not included unless you add it.

Credential isolation

Your Droppery API key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list dropshipping products' or 'check order tracking', and Jentic returns the matching Droppery operation with its input schema so the agent calls the right endpoint without browsing the docs.

FAQs

Specific to using Droppery REST API through Jentic.

Why is there no official OpenAPI spec for Droppery REST API?

Droppery does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Droppery REST API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Droppery REST API use?

Droppery uses an API key passed in the X-API-Key header. Through Jentic the key is stored in the encrypted vault and injected at execution, so it never enters the agent's prompt.

Can I place a dropshipping order with the Droppery REST API?

Yes. POST /orders accepts the line items and shipping details and returns an orderId. Use GET /orders/{orderId}/tracking to retrieve the carrier number once shipped.

What are the rate limits for the Droppery REST API?

The OpenAPI spec does not declare rate limits. Have your agent handle 429 responses with exponential backoff, and confirm your plan's quota with Droppery support.

How do I sync product inventory with the Droppery REST API through Jentic?

Search Jentic for 'check product inventory', load the schema for GET /products/{productId}/inventory, and execute on a schedule for the SKUs you list. Install with pip install jentic.

Does the Droppery REST API expose webhooks?

The current spec only exposes GET and POST endpoints under /products and /orders, with no webhook surface. Use polling on GET /orders/{orderId}/tracking for fulfilment updates.

Can I limit what my agent is allowed to do with the Droppery REST API?

Yes. Because you run Jentic One yourself, your own rules decide which Droppery operations and credentials the agent may use. Since Droppery puts the product and order ids in the URL path (/products/{productId}, /orders/{orderId}), you can pin the agent to read-only calls such as GET /products, GET /products/{productId}/inventory, and GET /orders/{orderId}/tracking. Placing an order via POST /orders is not included unless you add it, and the X-API-Key is injected at execution rather than exposed to the agent.

Droppery REST API

Name: Droppery REST API
Brand: Droppery REST API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticE CommerceInventoryapiKey7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Browse the Droppery dropshipping catalog, place orders, and check inventory and shipment tracking. Useful for storefront agents that need a managed supplier feed.

Use for: I need to place a dropshipping order on behalf of a customer, List all products available in the Droppery catalog, Check the current stock level for a product, Get tracking information for a recent order

Not supported: Does not handle storefront hosting, payment processing, or returns management - use for dropshipping catalog access and order placement only.

Jentic publishes the only available OpenAPI specification for Droppery REST API, keeping it validated and agent-ready. Droppery is a dropshipping platform that connects webshops to a managed product catalog, fulfils orders, and synchronises inventory levels. The API provides seven endpoints to list and read products, retrieve inventory counts, place and read orders, and fetch tracking information. Authentication uses an API key passed in the X-API-Key header.

Jentic One on Github View OpenAPI Document