Workspace settings

Make the workspace feel like yours.

These details appear on your public embed and keep the website choice anchored to the work you actually do.

API integrations

Connect your own workflow.

Create a separate staff key for each app or server. You can revoke it without signing out your team.

Save this key now. It is shown only once.

It grants staff access to this workspace. Store it in an encrypted secret manager on your server.

Loading integration keys…

API quick start

Send your staff key as a Bearer token from your server. For a public website, use a scoped website key instead.

POST https://api.seeingsells.ai/api/v1/generations
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: YOUR_UNIQUE_REQUEST_ID

Multipart fields:
source       Customer photo (PNG, JPEG, WebP or AVIF, under 4 MiB)
categoryId   For example: furniture or soft-furnishings
prompt       The colour, finish or requested change
reference    Optional material or swatch photo
productId    Optional catalogue reference
quality      default (1 credit) or premium (2 credits, Business)

A successful request returns a PNG image and the job ID in x-seeingsells-job-id. Reuse the same request ID for the exact same inputs to retry without spending credits twice. Use GET /api/v1/jobs to check saved results.

Agent access

Use this workspace from Claude, ChatGPT, Grok or any MCP agent.

Connect once, then ask your agent to search supplier references, check enquiries, create quote drafts or build a visualisation. Write actions remain approval-gated.

Remote MCPhttps://mcp.seeingsells.ai/mcpOAuth 2.1 for interactive clients · staff API key Bearer auth for automation

Claude

Add a custom connector using the MCP URL. Claude opens the secure SeeingSells authorization screen.

ChatGPT / OpenAI

Add a custom MCP connector or set server_url to the MCP URL in the Responses API.

Grok / xAI

Use a remote MCP tool with the same server_url. Supply the staff API key as Bearer auth for API calls.

Codex and other agents

Configure a remote HTTP MCP server. OAuth-aware clients connect interactively; automation can use the API key securely.

Keep the API key out of chat. Authorize interactive clients through SeeingSells. Store automation keys in your agent platform’s encrypted secret manager.