Sell Ltd Developers
List a business for sale with the Sell Ltd API or MCP
Use your own software or a connected AI agent to prepare a UK business advert, attach photos and video, and publish. Your first eligible advert gets 14 days of marketplace advertising free from publication.
Create a free Sell Ltd account, then choose your key permissions. No subscription or payment card required to get started.
Connect your agent
- Sign up or sign in and verify your email.
- Open API account and create a key with
research:readand the MCP audience. For research only, deselect other permissions. For selling, use the permissions described below. - Add
https://sellltd.co.uk/mcpas a remote Streamable HTTP MCP server in your client, with anAuthorization: Bearer <API_KEY>header.
{
"mcpServers": {
"sellltd": {
"url": "https://sellltd.co.uk/mcp",
"headers": {
"Authorization": "Bearer YOUR_SELL_LTD_API_KEY"
}
}
}
}Configuration formats and support for remote MCP and custom headers differ between Claude, Codex and other clients. Consult your client’s setup instructions. Never paste a key into a chat, publish a configuration containing it, or commit it to source control. Named-client compatibility has not been certified.
Research requests and retries
For search_companies, get_company and calculate_valuation, the agent must provide a unique idempotencyKey tool argument for each new operation. If a response is lost, retry the identical arguments with the same key; do not generate a new key for an uncertain operation. The operation key is not your Sell Ltd API key.
{
"query": "Example Bakery",
"limit": 5,
"idempotencyKey": "search-bakery-001"
}The server exposes this field in tools/list for API-key connections. Reconnect if your client cached an earlier tool list. A pending operation must be reconciled before retrying with a new key.
Research pricing
Your account shares a free allowance across REST and MCP of up to 600 research requests per rolling hour and 5,000 per rolling 24 hours. Beyond that allowance, successful company searches and lookups cost 1p each and indicative valuations cost 5p each. Empty searches, insufficient-data valuations and failures do not use paid credit. Top up from £10: no subscription, automatic top-up or VAT. If there is insufficient credit, the request stops.
Inspect the server
A compatible client normally initializes automatically. Public marketplace browsing is available without a research key. Send a JSON-RPC initialize request followed by tools/list; supply your bearer key when discovering and calling its permitted tools.
curl -X POST https://sellltd.co.uk/mcp \
-H "Authorization: Bearer $SELL_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"example","version":"1.0"}}}'OAuth
Resource audience: https://sellltd.co.uk/mcp. Use authorization-code flow with PKCE S256 and an exact registered redirect. Dynamic registration is supported at /oauth/register. Discovery is available from /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.
The person selects permissions. Publication starts unchecked and must be explicitly allowed. Connections can be restricted to existing adverts and revoked under Connected agents. Access tokens last one hour; refresh tokens rotate and expire after 30 days. Repeat the resource parameter when exchanging/refreshing.
Tools
- Research: search_companies, get_company, calculate_valuation.
- Discovery: search_marketplace, get_listing.
- Adverts: list_my_listings, get_my_listing, save_listing, validate_listing, publish_listing, pause_listing.
- Media: create_media_upload, complete_media_upload.
- Advertising: quote_advertising, create_advertising_checkout.
- Alerts: list_saved_searches, save_search_alert.
Use tools/list for input schemas. Include a stable idempotencyKey on research operations and writes. All ownership, NDA and publication rules are shared with the website.
Sell a business from a conversation
Try asking your connected agent: “Help me sell my bakery. Ask me what you need, keep the address private in the public teaser, and show me a draft before you publish.”
- Create a key with the MCP audience. Keep
account:read,listings:writeandmedia:writefor the seller workflow. Choose all your adverts, including new ones, to let the agent create a draft. Confirmlistings:publishonly if it may publish on your behalf. - Ask about the business name, categories, location, asking price or price on request, financial disclosures, public teaser and confidential description. Online businesses need a website. Other businesses need a region, address and postcode. Confirm authority to sell with the owner.
- Use
save_listingwith seller-approved facts. Offer optional details such as staff, assets or premises, tenure, highlights and handover plans where relevant. Use the fields in the tool schema. To edit a saved draft, read it and send its ID and latest version. - For each file, call
create_media_upload, transfer the actual file bytes to the signed URL, then callcomplete_media_uploadwith the returned media ID. The client needs access to the attachment and an HTTP upload capability. If it cannot transfer the file, the owner can attach it in the advert editor. Choose public or NDA visibility for photos. Uploaded videos and documents stay behind the listing’s NDA. - Call
validate_listing, ask the seller for missing details and check advertising eligibility. The first eligible advert per account gets 14 free days from publication. Additional time is a one-off purchase of 7–365 days. The owner can choose the advert and pay in Advertising & billing, or open the checkout link returned by the agent. - When the seller wants to go live, call
publish_listingwith delegated authority and return the public advert link after success. Otherwise give the owner their draft to review. Payment and signatures are completed by the person.
Use a unique idempotencyKey for each write, and reuse it for an identical retry. See the listing fields, media limits and REST examples.
Troubleshooting and security
- Create a key with the MCP audience and the required scopes, or use OAuth for supported account actions. An OAuth token for the REST audience cannot be used for MCP.
- If you receive HTTP 429, wait for the
Retry-Afterinterval before retrying. Upstream data sources can also impose limits. - A tool failure may be returned as a JSON-RPC tool result with
isError: true; inspect the result rather than assuming HTTP 200 means the action succeeded. - Revoke a lost key in API account or an OAuth connection in Connected agents. Do not share keys, access tokens, passwords or database credentials in chat.
Client configuration formats and OAuth support vary. Check your client’s documentation; compatibility with a particular product has not been certified.
Transport
Stateless Streamable HTTP JSON-RPC POST with JSON responses. Initialize before tools/list or tools/call. No persistent SSE subscription or session ID. Protocol versions: 2026-07-28, 2025-11-25, 2025-06-18 and 2025-03-26. Browser origins require deployment approval; server-side MCP clients do not need an Origin header. REST and MCP token audiences are distinct.
