[Integrations](https://spiral.ai/integrations) › [Perplexity](https://spiral.ai/integrations/perplexity) › [FDA drug application records](https://spiral.ai/integrations/perplexity/fda-drug-application-records)

# How to Use FDA drug application records in Perplexity

Returns Drugs@FDA application records with products and submission histories. Use it to examine application milestones and submission statuses before opening the supporting approval documents.

|  |  |
| --- | --- |
| Model | FDA drug application records |
| 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 drug application records in Perplexity

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

## How to set up FDA drug application records in Perplexity

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

### Use the Perplexity connector

1. **Add a remote connector**: In Perplexity, open Plugins in the sidebar (or Customize › Connectors if you don't see Plugins yet). Choose Add custom › Add MCP connector, then Remote. Name it Spiral and paste this MCP server URL:

```text
https://api.spiral.ai/mcp
```

2. **Sign in to Spiral and approve**: Select the Spiral card on the Plugins page to start sign-in. Spiral opens: sign in, pick the organization and click Authorize. No API key.

### Use the Spiral skill

1. **Send Perplexity 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 drug application 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": "fda-gov/records/drug_applications",
    "input": {
      "skip": 0
    }
  }'
```

Then paste one of the prompts above: Perplexity finds FDA drug application records on Spiral, shows the price and runs it.

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

## FDA drug application records tools and prices

- [FDA · Drug applications](https://spiral.ai/tools/alexandria/fda-gov/records/drug_applications) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| skip | 0 to 25000 | 0 | skip |
| limit | 1 to 10 | 5 | limit |
| query |  | — | Plain openFDA search expression, e.g. product_description:aspirin or report_date:[20250101 TO 20251231]. Use spaces around AND, OR and TO; do not URL-encode the expression or use + as a space. Literal plus signs are preserved. Mutually exclusive with record_id. Omit both to browse source default order. |
| record_id |  | — | Source identifier returned by this dataset. Exact quoted lookup; mutually exclusive with query. Pattern: ^[A-Za-z0-9-]{1,100}$. |

## What can you do with FDA drug application records in Perplexity?

Produce a cited explanation of what FDA has published about a drug, device, or company. A chat app can turn decision records, letter text, listings, and recall findings into a readable comparison that preserves the distinction between approval evidence and submitted information.

### 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.

### Drug catalog reconciliation

Compare a drug catalog's names, ingredients, dosage forms, routes, and packages with FDA listings. Add application references and labeling evidence without treating a listing as proof of approval.

### 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.

## Overview

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

## FDA drug application records in other agents

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

## More Perplexity guides

- [FDA drug adverse event reports](https://spiral.ai/integrations/perplexity/fda-drug-adverse-event-reports)
- [FDA drug approval documents](https://spiral.ai/integrations/perplexity/fda-drug-approval-documents)
- [FDA device UDI records](https://spiral.ai/integrations/perplexity/fda-device-udi-records)
- [FDA drug labeling](https://spiral.ai/integrations/perplexity/fda-drug-labeling)
- [FDA device PMA approvals](https://spiral.ai/integrations/perplexity/fda-device-pma-approvals)
- [FDA drug recall reports](https://spiral.ai/integrations/perplexity/fda-drug-recall-reports)

## Questions about FDA drug application records in Perplexity

**Can Perplexity use FDA drug application records?**

Yes. Add Spiral to Perplexity as an MCP server, and Perplexity can find and run FDA drug application records like any built-in tool.

**How much does FDA drug application records cost in Perplexity?**

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

**Do I need an Alexandria account to use FDA drug application records in Perplexity?**

No. Spiral runs FDA drug application 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 FDA drug application records in Perplexity?**

About two minutes: add a remote connector, then sign in to Spiral and approve.

**Does Perplexity wait while FDA drug application records runs?**

FDA drug application records runs in the background. Perplexity 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.

