# BSEE Safety Alert Metadata (`vixendata/bsee-safety-alert-metadata`) Actor

Official offshore safety alert numbers, dates, categories and source-linked PDF attachments without document downloads.

- **URL**: https://apify.com/vixendata/bsee-safety-alert-metadata.md
- **Developed by:** [Vixendata](https://apify.com/vixendata) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 source-linked publication/news/catalogue records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## BSEE Safety Alert Metadata

Private, read-only Actor for official BSEE offshore safety alert metadata. Returns alert number, title, issued/publication date, category and PDF links. Downloads no PDFs, images or incident narratives and never visits third-party sites.

### Run and input

`pip install -r requirements.txt`, then `python main.py`. Offline tests: `python -m unittest discover -s tests -v`. Uses the real Apify SDK, INPUT/default dataset/RUN_REPORT. Filters: sinceDate is inclusive issued date YYYY-MM-DD; categories match exact case-insensitive values; keywords match title substrings; alertNumbers exact string values. Empty filters include all. Default 10 alerts, 1 page; hard caps 50 alerts, 5 source-linked pages. Source order preserved. First listing: https://www.bsee.gov/guidance-and-regulations/guidance/safety-alerts-program?page=0 . Not a complete archive.

### Safety and output

Read-only urllib standard environment transport, no proxies, cookies, credentials, browser, redirects, retries, or challenge bypass. Live robots required, 2-second minimum or longer crawl delay, 25-second request timeout, 300-second request-launch/post-response budget (slow active reads may overrun until the post-read check), 56 total requests, 2 MB per response and 30 MB overall. Only official source-discovered alert detail URLs, including legacy top-level slugs. Exact listing path and bounded page query. Missing date fields remain null with diagnostics. Source document labels are preserved even where the agency uses MMA branding. PDF links restricted to official files paths but not fetched. Stable ID uses alert number; contentHash excludes observation time. Check current official documents; these metadata are not operational safety advice.

### Rights, demand, gap

BSEE expressly permits distribution/copying of public website information with attribution: https://www.bsee.gov/bsee.gov/privacy-disclaimer . Records attribute BSEE; no endorsement implied. No third-party document content collected.
IMCA distributes BSEE Alert 516: https://www.imca-int.com/resources/safety/safety-flashes/1326-bsee-compressed-gas-cylinder-hazards/ . IADC promotes BSEE alert notifications: https://iadc.org/drillbits/bsee-announces-release-of-bseesafe-program/ . These show professional consumption, not verified buyers or revenue.
2026-10-06 Store searches BSEE, bsee.gov and Bureau Safety Environmental Enforcement found no dedicated offshore alert Actor. Generic crawlers remain substitutes. This is bounded search evidence, not global absence proof.

### Verification

Portable official 2026-10-06 source fixtures included, 50 listing records. Actual local Apify SDK live run evidence in verification; not an Apify-hosted production run. No Console changes or Store publication.

# Actor input Schema

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

Maximum matching alerts emitted.

## `maxPages` (type: `integer`):

Maximum first listing pages visited, following eligible source next links.

## `sinceDate` (type: `string`):

Inclusive issued-date YYYY-MM-DD filter; empty disables. Missing dates do not match an enabled filter.

## `categories` (type: `array`):

Case-insensitive exact category match; any matches. Empty includes all; up to 20 values.

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

Case-insensitive title substrings; any matches. Empty includes all; up to 20 values.

## `alertNumbers` (type: `array`):

Exact alert numbers as strings; any matches. Empty includes all; up to 20 values.

## Actor input object example

```json
{
  "maxItems": 10,
  "maxPages": 1,
  "sinceDate": "",
  "categories": [],
  "keywords": [],
  "alertNumbers": []
}
```

# Actor output Schema

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

No description

# 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("vixendata/bsee-safety-alert-metadata").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("vixendata/bsee-safety-alert-metadata").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 vixendata/bsee-safety-alert-metadata --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vixendata/bsee-safety-alert-metadata"
        }
    }
}
```

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/HKwcqawFZQ3CitLJI/builds/pKXzIAxNox0KpBDAw/openapi.json