# Public Procurement/RFP Signal Agent (`jacksu/public-procurement-rfp-signal-agent`) Actor

Analyze public procurement, RFP, RFQ, tender, solicitation, and bid pages for buyer, notice type, status, deadlines, scope, submission instructions, documents, budget hints, evidence, risks, and change hashes.

- **URL**: https://apify.com/jacksu/public-procurement-rfp-signal-agent.md
- **Developed by:** [jack su](https://apify.com/jacksu) (community)
- **Categories:** Business, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Public Procurement/RFP Signal Agent

Extract structured evidence from public procurement, RFP, RFQ, tender, solicitation, bid, and business-opportunity pages: buyer hints, notice type, status, deadlines, question deadlines, published or award dates, budget/value hints, eligibility requirements, scope, submission instructions, document links, contact evidence, categories, risk labels, evidence URLs, and stable change hashes.

This Actor is built for AI agents, bid-tracking workflows, sales teams, market researchers, procurement analysts, and vendor qualification systems that need a compact public evidence record without logging into procurement portals or crawling government databases.

### What It Returns

- Notice title, notice type, procurement status, and opportunity hints from public page text.
- Buyer, jurisdiction, location, deadline, question deadline, published date, award date, budget/value, and category evidence.
- Scope, eligibility, submission instruction, contact, CPV/NAICS, and official document-link hints.
- Optional `focusTerms` matches, evidence snippets, evidence URLs, risk labels, missing fields, and a stable `procurementNoticeHash`.
- Change status when you pass previous records from an earlier run.

### Pricing Behavior

The Actor uses pay-per-event pricing and only charges the useful result event when it finds useful public procurement/RFP evidence.

Paid event:

- `useful-procurement-rfp-result`

It does not charge the useful event for:

- invalid or private-network URLs;
- failed fetches;
- generic company, news, partner, hiring, or case-study pages without procurement evidence;
- weak pages that only mention procurement without buyer/deadline/scope/submission/document evidence;
- `focusTerms` misses;
- unchanged records when you pass a previous `procurementNoticeHash`;
- duplicate normalized URLs in the same run.

`apify-default-dataset-item` is intentionally not used.

### Scope And Safety

- Public HTTP/HTTPS HTML or text pages only.
- Private-network hosts, credentials, query strings, fragments, path parameters, and token-like account paths are rejected.
- JavaScript is not executed.
- Forms are not submitted.
- Procurement portals are not logged into.
- PDF files, bid packages, addenda, attachments, vendor registration links, and external document links are recorded as evidence links only and are not fetched.
- The Actor does not crawl procurement databases, scrape private supplier accounts, submit bids, provide legal advice, or guarantee eligibility.
- Output is evidence-based and should be reviewed before bid/no-bid, sales, compliance, or legal decisions.

### Example Input

```json
{
  "procurementPageUrls": [
    "https://northwestcolorado.org/about-us/rfps-and-proposals/"
  ],
  "focusTerms": [
    "RFP"
  ],
  "requestTimeoutSecs": 20
}
```

### Best Use Cases

- Turn a public RFP, RFQ, tender, or bid page into AI-ready evidence.
- Monitor public procurement opportunity pages without paying for unchanged results.
- Extract deadlines, submission instructions, document links, and scope hints before deeper manual review.
- Filter procurement pages by focus category, buyer, geography, or service keyword.

# Actor input Schema

## `procurementPageUrls` (type: `array`):

Public HTTP/HTTPS procurement, RFP, RFQ, tender, solicitation, bid, or business-opportunity page URLs. Query parameters, fragments, credentials, path params, private-network hosts, and token-like account paths are rejected.

## `focusTerms` (type: `array`):

Optional industries, categories, locations, buyer names, notice types, or opportunity keywords that must appear in visible public evidence before the useful result event is charged.

## `previousProcurementRecords` (type: `array`):

Optional previous records from this Actor. If the stable procurementNoticeHash is unchanged for the same URL, the result is written without charging the useful event.

## `requestTimeoutSecs` (type: `integer`):

Maximum time in seconds to wait for the public page response.

## Actor input object example

```json
{
  "procurementPageUrls": [
    "https://northwestcolorado.org/about-us/rfps-and-proposals/"
  ],
  "focusTerms": [],
  "previousProcurementRecords": [],
  "requestTimeoutSecs": 20
}
```

# Actor output Schema

## `datasetId` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jacksu/public-procurement-rfp-signal-agent").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("jacksu/public-procurement-rfp-signal-agent").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call jacksu/public-procurement-rfp-signal-agent --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=jacksu/public-procurement-rfp-signal-agent",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/0MhrrzmAHnjIG86bd/builds/G3cJbsQ4dFMte7AMA/openapi.json