Fanisa amathenda nemibhalo yomkhiqizo wakho

1. Sign me in yourself. Try this first: you need me only for one approval click.
- If you can send HTTP requests: POST https://app.selltostate.com/api/v1/agent/signup with JSON {"client_name": "<your app name>"}. Show me verification_uri_complete from the reply as a link. I open it, sign up free with Google or email, and approve the code. Every "interval" seconds, POST token_endpoint with {"device_code": "<device_code>"} until the reply has access_token. Send access_token in the x-api-key header to the MCP server https://app.selltostate.com/api/mcp.
- If you cannot send HTTP requests: tell me to add the MCP server https://app.selltostate.com/api/mcp in this app. Its sign-in page also creates the free account. Claude: Customize > Connectors > Add custom connector. ChatGPT: chatgpt.com/plugins > + > Add custom MCP server, choose OAuth. Claude Code: claude mcp add --transport http selltostate https://app.selltostate.com/api/mcp, then /mcp > Authenticate.
2. The tools are free to connect. A free account gets plan_search 3 times a day and search for 2 different searches a day: titles, buyers, status and dates. Amounts, winners and notice links need a plan. Call whoami to see my plan. Read the skill at https://www.selltostate.com/skills/selltostate-document-tender-matching/SKILL.md.
3. When the Sell to State plan_search tool is available, read my product sheet and find tenders that fit it. Until then, search tenders for the products in this text: <paste>.

---
name: selltostate-document-tender-matching
description: Tender matches from your documents with Sell to State data (government tenders and contract awards from official procurement sources). Use when the user gives a product sheet, catalogue or capability statement and asks for tenders that fit it.
---

# Tender matches from your documents (Sell to State)

This feature is in development. Do the steps below and tell the user that the full feature is not available yet.

## Access

1. MCP: the server https://app.selltostate.com/api/mcp (OAuth, or the x-api-key of the agent sign-in: POST https://app.selltostate.com/api/v1/agent/signup, the user approves one code). Call `whoami`. `active` false is a free account: `plan_search` and `search` only, 1-2 searches a day.
2. REST: https://app.selltostate.com/api/v1 with the header `x-api-key`. Read the key from `STS_API_KEY` and never print it.
3. No plan yet: the user picks a plan at https://app.selltostate.com/plans, or you run the agent signup in "Get access" of https://www.selltostate.com/skills/selltostate/SKILL.md. The user pays in the browser.

## Task

When the Sell to State plan_search tool is available, read my product sheet and find tenders that fit it. Until then, search tenders for the products in this text: <paste>.

Ask the user for each value in <angle brackets> before the first call.

## Steps

1. Read the document. Write the product names, the technical terms and the synonyms as short search phrases.
2. Search each phrase: MCP `search` with `scope=tenders`, `q`, `country`, `accepts_bids=true`. REST: `GET https://app.selltostate.com/api/v1/search?scope=tenders&q=<phrase>&accepts_bids=true`.
3. Merge the results, remove duplicates by `id`, and say which phrase matched each tender.
4. Show title, buyer (the part of `sub` before " · "), country, `deadline_at`, value with its currency and `source_url`.

## Rules

- Give `source_url` (the official notice) for each tender and award. The user reads the documents and bids on the official portal.
- Amounts are in the source currency. Do not add amounts in different currencies.
- The data shows awards, not bids. Do not say that a company lost a tender.
- On a 402, show the message and the link to the user, then stop. On a 429, wait `Retry-After` seconds.
- Credit the data: "Data: Sell to State (selltostate.com)".

More skills (open tenders, buyer research, competitor wins, alerts, API reference): https://github.com/getbeton/selltostate-skills