Agent Access

Agents are welcome here

TechSnif aggregates tech stories into rich clusters: every story comes with the original sources, related coverage, X posts, LinkedIn commentary, Bluesky threads, forum discussions, and more. All of that data is structured and available for agents to pull through open interfaces, or pushed to you over the live stream and webhooks. No auth, no paywall.

What agents can access

Story clusters with full context

Each story includes the lead article, secondary sources, sub-stories, and "More" links, structured as machine-readable data.

Social commentary

X posts, LinkedIn takes, Bluesky threads, Reddit/forum discussions, all linked and attributed per story cluster.

TechSnif articles

Where available, clusters include linked TechSnif coverage alongside the original source material.

Events and metadata

Upcoming tech events, publisher info, timestamps, headline tiers, and ranking data across the full feed.

Choose your interface

Curious what agents are pulling right now? The stats page shows live stream connections plus request and download counts by client.

Webhooks

Prefer push over polling? Register an https endpoint and TechSnif POSTs story.new and story.updated events to it after each pipeline run. Optional topics and tier filters control what you receive.

curl -X POST https://techsnif.com/api/webhooks \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://example.com/hooks/techsnif", "topics": ["ai"], "tier": 2 }'

Registration verifies you control the endpoint: TechSnif POSTs { "type": "webhook.verify", "challenge": "<uuid>" } to your URL, and your endpoint must respond with a 2xx status and include the challenge string in its response body. The 201 response contains your signing secret, shown exactly once.

Every delivery is signed. The X-TechSnif-Signature header is sha256= followed by the hex HMAC-SHA256 of the raw request body, computed with your secret. Verify by recomputing HMAC-SHA256(secret, rawBody) and comparing hex digests. The delivery payload looks like this:

{
  "events": [
    {
      "type": "story.new",
      "id": "2026-08-18T19:30:00.000Z/example-story",
      "at": "2026-08-18T19:30:00.000Z",
      "story": {
        "slug": "example-story",
        "headline": "Example headline",
        "tier": 3,
        "rank": 1,
        "leadUrl": "https://publisher.example/article",
        "sourcePublisher": "Example Publisher",
        "url": "https://techsnif.com/story/example-story",
        "topics": ["ai"]
      }
    }
  ]
}

Unregister with DELETE /api/webhooks and body { url, secret }. Endpoints that fail 10 deliveries in a row are disabled automatically.

Common questions

What data can agents pull from TechSnif?

Agents can retrieve full story clusters including the lead article, related source links, social commentary from X, LinkedIn, Bluesky, and forums, plus linked TechSnif articles, ranking timelines, trending data, tracked entities (companies, people, products), and coverage leaderboards. All of it is structured and machine-readable.

How can an AI agent access TechSnif?

Through the MCP server for tool calling in chat clients (hosted at mcp.techsnif.com or local via npx), the CLI for terminal workflows, the public JSON API for direct HTTP requests (keyword and semantic search included), the live SSE and WebSocket stream at /api/stream for push updates, signed webhooks for deliveries to your own endpoint, or the RSS feed for simple ingestion.

Does TechSnif require API keys or login for agents?

No. All agent surfaces are intentionally open: no accounts, no paywalls, no authentication required.

Which agent tools work well with TechSnif?

TechSnif works with Claude Desktop, Cursor, Windsurf, Gemini CLI, Codex CLI, OpenClaw skills, custom scripts, and any workflow that speaks HTTP, SSE, WebSocket, RSS, MCP, or CLI.

Set up MCP

Connect TechSnif to your chat client in minutes.

Install the CLI

Query stories from your terminal with structured output.