[Integrations](https://spiral.ai/integrations) › [Codex](https://spiral.ai/integrations/codex) › [GDACS disaster event details](https://spiral.ai/integrations/codex/gdacs-disaster-event-details)

# How to Use GDACS disaster event details in Codex

Returns one disaster event with its episodes and optional footprint geometry. Use it to inspect an alert's development or map the affected area after finding the event.

|  |  |
| --- | --- |
| Model | GDACS disaster event details |
| Available through | Alexandria |
| Category | Public Records |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with GDACS disaster event details in Codex

- Use GDACS disaster event details for the tropical cyclone event selected in our dashboard and add its available episodes and footprint geometry to the detail view.
- Use GDACS disaster event details to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from GDACS disaster event details and tell me what changed since last week.
- Check GDACS disaster event details and summarize what you find in three bullet points.
- Pull the newest data from GDACS disaster event details and give me the result as a table.

## How to set up GDACS disaster event details in Codex

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Add the hosted server**

```bash
codex mcp add spiral --url https://api.spiral.ai/mcp
```

2. **Sign in**: Codex opens the browser: sign in to Spiral and click Authorize. No API key. `codex mcp list` then shows Spiral.

```bash
codex mcp login spiral
```

### Use the Spiral skill

1. **Send Codex this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run GDACS disaster event details**: One request; the result comes back by polling or a webhook.

```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_get",
    "input": {
      "eventid": 1,
      "eventtype": "EQ"
    }
  }'
```

Then paste one of the prompts above: Codex finds GDACS disaster event details on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/codex

## GDACS disaster event details tools and prices

- [GDACS global multi-hazard alerts · Records get](https://spiral.ai/tools/alexandria/gdacs-org/disaster-alerts/records_get) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| episodeid | 0 to … | — | Episode to read; default: the event's current episode. |
| polygon_types |  | — | polygontype filter for getgeometry, e.g. ["Green","Orange","Red"], ["Cones"], ["Line"]. Default: every feature. |
| include_geometry |  | — | Also fetch polygons/getgeometry for the episode. Default false. |

## What can you do with GDACS disaster event details in Codex?

Build a disaster event dashboard that shows GDACS assessments and available footprints alongside public infrastructure. Your coding agent can populate a historical collection, apply revisions, and add event detail views to the project.

### Maintain a disaster monitoring dashboard

Check catalogue status, collect a baseline archive, search the countries being monitored, inspect selected events, and apply subsequent changes to keep the dashboard current.

### Build a reviewed annual disaster archive

Use annual status information to plan collection, gather the year's events, search for review samples, inspect their details, and incorporate later revisions before publishing the analysis.

### Prepare recurring country briefings

Maintain a dated event collection, check source status, find relevant country alerts, examine the events behind the briefing, and update the draft when GDACS revises them.

### Review exposure around public infrastructure

Build and refresh a disaster event collection, use catalogue status to check collection scope, search relevant countries, and inspect available event footprints alongside ports, airports, or other public infrastructure.

### Investigate a cyclone's development

Find a cyclone during a defined period, then inspect its episodes and available footprints to describe how GDACS assessed the event as it developed.

### Find revised alerts for an editorial review

Retrieve recently modified disaster records and inspect the events behind them so an editor can reassess an earlier report before making corrections.

### Assemble disaster mapping examples

Search for earthquakes or cyclones in a selected country and retrieve available event geometry for maps that distinguish modeled impact areas from confirmed damage.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Codex guides](https://spiral.ai/integrations/codex)

## GDACS disaster event details in other agents

- [Amp](https://spiral.ai/integrations/amp/gdacs-disaster-event-details)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/gdacs-disaster-event-details)
- [Claude](https://spiral.ai/integrations/claude-desktop/gdacs-disaster-event-details)
- [Claude Code](https://spiral.ai/integrations/claude-code/gdacs-disaster-event-details)
- [Cline](https://spiral.ai/integrations/cline/gdacs-disaster-event-details)
- [Cursor](https://spiral.ai/integrations/cursor/gdacs-disaster-event-details)
- [Devin](https://spiral.ai/integrations/devin/gdacs-disaster-event-details)
- [dots](https://spiral.ai/integrations/dots/gdacs-disaster-event-details)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/gdacs-disaster-event-details)
- [Gemini](https://spiral.ai/integrations/gemini/gdacs-disaster-event-details)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/gdacs-disaster-event-details)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/gdacs-disaster-event-details)
- [goose](https://spiral.ai/integrations/goose/gdacs-disaster-event-details)
- [Grok](https://spiral.ai/integrations/grok/gdacs-disaster-event-details)
- [Grok Build](https://spiral.ai/integrations/grok-build/gdacs-disaster-event-details)
- [Hermes](https://spiral.ai/integrations/hermes/gdacs-disaster-event-details)
- [Instinct](https://spiral.ai/integrations/instinct/gdacs-disaster-event-details)
- [Manus](https://spiral.ai/integrations/manus/gdacs-disaster-event-details)
- [Muse](https://spiral.ai/integrations/muse/gdacs-disaster-event-details)
- [Muse Code](https://spiral.ai/integrations/muse-code/gdacs-disaster-event-details)
- [n8n](https://spiral.ai/integrations/n8n/gdacs-disaster-event-details)
- [Notion](https://spiral.ai/integrations/notion/gdacs-disaster-event-details)
- [OpenClaw](https://spiral.ai/integrations/openclaw/gdacs-disaster-event-details)
- [opencode](https://spiral.ai/integrations/opencode/gdacs-disaster-event-details)
- [Perplexity](https://spiral.ai/integrations/perplexity/gdacs-disaster-event-details)
- [Raycast](https://spiral.ai/integrations/raycast/gdacs-disaster-event-details)
- [VS Code](https://spiral.ai/integrations/vscode/gdacs-disaster-event-details)
- [Windsurf](https://spiral.ai/integrations/windsurf/gdacs-disaster-event-details)
- [Zapier](https://spiral.ai/integrations/zapier/gdacs-disaster-event-details)

## More Codex guides

- [GDACS disaster event archive](https://spiral.ai/integrations/codex/gdacs-disaster-event-archive)
- [GOV.UK government organizations](https://spiral.ai/integrations/codex/gov-uk-government-organizations)
- [GDACS disaster catalogue status](https://spiral.ai/integrations/codex/gdacs-disaster-catalogue-status)
- [GOV.UK manual contents and updates](https://spiral.ai/integrations/codex/gov-uk-manual-contents-and-updates)
- [GDACS disaster alert search](https://spiral.ai/integrations/codex/gdacs-disaster-alert-search)
- [GOV.UK page content](https://spiral.ai/integrations/codex/gov-uk-page-content)

## Questions about GDACS disaster event details in Codex

**Can Codex use GDACS disaster event details?**

Yes. Add Spiral to Codex as an MCP server, and Codex can find and run GDACS disaster event details like any built-in tool.

**How much does GDACS disaster event details cost in Codex?**

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

**Do I need an Alexandria account to use GDACS disaster event details in Codex?**

No. Spiral runs GDACS disaster event details on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up GDACS disaster event details in Codex?**

About two minutes: add the hosted server, then sign in.

**Does Codex wait while GDACS disaster event details runs?**

GDACS disaster event details runs in the background. Codex starts the run, checks on it and gives you the json when it's ready.

**Does GDACS provide confirmed disaster damage totals?**

GDACS calculates potential impact using hazard characteristics, population exposure, and vulnerability. Its terms require confirmation before notifications or automatic impact estimates are used for decisions.

**How fresh is GDACS information?**

GDACS describes its notifications as near-real-time, but explicitly gives no guarantee of completeness or timeliness. A recent retrieval does not establish that every relevant event or revision is already present.

**What does an active event mean on the GDACS homepage?**

The MHEWS homepage requires an update within the last four days, except for droughts, where the window is ten days. That label reflects recent monitoring activity rather than proof that a hazard has ended.

**Can a GDACS search return more than 100 events?**

The upstream search returns the first 100 results and supports pagination. A single result page should not be treated as the full historical collection.

**Does GDACS cover tropical cyclones outside the Atlantic?**

Yes. GDACS documents worldwide tropical cyclone coverage using NOAA and Joint Typhoon Warning Center bulletins.

