Spiral gives your agent every tool with one account. Browse the tools →

Muse Code · Health

How to Use FDA complete response letter details in Muse Code

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.

Prompts to try with FDA complete response letter details in Muse Code

Copy an example into Muse Code, or ask in your own words.

Use FDA complete response letter details to look this up and give me the result as a table. Save the result in ./assets.

FDA complete response letter detailsMuse Code
Try asking
  • 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 Muse Code

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

Use Spiral's MCP server

  1. Install Muse Code
    curl -fsSL https://dev.meta.ai/install.sh | bash
  2. Ask Muse to add the server

    Start muse and ask:

    Add the Spiral MCP server at https://api.spiral.ai/mcp
  3. Sign in

    In your terminal, run:

    muse mcp login spiral

Use the Spiral skill

  1. Send Muse Code 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.

    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.

    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: Muse Code finds FDA complete response letter details on Spiral, shows the price and runs it.

FDA complete response letter details providers and prices

Spiral runs FDA complete response letter details through Alexandria. Open a card for today's price, with every fee included.

AlexandriaHealth
FDA · Complete response letter
fda-gov/records/complete_response_letter

What can you do with FDA complete response letter details in Muse Code?

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.

Questions about FDA complete response letter details in Muse Code

Can Muse Code use FDA complete response letter details?

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

How much does FDA complete response letter details cost in Muse Code?

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

Do I need an Alexandria account to use FDA complete response letter details in Muse Code?

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 Muse Code?

About two minutes: install Muse Code, then ask Muse to add the server, then sign in.

Does Muse Code wait while FDA complete response letter details runs?

FDA complete response letter details runs in the background. Muse Code 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.

Get started

Start using FDA complete response letter details in Muse Code

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Muse Code:

Set up Muse Code

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options