The API behind every unit you sell
One REST API for inventory, orders, shipping and analytics, across every channel your sellers list on. Signed webhooks. A CLI that covers all of it. Docs your agent can read.
$ curl https://api.stockpilot.dev/inventory?page_size=1 \ -H "X-CLIENT-ID: $SP_CLIENT_ID" \ -H "X-CLIENT-SECRET: $SP_CLIENT_SECRET" { "count": 1284, "results": [{ "sku": "201156", "quantity": 150, "reserved_quantity": 3, "bin_location": ["A1-001-01"] }] }
API reference
Every endpoint, parameter and response, all 74 of them. Generated from the live schema, so it is never out of date.
Open the referenceTutorials
Working code, not pseudocode. Receive a webhook, buy a label, build a reorder bot, wire up an ERP.
Browse tutorialsCommand line
Your warehouse in the terminal. 77 commands, every one of them scriptable.
Install the CLIStart here
What you can build
Every one runs against the live API today. Nothing here is waiting on a roadmap.
Agent-ready
Your agent already knows how to use it
Point it at one URL. It reads the whole API and starts writing calls that work.
- llms.txt puts all 74 operations in one file, small enough to drop into any context window.
- llms-full.txt adds every parameter, request body and real response.
- openapi.json generates you a typed client in any language.
- SKILL.md teaches agents the CLI, and ships with it.
All four come straight off the schema on every request. They cannot go stale.
# point any agent at the whole API > Read https://api.stockpilot.dev/llms.txt > then list every SKU that runs out > within two weeks. Reading llms.txt … 74 operations GET /inventory?page_size=1000 GET /analytics/items/sales 7 SKUs below two weeks of cover: 201156 42 units · 9d 330012 18 units · 4d
Surface area
One API, the whole operation
The same objects the Stockpilot app runs on, not a trimmed down public subset.
Start now
You are five minutes from your first call
Generate a key in the app and go. No sandbox to request, no approval to wait for.
