kadi_bence/gov-tenders-scraper
kadi_bence--gov-tenders-scraperThis tool calls the Actor "kadi_bence/gov-tenders-scraper" and retrieves its output results. Actor description: $2.90 per 1,000 notices. Search UK and Australian government tenders and contract awards (Find a Tender, Contracts Finder, AusTender) via OCDS APIs. Input: sources, keywords, CPV/UNSPSC codes, notice types, dates, value range, buyer. Returns per notice: title, buyer, category, value, deadline, URL.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "kadi_bence--gov-tenders-scraper"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| regions | No | Buyer region or place of performance, prefix match. UK: ITL/NUTS codes like UKI (London), UKM (Scotland), UKL (Wales) or names like 'England'. Australia: ACT, NSW, VIC, QLD ... | |
| sources | No | Official procurement services to search. UK Find a Tender = higher-value UK notices (Procurement Act 2023). UK Contracts Finder = English public contracts over £12k-£30k, mostly awards. AusTender = Australian Government contract notices (awarded contracts only). Example values: ["uk_fts","uk_cf","au_austender"] | |
| keywords | No | Words or phrases searched in the title, description, buyer name and category label, e.g. 'software', 'cleaning'. Several lines = any of them (OR). Accents and case don't matter, and a term also matches inside longer words, so avoid very short terms like 'IT'. AusTender rows have no description, so there keywords only search title and buyer. Leave empty for all notices. | |
| maxValue | No | Same rule as above. | |
| minValue | No | Estimated value, or the awarded value when there is no estimate, in the notice's currency (GBP for UK, AUD for Australia). Notices without a value are excluded when you set this. | |
| waitSecs | No | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget. | |
| buyerName | No | Words in the buyer's name, e.g. 'NHS', 'County Council' or 'Department of Defence'. | |
| maxResults | No | Stop after this many notices in total (shared fairly across the sources). 0 = no limit. The default without input (API, MCP and AI-agent calls) is 20. Example values: 20 | |
| monitorName | No | Keeps separate 'already seen' lists for different schedules. Changing any filter also starts a new list. Example values: "default" | default |
| noticeTypes | No | Leave empty for all. 'Tender' = open calls you can bid on (with deadlines). 'Award' = who won and for how much. 'Planning' = pipeline and pre-market engagement notices. AusTender only has awards. | |
| publishedTo | No | Last publication date (YYYY-MM-DD). Default: today. | |
| categoryCodes | No | UK notices use CPV codes (e.g. 72000000 IT services, 45000000 construction), AusTender uses UNSPSC (e.g. 43230000 software, 80101500 consulting). Sub-categories are included: 72000000 also matches 72220000. You can type a short prefix like 72. Codes are checked against every selected source, so a CPV code can also match an unrelated UNSPSC code that starts with the same digits. For clean results, run UK (CPV) and AusTender (UNSPSC) searches separately. | |
| deadlineAfter | No | Only tenders you can still bid on: deadline on or after this date. Accepts YYYY-MM-DD, 'today' or '+14 days'. Notices without a deadline (awards, planning) are excluded when you set this. | |
| publishedFrom | No | First publication date (YYYY-MM-DD). | |
| includeUpdates | No | Also return changed or corrected notices (tender updates, award updates, contract changes). Turn off to get first publications only. Example values: true | |
| onlyNewNotices | No | Remember returned notices and output only NEW ones on the next runs with the same search. Ideal for a daily schedule: you only pay for new notices. | |
| proxyConfiguration | No | Not needed: all sources are official open-data APIs. Example values: {"useApifyProxy":false} | |
| publishedWithinDays | No | e.g. 3 for the last three days, 0 for today only. When set, it replaces the 'Published from / to' dates below. Leave empty to use the date range below (default: last 30 days). Example values: 3 |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key | |
| runId | Yes | Actor run ID | |
| stats | No | Run statistics | |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED | |
| actorId | Yes | Stable Apify Actor ID from the run record | |
| summary | Yes | Past-tense summary of the run state | |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) | |
| nextStep | Yes | One primary follow-up action with identifiers interpolated | |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. | |
| actorName | No | "username/actor-name" | |
| startedAt | No | ISO timestamp when the run started | |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) | |
| statusMessage | No | Pass-through from Apify run.statusMessage | |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |