Core Signals//v1/layoffs

WARNNode
Corporate Restructuring & Layoff Signals API

Machine-readable state WARN Act notices detailing company downsizings.

Built forHR-Tech AI models, restructuring lawyers, proactive staffing automation.

GET /v1/layoffs

[
  {
    "id": "warn-0000",
    "source": "example",
    "source_id": "warn-0000",
    "type": "warn",
    "discovered_at": "1970-01-01T00:00:00.000Z",
    "payload": {
      "employees": 1426,
      "date": "1969-11-02"
    }
  },
  {
    "id": "warn-0001",
    "source": "example",
    "source_id": "warn-0001",
    "type": "warn",
    "discovered_at": "1969-12-31T18:00:00.000Z",
    "payload": {
      "employees": 1221,
      "date": "1969-11-24"
    }
  },
  {
    "id": "warn-0002",
    "source": "example",
    "source_id": "warn-0002",
    "type": "warn",
    "discovered_at": "1969-12-31T22:00:00.000Z",
    "payload": {
      "employees": 55,
      "date": "1969-11-28"
    }
  }
]

Schema fields

titleCompany Name
payload.employeesImpacted · number
payload.dateEffective Date · date

Realtime

Webhooks

HMAC signed

Starts at

$49/mo

Curator tier · cancel anytime

Drop-in for any stack

Wire WARNNode into your agent — one snippet, seven frameworks.

One-line install

curl https://www.aiagentnode.io/api/v1/nodes/warn/records?limit=10 \
  -H "Authorization: Bearer $AIAGENTNODE_KEY"

What teams build

WARNNode powers…

Autonomous agents

Pipe WARNNode into your LangChain / Vercel AI / Lovable agent for real-time decisions.

RAG enrichment

Schema-stable JSON drops straight into your vector store with predictable embeddings and no parsing.

Internal dashboards

Webhook into Slack, Notion, Linear, or your own ops console. Same auth across every node.

How WARNNode works

Sourced from primary registries. Normalized for agents.

Primary data sources

All 50 US state WARN portals
California EDD
New York DOL
Texas WorkforceCommission
Federal contractor disclosures

We ingest from the upstream of record — never from secondary scrapers — so every warnnode record in your agent traces back to an authoritative publisher.

Methodology

Continuous polling of upstream sources with adaptive backoff
Deduplication via stable source_id + content fingerprint
LLM-friendly normalization into a single JSON envelope
Schema versioning so existing agents never break
HMAC-signed webhooks for guaranteed-delivery push

Update cadence

Hourly (state portals republish in batches)

End-to-end latency

Under 60 seconds from upstream publication to API

Coverage

All 50 US states + DC + territories

History

Full archive back to 2018

WARNNode vs DIY scraping

Stop maintaining brittle scrapers. Ship the agent.

Most teams spend a quarter rebuilding what WARNNode ships in a single API key. Here's the honest tradeoff.

Dimension	WARNNode	DIY scraper
Setup time	One API key, one endpoint	Weeks of scraper engineering
Schema stability	Versioned JSON contract	Breaks every upstream redesign
Freshness	<60s from publication	Cron job, often hours stale
Delivery	Polling + HMAC webhooks	Build your own queue
LLM readiness	Token-optimized payload	Manual cleaning per record
Compliance	Source TOS handled upstream	Your legal exposure

Integrate in 3 steps

From signup to first WARNNode record in under 5 minutes.

1. Generate an API key
Pick a tier, complete checkout, and a Bearer token is minted instantly — no email handoff.
2. Call /v1/layoffs
Send an authenticated GET to receive a paginated JSON envelope. Cursor in, more records out.
3. Subscribe to webhooks
Register an HTTPS endpoint to receive HMAC-signed pushes within seconds of upstream publication.

Frequently asked

WARNNode questions, answered.

How fresh is the WARNNode API data?+

New records appear in /v1/layoffs within ~60 seconds of being published upstream. The full dataset is polled every 5 minutes and pushed to webhook subscribers in the same window.

What format does WARNNode return?+

Every endpoint returns a stable JSON envelope: { id, source, source_id, type, discovered_at, payload }. The payload mirrors the source's natural shape, normalized and token-optimized for direct ingestion into LLMs, vector stores, and RAG pipelines.

Is WARNNode suitable for AI agents and RAG pipelines?+

Yes — that is the primary design goal. Field keys are stable, units are normalized, free text is cleaned, and total token weight per record is minimized so you can drop responses directly into LangChain, Vercel AI SDK, OpenAI tools, MCP, n8n, or Lovable agents without preprocessing.

How is authentication handled?+

A single API key (Bearer token) works across every node. Webhook payloads are HMAC-SHA256 signed with your tenant secret so you can verify provenance before acting on a record.

Can I get historical WARNNode data for backtesting?+

Pro tiers include a rolling 24-month backfill via the same endpoint with ?since=<ISO date>. Scale and Agency tiers can request full historical exports as compressed JSONL.

What is the rate limit?+

Curator: 60 req/min. Pro: 600 req/min. Scale: 6,000 req/min. Agency: 60,000 req/min. Enterprise: negotiated. All tiers support paginated cursors so you never need to spike for a backfill.

Why not just scrape warnnode sources directly?+

Upstream sources change formats, throttle aggressively, and break silently. We absorb that fragility, version the schema, sign deliveries, and republish a single contract so your agent stays online when the source moves.

HMAC-signed webhooks

SHA-256 signatures on every push.

99.95% uptime SLA

Status + history at /status.

Versioned schema

No silent breaking changes, ever.

One auth across nodes

One key, every endpoint.

Related nodes