# Legislation Radar — New Laws, Regulations & Bills (`tacps126/legislation-radar`) Actor

New laws in one feed: EU regulations, directives and decisions (EUR-Lex), UK Acts and statutory instruments of all four nations, US public laws and bill texts. Number, title, date, official text and PDF links; AI summaries. From $3 per 1,000 laws.

- **URL**: https://apify.com/tacps126/legislation-radar.md
- **Developed by:** [Tapaswai Ashok Choudhary](https://apify.com/tacps126) (community)
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.40 / 1,000 law or bills

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Legislation Radar — New Laws, Regulations & Bills

New legislation from the **official publishers in one clean feed**: EU regulations, directives and decisions from EUR-Lex, new UK legislation (Acts and statutory instruments of the UK, Scotland, Wales and Northern Ireland) from legislation.gov.uk, US public laws and bill texts from GovInfo, new Australian Acts and legislative instruments from the Federal Register of Legislation, and new Canadian regulations from the Canada Gazette. Filter by keyword, sector and kind; get only what's new; let AI tell you what each law changes and who it affects.

**Built for** compliance and legal teams, public-affairs consultants, law firms, trade associations, regulatory-intelligence products, and AI agents.

### Sources

| Jurisdiction | Publisher | What you get |
|---|---|---|
| 🇪🇺 European Union | **EUR-Lex** (Publications Office) | Regulations, directives and decisions with number, date and English title, official text and PDF |
| 🇬🇧 United Kingdom | **legislation.gov.uk** | New Acts and statutory instruments of the UK, Scottish, Welsh and Northern Ireland legislatures and governments |
| 🇺🇸 United States | **GovInfo** | Public laws (enacted) and bill texts at every stage (introduced, reported, engrossed, enrolled) |
| 🇦🇺 Australia | **Federal Register of Legislation** | New Acts and legislative instruments as made, with number, making date and official text |
| 🇨🇦 Canada | **Canada Gazette, Part II** | New regulations (SOR) and statutory instruments (SI) with number, registration date and text |

### Why this Actor

- **One schema.** `country`, `subdivision` (for Scottish, Welsh, NI law), `kind`, `number`, `title`, `date`, `stage` (bills), `sectors`, `url`, `pdfUrl`.
- **Sector and keyword filters** across all five jurisdictions.
- **Law alerts.** Turn on *Only new laws* and schedule it; send results to Slack, Google Sheets, a webhook or an RSS reader.
- **AI insights (optional).** What the law does, who is affected, and with your profile a relevance score.
- **For AI agents.** Callable as an MCP tool.

### How to use it

```json
{
  "keywords": ["sanctions", "anti-dumping"],
  "countries": ["EU", "GB"],
  "postedWithinDays": 7,
  "onlyNew": true
}
```

### Pricing

**$3 per 1,000 laws** plus a small start fee per run. AI insights, when you turn them on, are $0.01 each plus the model's own cost.

### Good to know

Titles and numbers are as published; the `url` is the official text. Gov Radar covers the news, consultations and guidance around new law; Legislation Radar covers the law itself.

### Need something bigger?

More jurisdictions (India, Brazil, Canadian bills, Australian states), consolidated texts, or a private feed: **contact tacps126@gmail.com**.

# Actor input Schema

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

Whole words matched on the title, e.g. sanctions, data, emissions, tax.

## `sectors` (type: `array`):

Only tenders in these sectors, from their CPV / UNSPSC codes and words in several languages.

## `countries` (type: `array`):

Empty = all.

## `kinds` (type: `array`):

Empty = all.

## `postedWithinDays` (type: `integer`):

Laws dated (adopted, made or published) in this window.

## `excludeKeywords` (type: `array`):

Leave out laws whose title contains any of these (e.g. corrigendum, road traffic).

## `sources` (type: `array`):

Pick specific sources instead of jurisdictions.

## `maxItemsPerSource` (type: `integer`):

Most laws kept from each source.

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

Most laws returned (newest first).

## `aiInsights` (type: `boolean`):

Add an `insight` to each law: what it does or changes in plain words, who is affected, and what to do. With a profile, also a 0-100 relevance score.

## `aiProfile` (type: `string`):

What your organisation does and where, e.g. "Online lender in Ireland and the UK; consumer credit and payments".

## `aiLanguage` (type: `string`):

Insights are written in this language, whatever the source language.

## `maxInsights` (type: `integer`):

Insights are added to the first N laws (newest first).

## `aiProvider` (type: `string`):

Which AI does the analysis. Apify needs no key: the model runs through Apify's OpenRouter proxy and is billed to your Apify account. Any other provider uses your own key and bills you there.

## `aiApiKey` (type: `string`):

Your own key for the provider above (not needed for Apify). Sent only to that provider, never stored.

## `aiModel` (type: `string`):

Model name. Apify: an OpenRouter id like anthropic/claude-sonnet-… or google/gemini-… (default: the newest Claude Haiku listed, a light model since it runs once per result). Anthropic: default claude-opus-5-5. Others: required.

## `aiBaseUrl` (type: `string`):

Only for "Other OpenAI-compatible API", e.g. http://localhost:11434/v1 for Ollama.

## `onlyNew` (type: `boolean`):

Schedule the Actor (daily or weekly) and each run returns only laws and bills earlier runs didn't deliver.

## `monitorName` (type: `string`):

Optional name for the “only new” history, so several monitors can run side by side.

## `delivery` (type: `object`):

Webhook: {"webhookUrl": "https://…", "format": "json" | "slack" | "discord", "onlyWhenResults": true, "includeItems": 10}. Google Sheets: {"spreadsheetId": "<id from the sheet URL>", "sheetName": "Sheet1"} plus the service account key below; share the sheet with the service account's e-mail first. Leave empty to only save results in the dataset.

## `googleServiceAccountJson` (type: `string`):

Only for Google Sheets delivery: paste the service account's JSON key. Stored encrypted; the account sees only sheets you share with it.

## `tenantId` (type: `string`):

Optional label used to keep separate histories for different clients or teams.

## `debug` (type: `boolean`):

Save extra diagnostics with the run (for support requests).

## Actor input object example

```json
{
  "keywords": [
    "artificial intelligence"
  ],
  "postedWithinDays": 7,
  "maxItemsPerSource": 300,
  "maxItems": 500,
  "aiInsights": false,
  "aiLanguage": "English",
  "maxInsights": 25,
  "aiProvider": "apify",
  "onlyNew": false,
  "debug": false
}
```

# Actor output Schema

## `results` (type: `string`):

The produced items (default dataset items).

# 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 = {
    "keywords": [
        "artificial intelligence"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tacps126/legislation-radar").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 = { "keywords": ["artificial intelligence"] }

# Run the Actor and wait for it to finish
run = client.actor("tacps126/legislation-radar").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 '{
  "keywords": [
    "artificial intelligence"
  ]
}' |
apify call tacps126/legislation-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tacps126/legislation-radar"
        }
    }
}
```

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/yxZMVhzKhJKdhCNRG/builds/5KNDVrXrcziHJUcde/openapi.json