Government Tender Monitor API (SAM.gov + TED)

Track, score, and deduplicate public tenders from US SAM.gov and EU TED. Built for agencies, B2B sales teams, bid managers, and procurement intelligence workflows.

What this Actor does:

• Source connectors: SAM.gov + TED
• Normalized output schema
• Deduplication via hash(source + noticeId + deadlineAt)
• Relevance scoring and risk flags
• Delivery modes: dataset (default), webhook (implemented), email (placeholder)
• Retry with exponential backoff for transient HTTP failures

Use cases:

• Daily government RFP watchlist
• Cybersecurity / cloud tender pipeline generation
• Public sector lead monitoring
• Regional tender scouting across US + EU

Recommended first run:

• jurisdictions: us,eu
• keywords: cybersecurity, cloud migration, zero trust
• minValue: 100000
• daysAhead: 30
• delivery: dataset

Local Run

1. Set secrets in .env:

cd /volume1/docker/Apify/procurement-intel-actor
cp -n .env.example .env
# then edit .env and paste your real keys

2. Run:

cd /volume1/docker/Apify/procurement-intel-actor
cp -n input.example.json input.json
./scripts/run-with-env.sh
cat output/results.json

The provided input.example.json is configured for a live cloud run by default.

Input

Use input.json or APIFY_INPUT_PATH.

Important fields:

• jurisdictions: ["us","eu"]
• keywords: string list
• cpvCodes, naicsCodes
• minValue
• daysAhead
• delivery: dataset|webhook|email
• webhookUrl when delivery=webhook
• samFixturePath, tedFixturePath for offline verification

Detailed schema: INPUT_SCHEMA.json Output schema: OUTPUT_SCHEMA.json

Output Schema (notice)

Each record contains:

• source (sam|ted)
• noticeId
• title
• buyer
• country
• publishedAt
• deadlineAt
• estimatedValue
• currency
• tags
• relevanceScore (0-100)
• riskFlags
• url
• dedupeHash

Keywords

SAM.gov API, TED tenders API, government tenders, public procurement, RFP monitor, bid intelligence, tender alerts, procurement pipeline.

Tests

$npm test

Live TED smoke test:

$npm run smoke:live

OpenClaw Cron Example

Once the actor is deployed, you can schedule from OpenClaw by invoking the Apify run API.

/volume1/docker/Apify/procurement-intel-actor/openclaw-cron-example.sh

This script auto-loads .env in the same directory.

Apify Cloud Scheduler

If you run fully on Apify cloud (recommended for home PC outages), use Apify Task + Schedule.

Required env keys in .env:

• APIFY_TOKEN
• APIFY_ACTOR_ID
• APIFY_TASK_ID
• APIFY_SCHEDULE_ID

One-time setup / idempotent update:

cd /volume1/docker/Apify/procurement-intel-actor
set -a && source .env && set +a
npm run apify:cloud:setup

Manual run from task:

$curl -sS -X POST "https://api.apify.com/v2/actor-tasks/${APIFY_TASK_ID}/runs?token=${APIFY_TOKEN}"

Check schedule:

$curl -sS "https://api.apify.com/v2/schedules/${APIFY_SCHEDULE_ID}?token=${APIFY_TOKEN}"

Disable / enable schedule:

curl -sS -X PUT "https://api.apify.com/v2/schedules/${APIFY_SCHEDULE_ID}?token=${APIFY_TOKEN}" \
  -H "content-type: application/json" \
  -d '{"isEnabled":false}'

curl -sS -X PUT "https://api.apify.com/v2/schedules/${APIFY_SCHEDULE_ID}?token=${APIFY_TOKEN}" \
  -H "content-type: application/json" \
  -d '{"isEnabled":true}'

Pricing Playbook (PPE)

Recommended staged pricing for apify-default-dataset-item:

• Stage 1 (now): $0.0001
• Stage 2 (after 7 days without churn): $0.0002
• Stage 3 (after another 7 days): $0.0003

apify-actor-start can stay at $0.00005 initially.

Apify enforces a pricing change cooldown (typically 1 month). To schedule the next change:

cd /volume1/docker/Apify/procurement-intel-actor
set -a && source .env && set +a
NEXT_RESULT_PRICE=0.0002 npm run apify:schedule-price

Seed Early Usage

Create a few successful runs to build initial run history:

cd /volume1/docker/Apify/procurement-intel-actor
set -a && source .env && set +a
SEED_RUNS=2 npm run apify:seed-usage

Notes

• SAM often requires an API key; set samApiKey or SAM_API_KEY.
• If SAM key is missing, the actor skips US source and reports a warning instead of hard-failing.
• delivery=dataset pushes notices to Apify default dataset when APIFY_DEFAULT_DATASET_ID and APIFY_TOKEN are present (Apify cloud run). Without them, it keeps local JSON output only.
• If publish is blocked with public profile, enable your Apify public profile once and rerun npm run apify:cloud:setup.
• TED expert query requires explicit fields and query syntax. This actor sends safe defaults.
• For production monetization, add strong schema validation and source-specific contract tests.
• If this Actor saved time for you, please leave a Store review. Early reviews significantly improve discovery in Apify search.