[Integrations](https://spiral.ai/integrations) › [Codex](https://spiral.ai/integrations/codex) › [FDA complete response letter details](https://spiral.ai/integrations/codex/fda-complete-response-letter-details)

# How to Use FDA complete response letter details in Codex

Returns the published text of an FDA complete response letter, including cited deficiencies and any recommended actions. Use it to examine a specific application decision after finding a letter.

|  |  |
| --- | --- |
| Model | FDA complete response letter details |
| Available through | Alexandria |
| Category | Health |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with FDA complete response letter details in Codex

- Use FDA complete response letter details to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from FDA complete response letter details and tell me what changed since last week.
- Check FDA complete response letter details and summarize what you find in three bullet points.
- Pull the newest data from FDA complete response letter details and give me the result as a table.
- Check FDA complete response letter details every morning and tell me only when something changed.

## How to set up FDA complete response letter 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 FDA complete response letter 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": "fda-gov/records/complete_response_letter",
    "input": {
      "application_number": "<application_number>"
    }
  }'
```

Then paste one of the prompts above: Codex finds FDA complete response letter details on Spiral, shows the price and runs it.

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

## FDA complete response letter details tools and prices

- [FDA · Complete response letter](https://spiral.ai/tools/alexandria/fda-gov/records/complete_response_letter) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| submission |  | — | Only needed when an application has two letters on one day, e.g. Original 1 or Original 2 for BLA761303 on 2024-03-22. |
| letter_date |  | — | Letter date, YYYY-MM-DD; omit for the most recent letter. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |

## What can you do with FDA complete response letter details in Codex?

Build a product research view that puts FDA decisions, submitted product information, and reported safety findings beside their source records. A coding agent can add the returned evidence to your project's tables while preserving application numbers, document links, and decision meanings.

### Company regulatory due diligence

Build an evidence packet for a public drug or device company using its published application decisions, documents, listings, labeling, adverse event reports, and recall findings. Keep each record's regulatory meaning attached to the finding.

### Internal FDA research digest

Prepare a recurring digest of newly available or changed FDA evidence for a company or product watchlist. Separate application decisions, submitted product information, reported reactions, and historical recall findings.

### Regulatory milestone timelines

Reconstruct a drug application's published review history or a device's 510(k) decision history. Put CRL findings beside subsequent application milestones and links to supporting documents.

### Product claim fact-checking

Check public claims about approval, labeling, product identity, reported adverse reactions, or recall findings against the relevant FDA records. Identify the exact passage or decision that supports each statement.

### Publication evidence archive

Assemble the FDA evidence behind a company profile, product explainer, or regulatory investigation. Preserve document links, source identifiers, dates, and the passages used so an editor can check the published account.

### CRL deficiency comparison

Find published letters mentioning manufacturing or clinical deficiencies, then read the relevant passages. Compare FDA's stated concerns and requested actions across applications without estimating unpublished rejection rates.

## Overview

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

## FDA complete response letter details in other agents

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

## More Codex guides

- [FDA cell and gene therapy approvals](https://spiral.ai/integrations/codex/fda-cell-and-gene-therapy-approvals)
- [FDA complete response letter search](https://spiral.ai/integrations/codex/fda-complete-response-letter-search)
- [FDA Purple Book biologic records](https://spiral.ai/integrations/codex/fda-purple-book-biologic-records)
- [FDA device 510(k) decisions](https://spiral.ai/integrations/codex/fda-device-510-k-decisions)
- [FDA Paragraph IV patent certifications](https://spiral.ai/integrations/codex/fda-paragraph-iv-patent-certifications)
- [FDA device PMA approvals](https://spiral.ai/integrations/codex/fda-device-pma-approvals)

## Questions about FDA complete response letter details in Codex

**Can Codex use FDA complete response letter details?**

Yes. Add Spiral to Codex as an MCP server, and Codex can find and run FDA complete response letter details like any built-in tool.

**How much does FDA complete response letter 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 FDA complete response letter details in Codex?**

No. Spiral runs FDA complete response letter 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 FDA complete response letter details in Codex?**

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

**Does Codex wait while FDA complete response letter details runs?**

FDA complete response letter details runs in the background. Codex starts the run, checks on it and gives you the json when it's ready.

**How fresh are FDA records?**

FDA datasets follow different schedules. Application records update on weekdays, labeling updates weekly, 510(k) records update monthly, and FAERS updates quarterly with a possible lag of three months or more.

**How far back does FDA's published history go?**

Coverage depends on the record type: Drugs@FDA includes most products approved since 1939, 510(k) history begins in 1976, and the recall datasets begin in 2004. Supporting drug documents are more widely available for products approved since 1998.

**Does appearing in an FDA database prove a product is approved?**

An NDC number does not establish approval, and submitted labeling may differ from approved labeling. The CRL database also includes unapproved applications, while 510(k) records concern substantial equivalence decisions.

**Are public FDA records complete and independently verified?**

Public CRLs have confidential commercial information and trade secrets removed. NDC information is submitted by labelers, and adverse event reports do not establish that a product caused the reported reaction.

**Can FDA data be reused in a commercial research product?**

Unless otherwise noted, openFDA materials carry a CC0 1.0 dedication that permits commercial reuse. Some third-party material has separate restrictions, so the terms do not grant unrestricted rights to every included work.

