[Integrations](https://spiral.ai/integrations) › [Codex](https://spiral.ai/integrations/codex) › [Benzinga withdrawn calendar records](https://spiral.ai/integrations/codex/benzinga-withdrawn-calendar-records)

# How to Use Benzinga withdrawn calendar records in Codex

Returns identifiers, event types, and update timestamps for removed or canceled calendar records. Use it to reconcile saved ratings and deal calendars when Benzinga withdraws an earlier entry.

|  |  |
| --- | --- |
| Model | Benzinga withdrawn calendar records |
| Available through | Alexandria |
| Category | Finance |
| Price | $0.013 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with Benzinga withdrawn calendar records in Codex

- Use Benzinga withdrawn calendar records to reconcile the saved analyst rating events in this project's AAPL watchlist database and report which stored identifiers match.
- Use Benzinga withdrawn calendar records to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from Benzinga withdrawn calendar records and tell me what changed since last week.
- Check Benzinga withdrawn calendar records and summarize what you find in three bullet points.
- Pull the newest data from Benzinga withdrawn calendar records and give me the result as a table.

## How to set up Benzinga withdrawn calendar records 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 Benzinga withdrawn calendar records**: 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": "benzinga/calendar/removed",
    "input": {
      "page": 0
    }
  }'
```

Then paste one of the prompts above: Codex finds Benzinga withdrawn calendar records on Spiral, shows the price and runs it.

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

## Benzinga withdrawn calendar records tools and prices

- [Benzinga · Removed calendar events](https://spiral.ai/tools/alexandria/benzinga/calendar/removed) (Alexandria): $0.013 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| page | … to 100000 | 0 | Page offset, limited to 0-100000. Set this when walking a long backlog of removals. |
| type | ratings, ma | — | Which calendar to read removals for: ratings for calendar/ratings rows, ma for calendar/mergers-acquisitions rows. Always set it: left unset the feed returns removals from every Benzinga calendar, most of them for calendars not published here (probed 2026-09-21, the unfiltered first page was dividends). |
| updated |  | — | Unix timestamp (UTC); only records updated at or after this are returned. Set this to the time of your last sync so you get just the newly withdrawn events. |
| pageSize | … to 1000 | 100 | Number of removal records to return, limit 1000. |

## What can you do with Benzinga withdrawn calendar records in Codex?

Build a company research view with Benzinga recommendations, research-source identities, and acquisition records. A coding agent can turn the returned records into tables, comparisons, and reconciliation logic in your project.

### Review analyst responses around an acquisition

Place a deal's status and dates beside rating changes and consensus for the companies involved. Identify the research sources and reconcile withdrawn calendar entries before assembling the review.

### Produce a weekly portfolio research digest

For a stock watchlist, summarize consensus, recommendation changes, and acquisition activity. Add analyst performance context and firm names, and remove withdrawn events from the saved calendar used for the digest.

### Build an internal research dashboard

Give each watched company a consensus summary, a rating-change timeline, and a deal calendar. Link recommendations to analyst and firm records, and reconcile withdrawals so obsolete events disappear.

### Maintain a company research archive

Save consensus snapshots alongside individual ratings and deal records. Retain analyst and firm identifiers for attribution, and use withdrawal records to correct the archive when calendar entries are removed.

### Maintain an acquisition closing calendar

Organize transactions by expected and completed dates, with deal status and payment details attached. Reconcile withdrawn records against saved transactions.

## Overview

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

## Benzinga withdrawn calendar records in other agents

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

## More Codex guides

- [Benzinga stock move explanations](https://spiral.ai/integrations/codex/benzinga-stock-move-explanations)
- [CFTC Financial futures report, futures and options combined](https://spiral.ai/integrations/codex/cftc-financial-futures-report-futures-and-options-combined)
- [Benzinga stock analyst rating changes](https://spiral.ai/integrations/codex/benzinga-stock-analyst-rating-changes)
- [CFTC Financial futures report, futures only](https://spiral.ai/integrations/codex/cftc-financial-futures-report-futures-only)
- [Benzinga removed news](https://spiral.ai/integrations/codex/benzinga-removed-news)
- [CFTC commodity futures and options positions](https://spiral.ai/integrations/codex/cftc-commodity-futures-and-options-positions)

## Questions about Benzinga withdrawn calendar records in Codex

**Can Codex use Benzinga withdrawn calendar records?**

Yes. Add Spiral to Codex as an MCP server, and Codex can find and run Benzinga withdrawn calendar records like any built-in tool.

**How much does Benzinga withdrawn calendar records cost in Codex?**

$0.013 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 Benzinga withdrawn calendar records in Codex?**

No. Spiral runs Benzinga withdrawn calendar records on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up Benzinga withdrawn calendar records in Codex?**

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

**Does Codex wait while Benzinga withdrawn calendar records runs?**

Benzinga withdrawn calendar records runs in the background. Codex starts the run, checks on it and gives you the json when it's ready.

**Which markets does Benzinga cover for ratings and deals?**

Benzinga lists US equities as the coverage for both its analyst ratings and merger and acquisition datasets. These product descriptions do not establish worldwide coverage.

**Where does Benzinga get analyst recommendations?**

Benzinga says its news desk has direct partnerships with major sell-side banks. Its guidebook reports capturing 125 to 150 analyst actions per day.

**How quickly are analyst rating changes published?**

Benzinga says rating changes made during trading hours are posted intraday. That describes publication frequency, rather than a guaranteed delivery delay in seconds.

**How far back does Benzinga's historical coverage go?**

Benzinga's product pages list analyst ratings history from 2013 and merger and acquisition history from 2019. Those are dataset descriptions, rather than a promise that every company has records throughout that period.

**Can Benzinga withdraw a previously published calendar entry?**

Yes. Benzinga provides a separate feed for removed or canceled calendar events, including the affected record's identifier and event type.

