# GDACS global multi-hazard alerts · Records changes

Search public records with GDACS global multi-hazard alerts · Records changes from Alexandria through one Spiral API key. Reconcile a live window or pull deltas since the last sweep: 'events modified since 2026-10-18T03:00'. It runs in the background and returns structured JSON. Pay as you go, with no subscription.

- Provider: Alexandria
- Category: Public Records
- Runs: In the background
- Returns: json
- Tool id: `alexandria` / `gdacs-org/disaster-alerts/records_changes`
- Page: https://spiral.ai/tools/alexandria/gdacs-org/disaster-alerts/records_changes

## Pricing

$0.00873 per call.

## Limits

- Longest queue wait: 1 hour
- Run deadline: 5 minutes
- Longest run, end to end: 225 minutes
- Largest inline input: 1 MB
- Largest input file: 2 GB
- Largest output: 5 GB

## Input

| Field | Kind | Allowed | Default | Description |
| --- | --- | --- | --- | --- |
| `since` | text |  | — | UTC timestamp, YYYY-MM-DDTHH:MM:SS (Z optional) or a date. Required unless cursor or since_hours_ago is given. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}(T[0-9]{2}:[0-9]{2}(:[0-9]{2}(\.[0-9]+)?)?)?Z?$. |
| `cursor` | text |  | — | next_cursor from the previous page. |
| `eventlist` | list |  | — | Hazard types to include. Default: all six (EQ earthquake, TC tropical cyclone, FL flood, VO volcano, DR drought, WF wildfire). |
| `since_hours_ago` | number | 1 to 8784 | — | Relative alternative to since: changes in the last N hours (computed from the runner clock, UTC). Not with since. |

## Example

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "gdacs-org/disaster-alerts/records_changes",
    "input": {
      "since": "<since>"
    }
  }'
```

Try it in the Playground: https://spiral.ai/start?provider=alexandria&model=gdacs-org%2Fdisaster-alerts%2Frecords_changes

## Common questions

### GDACS global multi-hazard alerts · Records changes

**How much does GDACS global multi-hazard alerts · Records changes cost?**

$0.00873 per call. You pay as you go from one Spiral balance, with no subscription, and a failed run is not charged.

**How do I use GDACS global multi-hazard alerts · Records changes through an API?**

Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "gdacs-org/disaster-alerts/records_changes"` and the input fields on this page, using one Spiral API key. It runs in the background: poll the run, or name a webhook to be told when it finishes.

**Do I need an account with Alexandria to use GDACS global multi-hazard alerts · Records changes?**

No. Spiral runs it on its own Alexandria account and charges your Spiral balance.

**Can my AI agent use GDACS global multi-hazard alerts · Records changes?**

Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.

