Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.receiptor.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Why workspace context exists

Receiptor users can belong to multiple workspaces. Non-session interfaces (API key, CLI, MCP) must run in an explicit workspace context.

​
List available workspaces (REST)

curl -s https://developer.api.receiptor.ai/v1/workspaces \
  -H "Authorization: Bearer $RECEIPTOR_API_KEY"
Response includes:
  • currentOrgId
  • workspaces[] with orgId, orgName, role, isCurrent

​
Apply workspace to capability execution (REST)

curl -s -X POST https://developer.api.receiptor.ai/v1/capabilities/documents.search \
  -H "Authorization: Bearer $RECEIPTOR_API_KEY" \
  -H "X-Receiptor-Org-Id: org_..." \
  -H "Content-Type: application/json" \
  -d '{"query":"uber"}'

​
CLI workspace commands

receiptor workspace --status
receiptor workspace list
receiptor workspace use org_...
receiptor workspace clear
CLI uses selected workspace by sending X-Receiptor-Org-Id on capability calls. RECEIPTOR_ORG_ID env var overrides config for one-off runs.

​
Capability equivalent

workspaces.list is also exposed in capability discovery and MCP tooling for workspace listing use cases.

​
Workspace-scoped defaults

Non-session interfaces also resolve workspace-scoped defaults from the selected organization context. That includes preferred currency. The active workspace currency takes precedence over the user profile currency, with usd as the final fallback. Receiptor AI memory retrieval is also workspace-scoped. Long-term operational memory does not fall back to a personal workspace-less mode.