Build with your inventory

Your inventory is useful beyond one app. Let a script keep records in sync, or ask an assistant to inspect photos and suggest useful names.

01 / REST API

Build an integration

Inventory, private photos, tags, history, exports, and label printing.

Start with the API →02 / MCP SERVER

Connect an assistant

Find unnamed objects, inspect images, review suggestions, and apply a batch.

Set up MCP →

Your first request

Create an access token with inventory:read, place it in the STUFFOWL_TOKEN environment variable, and list unnamed photographed items:

Terminal

curl --fail-with-body \
  -H "Authorization: Bearer $STUFFOWL_TOKEN" \
  'https://stuffowl.com/api/v1/nodes?kind=item&unnamed=true&hasPhoto=true&limit=25'

The response contains nodes and nextCursor. Every result belongs to the inventory you authorized.

Built around your control

Specific permissions. Reading metadata, viewing photos, deleting records, and printing labels have separate scopes.
Review before applying. Enrichment previews store proposed changes. Apply and undo reject conflicting edits.
Permanent identity. Renaming or moving an item never changes its UUID or printed label URL.
Your assistant, your model. StuffOwl serves the data and tools. Inference uses your assistant’s plan or API billing.

One API, multiple clients

The mobile app and integrations use the same versioned API. MCP tools call these same handlers. Download the OpenAPI 3.1 document or browse the endpoint reference.

API access does not add an AI subscription to StuffOwl. Existing storage limits still apply. An assistant connection does not automatically analyze every new photo in the background.