Remote Tech Job & Transparent Salary Filter
Pricing
$3.00 / 1,000 extracted data record / events
Remote Tech Job & Transparent Salary Filter
Filter and extract remote tech job listings featuring transparent salary ranges and equity compensation. Export curated remote leads to clean CSV & JSON. Zero proxies required. Zapier & Make ready. PPE ($0.003/item with 10 free preview records).
Pricing
$3.00 / 1,000 extracted data record / events
Rating
0.0
(0)
Developer
Deepak Sheoran
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Share
⚡ Value Proposition: High-Agency Engineering vs Legacy Scrapers
Most data collection scrapers waste your budget by spinning up heavy headless browsers (Chrome/Puppeteer), demanding expensive $15/GB residential proxies, and crashing when layouts change.
Remote Tech Job & Transparent Salary Filter is architected for production reliability:
- Zero Proxy Tax ($0.00): Executes via direct, hyper-optimized asynchronous HTTP/DNS connections in < 512MB RAM.
- Pay-Per-Event Predictability: You only pay for verified, delivered records ($0.003 / record).
- Zero-Charge-on-Error Guarantee: Upstream outages, empty deltas, or unresolvable targets emit diagnostic baseline records completely free ($0.00).
- Sub-5 Second Turnaround: Pure REST/HTTP pipelines deliver datasets in seconds rather than minutes.
🤖 AI Agent & Model Context Protocol (MCP) Integration
This Actor is packaged as an AI-first tool compatible with Claude Desktop, Cursor IDE, Windsurf, and LangChain / CrewAI agentic workflows.
Agent Trigger Rule:
"Use this tool when the user requests filter linkedin job openings by true remote status and extract transparent pay and salary bands from descriptions. or needs structured JSON data for linkedin-remote-salary-filter without browser overhead or manual cleanup."
Claude Desktop / Cursor claude_desktop_config.json Snippet:
{"mcpServers": {"linkedin-remote-salary-filter": {"command": "npx","args": ["-y", "@apify/mcp-server-apify"],"env": {"APIFY_TOKEN": "YOUR_APIFY_API_TOKEN"}}}}
💰 Unit Economics & Cost Comparison
| Feature | Remote Tech Job & Transparent Salary Filter | Traditional Puppeteer / Playwright Scraper |
|---|---|---|
| Residential Proxy Bandwidth | $0.00 (Zero Proxy Tax) | $12.00 – $25.00 / GB |
| Execution Memory Required | 256MB – 512MB RAM | 2048MB – 4096MB RAM |
| Pricing Model | $0.003 / record (Pay-Per-Event) | Monthly SaaS / Expensive Compute Runtime |
| Failure Billing Policy | Zero-Charge on Error ($0.00) | Billed for full runtime on crash |
| Execution Speed | 2–5 Seconds | 45–120 Seconds |
⚡ 1-Click Integration Blueprints
1. Sync Execution via cURL / REST API
Run the Actor synchronously and retrieve dataset records immediately in one HTTP call:
curl -X POST "https://api.apify.com/v2/acts/deepaksheoran172~linkedin-remote-salary-filter/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{}'
2. Python (apify-client)
from apify_client import ApifyClientclient = ApifyClient("YOUR_APIFY_TOKEN")run_input = {}# Start Actor run and wait for completionrun = client.actor("deepaksheoran172/linkedin-remote-salary-filter").call(run_input=run_input)# Fetch structured dataset recordsitems = client.dataset(run["defaultDatasetId"]).list_items().itemsfor record in items:print(record)
3. n8n / Make.com Webhook Automation
- Node Type: HTTP Request Node
- Method:
POST - URL:
https://api.apify.com/v2/acts/deepaksheoran172~linkedin-remote-salary-filter/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN - Headers:
Content-Type: application/json - Body: Raw JSON
{}
📥 Input Parameters
All properties feature built-in defaults; providing an empty object {} triggers a reliable default scan.
| Parameter | Type | Default | Description |
|---|---|---|---|
keywords | string | Software Engineer | Configure keywords parameter for LinkedIn Remote Jobs & Transparent Salary Range Filter. |
minSalary | integer | 100000 | Configure minSalary parameter for LinkedIn Remote Jobs & Transparent Salary Range Filter. |
proxyConfiguration | object | {'useApifyProxy': False} | Apify Proxy configuration object to route network requests. Uses zero-cost direct HTTP connections by default without proxy fees. |
maxItems | integer | 25 | Maximum total records to extract and deliver to the output dataset during this run (for example 50 or 100 records) to govern compute time and data volume. |
📤 Output Dataset Specification
Output records strictly adhere to the official Apify dataset schema:
| Field Name | Type | Description |
|---|---|---|
company | string | Hiring company. |
currency | string | Currency code (USD, EUR, GBP). |
isRemote | boolean | True if confirmed remote position. |
salaryMax | integer | Discovered max salary. |
salaryMin | integer | Discovered min salary. |
headline | string | Job title. |
title | string | Field 'title' extracted and verified by linkedin_remote_salary_filter. |
❓ Frequently Asked Questions (FAQ)
Q: How does Pay-Per-Event (PPE) pricing protect my budget?
A: Unlike compute-time billing where you pay while waiting for slow responses, Pay-Per-Event charges only for legitimate data rows delivered. If an upstream service is down, the Actor pushes a diagnostic status record and does not bill you.
Q: Can I run this on a recurring schedule?
A: Yes! Use Apify's built-in Scheduler (Cron), or trigger it via Zapier, Make.com, or n8n on a daily, weekly, or hourly cadence.
Q: Are external proxies or browser engines required?
A: No. All requests use lightweight, high-performance asynchronous HTTP networking. There is zero proxy markup and zero browser overhead.
🔍 High-Intent Search & Buyer Keywords
b2b lead enrichment, clay.com alternative, n8n http request scraper, bulk email mx smtp validator, cold email lead cleaner, executive email finder, zero-proxy API