For developers and agents
There is an API behind this shop.
Everything on these shelves is available as structured data. The same catalog that fills the shop answers directly, so an assistant does not have to read the page to know what something costs.
Get a key
curl -sX POST https://deverra.devilabs.dev/api/v1/keys \
-H 'content-type: application/json' \
-d '{"email":"you@example.com"}'
# => {"id":"k_...","key":"dl_live_...","rate_limit":600}
Search
curl -sX POST https://deverra.devilabs.dev/api/v1/search \
-H "x-api-key: $KEY" -H 'content-type: application/json' \
-d '{"query":"running shoes","limit":10}'
Endpoints
| Endpoint | Returns |
|---|---|
| POST /api/v1/search | Products with every shop's price |
| GET /api/v1/product/{id} | One product, fully hydrated |
| GET /api/v1/product/{id}/offers | Offers only, cheapest first |
| GET /api/v1/product/{id}/history | 90-day price statistics |
| POST /api/v1/similar | Related products |
| POST /mcp | Same tools over MCP |
Connect an agent instead
If you would rather your assistant handled it, point it at /connect. It reads agent.md, registers its own key, and tells you what it can see before it starts.
What we collect
A hashed key, your email, and a count of calls. Not your prompts, not your end users, not payment details — there is no payment surface. Full detail at /privacy.
Connect an agent agent.md OpenAPI
0 products currently shelved on Deverra.