# Techmeme Tech News Scraper (`scrapyx/techmeme-tech-news-scraper`) Actor

Fetches Techmeme's curated tech-news river -- headline, author, source publication, article link and Techmeme's own social permalinks for every story currently listed, typically ~100-160 spanning the trailing several days.

- **URL**: https://apify.com/scrapyx/techmeme-tech-news-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.10 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

## Techmeme Tech News Scraper

Fetches Techmeme's curated tech-news river: the headline, author, source
publication, original article link and Techmeme's own social-post
permalinks (Twitter/X, Mastodon, Threads, Bluesky) for every story
currently on the page.

### What you get

One `SEARCH_SUMMARY` row plus one `STORY` row per story, most-recent-first:

- `storyHeadline`, `storySourceName`, `storySourceUrl`, `storyAuthorName`
- `storyArticleUrl` -- the original publisher's article
- `techmemeUrl` -- Techmeme's own permalink for the story
- `storyDate`, `storyTimeText` -- as Techmeme itself labels the story
- `techmemeTwitterUrl` / `techmemeMastodonUrl` / `techmemeThreadsUrl` /
  `techmemeBlueskyUrl` -- Techmeme's own social posts about the story

### Coverage: current river, not a historical archive

Techmeme's `/river` page is a rolling snapshot -- at any given time it holds
roughly the trailing several days of stories (~100-160 on a normal day).
There is no working way to ask for an older window over plain HTTP: the
`day`/`date`/`ts` query parameters are silently ignored by upstream (proven
during recon: identical response regardless of value), and the dated
archive pages that do exist (`techmeme.com/YYMMDD/`) sit behind Cloudflare
on every TLS profile tested. This actor does not offer a date-range input
because it could not honestly honor one -- run it on a schedule (e.g. daily)
if you want an accumulating history; each run's `storyDate`/`techmemePml`
make de-duplication straightforward downstream.

### Filtering

`keywords` is applied **client-side**, after the fetch (case-insensitive
substring match against headline/source/author, OR-combined). Techmeme
exposes no server-side search or filter on this page, so this is this
actor's own post-filter, not something upstream evaluates -- documented here
so it isn't mistaken for a real query parameter.

### No WAF, no auth

`/river` answered clean on every TLS profile tested (chrome124, firefox133,
safari17\_0, chrome99\_android), cold, no warmup needed. robots.txt disallows
only a handful of tracking/redirect paths (`/r2/`, `/goto/`, `/search/`,
etc.) that this actor never touches -- see CRAWLING\_METHOD.md.

### Known limits

- Sponsor posts and "Featured Podcasts" are excluded -- they use unrelated
  markup routed through `/r2/`, which robots.txt disallows.
- No per-story "related coverage" cluster (Techmeme's own site groups a
  story with the other outlets covering it on the story's own permalink
  page) -- this actor reads the /river list view only, one row per listed
  citation, not a second fetch per story.

# Actor input Schema

## `keywords` (type: `array`):

Optional. Keep only stories whose headline, source publication or author contains one of these words/phrases (case-insensitive, OR-combined). Applied AFTER fetching -- Techmeme's /river page has no server-side search, so this narrows locally rather than pretending upstream filters it. Leave empty to keep every story on the current river.

## `maxItems` (type: `integer`):

Cap on returned STORY rows after the keyword filter above. Set to 0 for unlimited -- returns every story currently on the river (typically ~100-160, spanning the trailing several days; see README for why this isn't a deeper historical crawl).

## `proxyConfiguration` (type: `object`):

No bot-mitigation gate was observed anywhere in recon (4 TLS profiles clean, cold, on /river). Residential is still this portfolio's standard cloud default.

## Actor input object example

```json
{
  "keywords": [],
  "maxItems": 0,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# 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("scrapyx/techmeme-tech-news-scraper").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("scrapyx/techmeme-tech-news-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).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 scrapyx/techmeme-tech-news-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/techmeme-tech-news-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/qUznM0JGz7bdohJ5G/builds/3cbH5wmJvn9IsFj52/openapi.json