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

OpenClaw · Health

How to Use FDA device 510(k) decisions in OpenClaw

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 OpenClaw

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

Each month, use FDA device 510(k) decisions to check Dexcom records and summarize newly available decision dates and descriptions.

FDA device 510(k) decisionsOpenClaw
Try asking
  • Every Monday at 9am: use FDA device 510(k) decisions to look this up and give me the result as a table.

  • 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 OpenClaw

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

Use the Spiral skill

  1. Send OpenClaw 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 Spiral's MCP server

  1. Add the server

    On the machine that runs OpenClaw's Gateway:

    openclaw mcp add spiral \
      --url https://api.spiral.ai/mcp \
      --transport streamable-http \
      --auth oauth
  2. Sign in

    In Settings › MCP, select Sign in on the Spiral server, sign in to Spiral and click Authorize. No API key.

    openclaw mcp login spiral
  3. Reload and check

    A running Gateway may keep its old tool list: restart it, or Save & Publish in the Control UI.

    openclaw mcp reload
    openclaw mcp doctor spiral --probe

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 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: OpenClaw 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.

AlexandriaHealth
FDA · Device clearances
fda-gov/records/device_clearances

Settings you can ask for

Ask OpenClaw for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Skip0 to 250000

skip

Limit1 to 105

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 OpenClaw?

Maintain an internal research digest of newly published FDA evidence for a product or company watchlist. A scheduled agent can compare successive results and summarize new documents or revised records while accounting for each dataset's publication lag.

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.

Questions about FDA device 510(k) decisions in OpenClaw

Can OpenClaw use FDA device 510(k) decisions?

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

How much does FDA device 510(k) decisions cost in OpenClaw?

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

Do I need an Alexandria account to use FDA device 510(k) decisions in OpenClaw?

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 OpenClaw?

About two minutes: add the server, then sign in, then reload and check.

Does OpenClaw wait while FDA device 510(k) decisions runs?

FDA device 510(k) decisions runs in the background. OpenClaw 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 device 510(k) decisions in OpenClaw

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

Paste this into OpenClaw:

Set up OpenClaw

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