Seller API and MCP

After your listing claim is approved, create API keys in the seller dashboard. Keys start with lcs_ and are shown only once when created or rotated.

Authentication

Send your key on every request:

Authorization: Bearer lcs_…

Each key is scoped to your claimed listing. Requests for other listings return 404 (not 403) so IDs are not leaked.

REST API

Base URL: https://localcutguide.com/api/seller/v1

Method	Path	Scope
GET	/listings	read
GET	/listings/:id	read
PATCH	/listings/:id/profile	profile:write
GET	/listings/:id/offers	read
POST	/listings/:id/offers	offers:write
PATCH	/offers/:offerId	offers:write
PATCH	/offers/:offerId/availability	offers:write
DELETE	/offers/:offerId	offers:write
PUT	/listings/:id/locations	locations:write
GET	/listings/:id/edits	read

Example

curl -s -H "Authorization: Bearer lcs_YOUR_KEY" \
  https://localcutguide.com/api/seller/v1/listings

MCP

JSON-RPC-style POST to https://localcutguide.com/mcp/seller with the same Authorization header.

{
  "method": "tools/call",
  "params": {
    "name": "seller_list_listings",
    "arguments": {}
  }
}

Tools mirror REST capabilities: seller_list_listings, seller_get_listing, seller_update_profile, seller_list_offers, seller_upsert_offer, seller_set_availability, seller_retire_offer, seller_set_locations, seller_list_edits.

Key scopes

read: list listings, offers, and edit history
profile:write: update about text and availability fields
offers:write: create, update, or retire offers
locations:write: replace pickup and market locations

Rate limits

Seller API traffic is limited to about 120 requests per minute per API key (rolling one-minute window). Over-limit requests receive 404.

Back to For sellers