How to Use FDA device 510(k) decisions in Devin
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.
Prompts to try with FDA device 510(k) decisions in Devin
Copy an example into Devin, or ask in your own words.
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 Devin
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add a custom MCP
Open Customize › MCPs. Click + and choose New MCP. Fill in:
- Sign in to Spiral and approve
In Customize › MCPs, open Spiral and choose Connect. Spiral opens: sign in, pick the organization and click Authorize. No API key.
- Check it
On Spiral's configuration page, click Test tools. Devin lists Spiral's tools.
Use the Spiral skill
- Send Devin this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- 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
- Create an API key
In the console, under API keys.
- Run FDA device 510(k) decisions
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/device_clearances", "input": { "skip": 0 } }'
Then paste one of the prompts above: Devin finds FDA device 510(k) decisions on Spiral, shows the price and runs it.
FDA device 510(k) decisions providers and prices
Spiral runs FDA device 510(k) decisions through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Devin for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Skip | 0 to 25000 | 0 | skip |
| Limit | 1 to 10 | 5 | limit |
Every API field of FDA · Device clearances is on its tool page: open its card above.
What can you do with FDA device 510(k) decisions in Devin?
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.
More on FDA device 510(k) decisions and Devin
Overview
FDA device 510(k) decisions in other agents
Questions about FDA device 510(k) decisions in Devin
Can Devin use FDA device 510(k) decisions?
Yes. Add Spiral to Devin as an MCP server, and Devin can find and run FDA device 510(k) decisions like any built-in tool.
How much does FDA device 510(k) decisions cost in Devin?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Devin plan is separate.
Do I need an Alexandria account to use FDA device 510(k) decisions in Devin?
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 Devin?
About two minutes: add a custom MCP, then sign in to Spiral and approve, then check it.
Does Devin wait while FDA device 510(k) decisions runs?
FDA device 510(k) decisions runs in the background. Devin 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.
Start using FDA device 510(k) decisions in Devin
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Devin:
set up https://spiral.ai/SKILL.md


