[Integrations](https://spiral.ai/integrations) › [Muse Code](https://spiral.ai/integrations/muse-code) › [FDA device 510(k) decisions](https://spiral.ai/integrations/muse-code/fda-device-510-k-decisions)

# How to Use FDA device 510(k) decisions in Muse Code

Returns device names, applicants, and decision records from FDA's 510(k) database. Use it to research substantial equivalence decisions and dates while preserving the specific decision recorded.

|  |  |
| --- | --- |
| Model | FDA device 510(k) decisions |
| 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 device 510(k) decisions in Muse Code

- Use FDA device 510(k) decisions to find Dexcom submissions and build a table of device names, applicants, decision descriptions, and decision dates.
- Use FDA device 510(k) decisions to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from FDA device 510(k) decisions and tell me what changed since last week.
- Check FDA device 510(k) decisions and summarize what you find in three bullet points.
- Pull the newest data from FDA device 510(k) decisions and give me the result as a table.

## How to set up FDA device 510(k) decisions in Muse Code

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

### Use Spiral's MCP server

1. **Install Muse Code**

```bash
curl -fsSL https://dev.meta.ai/install.sh | bash
```

2. **Ask Muse to add the server**: Start `muse` and ask:

```text
Add the Spiral MCP server at https://api.spiral.ai/mcp
```

3. **Sign in**: In your terminal, run:

```bash
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.

```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 device 510(k) decisions**: 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/device_clearances",
    "input": {
      "skip": 0
    }
  }'
```

Then paste one of the prompts above: Muse Code finds FDA device 510(k) decisions on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/muse-code

## FDA device 510(k) decisions tools and prices

- [FDA · Device clearances](https://spiral.ai/tools/alexandria/fda-gov/records/device_clearances) (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 device 510(k) decisions 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.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Muse Code guides](https://spiral.ai/integrations/muse-code)

## FDA device 510(k) decisions in other agents

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

## More Muse Code guides

- [FDA complete response letter search](https://spiral.ai/integrations/muse-code/fda-complete-response-letter-search)
- [FDA device PMA approvals](https://spiral.ai/integrations/muse-code/fda-device-pma-approvals)
- [FDA complete response letter details](https://spiral.ai/integrations/muse-code/fda-complete-response-letter-details)
- [FDA device UDI records](https://spiral.ai/integrations/muse-code/fda-device-udi-records)
- [FDA cell and gene therapy approvals](https://spiral.ai/integrations/muse-code/fda-cell-and-gene-therapy-approvals)
- [FDA drug adverse event reports](https://spiral.ai/integrations/muse-code/fda-drug-adverse-event-reports)

## Questions about FDA device 510(k) decisions in Muse Code

**Can Muse Code use FDA device 510(k) decisions?**

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run FDA device 510(k) decisions like any built-in tool.

**How much does FDA device 510(k) decisions 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 device 510(k) decisions in Muse Code?**

No. Spiral runs FDA device 510(k) decisions 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 device 510(k) decisions 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 device 510(k) decisions runs?**

FDA device 510(k) decisions 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.

