Government RFP & Tender Monitor avatar

Government RFP & Tender Monitor

Pricing

from $10.00 / 1,000 tender results

Go to Apify Store
Government RFP & Tender Monitor

Government RFP & Tender Monitor

Monitor public government procurement portals for new RFPs, tenders, and bids. Structured JSON output with tender title, authority, closing date, value, and document links.

Pricing

from $10.00 / 1,000 tender results

Rating

0.0

(0)

Developer

Technical Dost Solutions

Technical Dost Solutions

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

0

Monthly active users

13 days ago

Last modified

Share

What this Actor does

Monitor public government procurement, tender, and RFP listing pages and extract new tenders as clean, structured JSON.

It processes user-provided public URLs (such as national procurement portals, state e-tender pages, or public agency notice boards), prioritizes JSON-LD/schema.org structured data, and can optionally use a conservative fallback that reads visible public tender links and table rows. It normalizes useful fields, applies an optional keyword filter, deduplicates rows by tender URL, and saves structured records to the Apify dataset.

Why this Actor is useful

Suppliers, bid teams, and analysts pay for this kind of extraction because it replaces manual portal checking, creates repeatable daily or weekly monitoring, feeds spreadsheets, CRMs, and bid pipelines, and turns scattered public procurement pages into a clean, API-ready dataset.

Who this is for

  • Government suppliers and contractors
  • Bid and proposal (RFP) teams
  • Procurement and tender consultants
  • Construction, IT, and services vendors
  • Market intelligence and GovTech analysts
  • Trade associations and chambers of commerce
  • Researchers tracking public spending

Common use cases

  • Track new tenders across multiple government portals
  • Filter opportunities by keyword (e.g. "construction", "IT services")
  • Feed a bid pipeline or CRM with fresh RFP leads
  • Monitor a specific issuing authority or region
  • Build recurring public-procurement intelligence datasets

Input

FieldTypeDescription
startUrlsarray (required)Public tender/RFP/procurement listing pages to extract from. Use only pages you may access without login or bypassing access controls.
keywordsarray of stringsOptional keywords. Only tenders whose title or surrounding text contains at least one keyword (case-insensitive) are kept. Empty = no filter.
maxItemsintegerMaximum rows to save. Default 50, min 1, max 10000.
maxConcurrencyintegerPages processed in parallel. Default 3, min 1, max 20.
extractionModestringstructuredDataOnly or structuredDataWithFallback (default). The fallback safely reads visible public tender listings.
requestTimeoutSecsintegerMaximum time per page. Default 30, min 5, max 180.
proxyConfigurationobjectOptional Apify proxy configuration where permitted by your source review.

Output

FieldDescription
tenderTitleTitle of the tender, RFP, or bid notice.
tenderIdTender / NIT / reference number when present.
issuingAuthorityDepartment or agency issuing the tender.
categoryTender category or type when available.
locationRegion, state, or location of the work.
publishedDateDate the tender was published or issued.
closingDateBid closing / last submission date.
estimatedValueEstimated contract value when published.
currencyCurrency of the estimated value (e.g. INR, USD, EUR).
tenderUrlPublic URL of the tender detail page.
documentUrlPublic link to the tender document/notice when available.
sourceUrlURL where the data was extracted.
detectedAtTimestamp when this Actor extracted the row.
extractionMethodstructured_data for schema data, or fallback_public_tender_listing for visible public listings.
confidenceScoreHeuristic confidence based on structured data availability and completeness.
missingFieldsRequired fields that were not available from the source page.

Sample input

{
"startUrls": [
{
"url": "https://www.contractsfinder.service.gov.uk/Search/Results"
}
],
"maxItems": 25,
"maxConcurrency": 3,
"extractionMode": "structuredDataWithFallback",
"requestTimeoutSecs": 30
}

Sample output

A real row from the UK Contracts Finder results page:

{
"tenderTitle": "Fully Managed Renal Dialysis Satellite Unit in Crawley Area",
"issuingAuthority": "Epsom and St Helier University Hospitals NHS Trust",
"category": "Opportunity",
"location": "England",
"publishedDate": "22 October 2026",
"closingDate": "25 November 2026, 12pm",
"estimatedValue": 1600000,
"currency": "GBP",
"tenderUrl": "https://www.contractsfinder.service.gov.uk/notice/9a893374-3f8e-4d6e-b469-2be04291acb6?origin=SearchResults&p=1",
"sourceUrl": "https://www.contractsfinder.service.gov.uk/Search/Results",
"detectedAt": "2026-10-23T00:10:00.000Z",
"extractionMethod": "fallback_public_tender_listing",
"confidenceScore": 0.8,
"missingFields": []
}

Pricing

This Actor uses a pay-per-event model: $0.005 per tender result saved to the dataset. You pay only for the structured tender rows you receive, which makes recurring monitoring predictable and low-cost.

How to use

Run this Actor on Apify with public tender portal URLs, export the dataset as JSON, CSV, or Excel, or pull it through the Apify API. Connect the output to Google Sheets, Make, Zapier, a webhook, your CRM, or an internal bid dashboard. For monitoring, save the input as an Apify task and schedule recurring runs to catch new tenders.

Best practices

  • Start with a small set of reviewed public procurement URLs.
  • Prefer portals that expose schema.org / JSON-LD structured data.
  • Use keywords to focus on the sectors or services you bid on.
  • Use structuredDataOnly for highest precision; use structuredDataWithFallback for portals that only show visible tender tables.
  • Keep maxConcurrency low for smaller portals.
  • Review each source website's rules before scheduling recurring runs.

Compliance and responsible use

This Actor is for public data only. It must not be used to bypass logins, paywalls, CAPTCHAs, or security systems, to collect private or sensitive personal data, or to support spam or abuse. Government procurement information processed here should be publicly published tender notices. You are responsible for following applicable laws and each source website's rules.

Limitations

  • Output quality depends on the public structured data available on the source pages.
  • Fallback extraction is intentionally conservative and only looks for visible public tender/RFP/bid link and table patterns. It does not claim universal portal support.
  • Dates and amounts are extracted as published; formats vary by country and portal and are not reformatted or converted.
  • Some fields may be empty when the source does not publish them; these appear in missingFields.
  • The Actor does not claim support for any specific third-party procurement platform.
  • Website markup and access policies can change.

Troubleshooting

  • Empty output usually means the page has no public structured tender data and no visible tender-link patterns.
  • Invalid URL errors mean one or more input URLs are malformed.
  • Slow runs can usually be improved by lowering maxConcurrency.
  • Missing fields are source-data limitations, not inferred values.

Changelog

  • v0.1.0: Initial release with structured-data-first extraction, conservative public tender-listing fallback, keyword filtering, and confidence scoring.

Use Government RFP & Tender Monitor with AI agents (MCP)

Give Claude, ChatGPT, Cursor, VS Code or any MCP client this Actor as a tool through the hosted Apify MCP server. The agent sees the input fields with descriptions and example values, runs the Actor, and reads the results.

MCP server URL (this Actor only):

https://mcp.apify.com/?tools=technicaldost/gov-rfp-tender-monitor

Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com/?tools=technicaldost/gov-rfp-tender-monitor" --header "Authorization: Bearer YOUR_APIFY_TOKEN"

Cursor, VS Code, Claude Desktop and other clients (mcp.json or the client's MCP settings):

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com/?tools=technicaldost/gov-rfp-tender-monitor",
"headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
}
}
}

Clients that support sign-in (such as Claude.ai connectors) can use the URL without a token and log in to Apify instead. Get your token in Apify Console → Settings → API & Integrations, or generate a ready config for your client at mcp.apify.com. In the agent the tool is named technicaldost--gov-rfp-tender-monitor; ask it, for example, to "run Government RFP & Tender Monitor with {"startUrls": [{"url": "https://www.find-tender.service.gov.uk/Search/Results"}], "maxItems": 20}".

AI agents without an Apify account can also run and pay for this Actor per request with x402 agentic payments.

Run Government RFP & Tender Monitor via API

Run the Actor and get its results in one call (replace YOUR_APIFY_TOKEN):

curl -X POST "https://api.apify.com/v2/acts/technicaldost~gov-rfp-tender-monitor/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"startUrls": [{"url": "https://www.find-tender.service.gov.uk/Search/Results"}], "maxItems": 20}'

Python (pip install apify-client):

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("technicaldost/gov-rfp-tender-monitor").call(run_input={"startUrls": [{"url": "https://www.find-tender.service.gov.uk/Search/Results"}], "maxItems": 20})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

JavaScript / TypeScript (npm install apify-client):

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('technicaldost/gov-rfp-tender-monitor').call({"startUrls": [{"url": "https://www.find-tender.service.gov.uk/Search/Results"}], "maxItems": 20});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Long runs: start them with POST /v2/acts/technicaldost~gov-rfp-tender-monitor/runs and fetch the dataset when the run finishes, or receive a webhook.

FAQ

Can I use Government RFP & Tender Monitor with AI agents like Claude or ChatGPT?

Yes. Connect the Apify MCP server with ?tools=technicaldost/gov-rfp-tender-monitor (see above) and the agent can run the Actor and read its results on its own.

Can I call Government RFP & Tender Monitor from my own code?

Yes. Use the REST API, or the official Python and JavaScript clients shown above. Results are available as JSON, CSV, Excel, XML or HTML.

How do I run it on a schedule?

Save your input as a task in Apify Console and add a schedule (for example, daily). Use webhooks or integrations to send each run's results onward.

It works with publicly available data. Make sure your use complies with the source website's terms and with data protection laws such as GDPR, especially for personal data.

Something doesn't work or I need a feature. What should I do?

Open an issue in the Issues tab on this Actor's page with an example input, and we'll look into it.