One check per order.

Most stores write no code at all. Pick the way that matches your system.

No code

WooCommerce

Install the plugin and paste the one-time code from Settings. Every order is checked and the consent box is added to checkout.

How the plugin works

No code

OptiMantra, or any system with no API

Look the order up on the Lookup screen in Provkeep and paste the text it gives you into the chart.

Lookup and telehealth

Three lines

Your own checkout or platform

Download one file from the code kit and make one call per order. Cerbo works this way.

See the three lines

One address

The rules in Claude, Claude Code or Cursor

Connect provkeep.com/mcp and ask what a state or the FDA published about a peptide. Free with an account, 300 lookups a month.

Set it up

Reference

Every endpoint and field

The API reference, the change policy and an OpenAPI file.

The API reference

Recipes

Provkeep for your stack

Where the check goes in Healthie, Empower, Cerbo, DoseSpot, OpenLoop and more, with the code. No partnership needed.

Every recipe

For platforms

Connect Provkeep

A button in your software. Your customers sign in to their own Provkeep account and pay on their own plan.

How it works

The code kit: three lines, and what comes back

Node, PHP and Python, one file each with nothing else to install. Use your own order number as the second argument, so a retry can never record the order twice.

import { Provkeep } from "./provkeep.mjs";
const pk = new Provkeep(process.env.PROVKEEP_KEY);
const answer = await pk.check({ code: "1042", patient_state: "OH", lines: [{ peptide: "bpc-157" }] }, { idempotencyKey: "1042" });

One file, no dependencies: download provkeep.mjs. It never throws and never holds an order on its own failure.

Order 1042BPC-157, ships to Ohio
RestrictedOhio, the patient's state
Additionally, peptides such as BPC-157 and other bulk drug substances in category 2 and 3 (see FDA guidance ) cannot be compounded because it violates federal and state law.

Ohio: OH pharmacy board: Ten Common Prescriber Clinic and Medical Spa Violations, read 2026-11-20. Open the page it came from

  • Federal position appliesFlorida, the pharmacy's state
  • FederalFDA published safety risks

Check txn_EXAMPLE · the order carries on unless you asked us to hold it

Without the kit: the raw HTTP call, in five languages
curl -X POST https://api.provkeep.com/v2/checks \
  -H "Authorization: Bearer $PROVKEEP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"code":"1042","patient_state":"OH","prescriber_state":"OH","pharmacy_state":"FL","lines":[{"peptide":"bpc-157"}]}'
The full answer, as JSON
200 OKprovkeep-environment: sandbox
{
  "transaction_id": "txn_EXAMPLE",
  "code": "1042",
  "environment": "sandbox",
  "checked": true,
  "recorded": false,
  "hold_requested": false,
  "summary": {
    "label": "What the rules say",
    "status": "restricted",
    "status_label": "Restricted",
    "explains": "The strictest status across the states involved.",
    "decided_by": {
      "line_id": "1",
      "state": "OH",
      "role": "patient"
    },
    "coverage": {
      "label": "What we covered",
      "complete": true,
      "note": "We read the board in every state on this order.",
      "not_fully_read": []
    }
  },
  "ruleset_version": "2026-11-20.1",
  "answered_at": "2026-11-21T02:05:10.083Z",
  "lines": [
    {
      "line_id": "1",
      "peptide": {
        "slug": "bpc-157",
        "name": "BPC-157",
        "sent": "bpc-157"
      },
      "name": null,
      "quantity": null,
      "covered": true,
      "line_status_label": null,
      "ingredients": null,
      "stack_needs_ingredients": false,
      "unlisted": null,
      "reason_code": null,
      "why": null,
      "federal": {
        "position": "fda_safety_risk_withdrawn",
        "label": "FDA published safety risks",
        "channel": "unknown",
        "note": "HHS conditions apply if a licensed pharmacy fills the order.",
        "citations": [
          {
            "quote": "Compounded drugs containing BPC-157 may pose risk for immunogenicity for certain routes of administration and may have complexities with regard to peptide-related impurities and active pharmaceutical ingredient (API) characterization.",
            "source_name": "FDA: certain bulk drug substances that may present significant safety risks",
            "url": "https://www.fda.gov/drugs/human-drug-compounding/certain-bulk-drug-substances-use-compounding-may-present-significant-safety-risks",
            "origin": "federal",
            "retrieved_on": "2026-11-20 17:30:05.716714+00"
          },
          {
            "quote": "BPC-157 Compounded drugs containing BPC-157 may pose risk for immunogenicity for certain routes of administration and may have complexities with regard to peptide-related impurities and active pharmaceutical ingredient (API) characterization.",
            "source_name": "FDA, same page, table headed \"Bulk drug substances nominated but withdrawn\": previously in category 2, withdrawn by the nominators",
            "url": "https://www.fda.gov/drugs/human-drug-compounding/certain-bulk-drug-substances-use-compounding-may-present-significant-safety-risks",
            "origin": "federal",
            "retrieved_on": null
          }
        ]
      },
      "jurisdictions": [
        {
          "state": "OH",
          "name": "Ohio",
          "role": "patient",
          "status": "restricted",
          "status_label": "Restricted",
          "reason_code": "state_published",
          "why": "This state has published wording that forbids it.",
          "coverage": {
            "kind": "board_read"
          },
          "citations": [
            {
              "quote": "Additionally, peptides such as BPC-157 and other bulk drug substances in category 2 and 3 (see FDA guidance ) cannot be compounded because it violates federal and state law.",
              "source_name": "Ohio: OH pharmacy board: Ten Common Prescriber Clinic and Medical Spa Violations",
              "url": "https://www.pharmacy.ohio.gov/documents/pubs/special/ivtherapy/ten%20common%20prescriber%20clinic%20and%20medical%20spa%20violations.pdf",
              "origin": "state",
              "retrieved_on": "2026-11-20 17:30:13.389472+00"
            }
          ],
          "bills": []
        },
        {
          "state": "FL",
          "name": "Florida",
          "role": "pharmacy",
          "status": "federal_limit",
          "status_label": "Federal position applies",
          "reason_code": "state_silent_board_read",
          "why": "This state has published nothing restricting it. What applies is the federal position.",
          "coverage": {
            "kind": "board_read"
          },
          "citations": [],
          "bills": []
        }
      ],
      "lot": null
    }
  ],
  "messages": [],
  "fields_dropped": 0,
  "notice": "Provkeep reports what states and federal agencies have published. It does not say whether an order is lawful."
}

The real answer for this order, worked out as this page loaded. The API also returns considered, requires, not_asked and unknowns on each line, left off here for length.

Three things worth knowing first

It always answers 200

Including when we are down, rate limited or the subscription has lapsed. Read hold_requested, which is true only if you turned on holding Restricted orders, never the HTTP status. A compliance tool that stops a customer trading is worse than no tool.

Test and live keys are separate

A test key talks to sandbox.provkeep.com, which keeps its own database, so nothing reaches your live records. Every response carries provkeep-environment.

We never guess a product

You send the slug. We do not infer it from a product title, because guessing would mean inventing a fact and writing it into the record.

From here to your first checked order

01

Make a test key

Settings, one click. Shown once, and shown again whenever you ask.

02

Send one request

From the sandbox or your terminal. The sandbox hands you the exact call in your language before you send anything.

03

Read the answer

Then swap the test key for a live one. Nothing else changes.

The Sandbox screen in the product, where a test order is built and sent.The Sandbox screen in the product, where a test order is built and sent.
The sandbox, where the first request is sent.

What each status means

Every line of an answer carries one of these as status, with the label below as status_label.

  • RestrictedrestrictedA law, rule or board document this state published says this cannot be compounded, dispensed or shipped. The exact sentence is below.
  • Conditions applyconditionsThis state allows it subject to something: a prescription, a licence, a pharmacy type or a consult requirement. The wording that sets the condition is below.
  • New rule found, see quotenew_ruleThis state published wording about this product that may set a rule, and our reader has not yet confirmed what it sets. Read the sentence and its source below. We do not call it Restricted or Conditions apply until it passes every check.
  • Laws checked, board not yetlaws_onlyWe read this state's statutes and its adopted rules, and nothing in them restricts this product. We do not have its board's own guidance, so quiet here means less than it does in a state whose board we read.
  • Not covered yetnot_coveredNo source we hold for this state answers us, so we are not watching it. We would rather say so than let it look quiet.
  • Federal position appliesfederal_limitThis state has published nothing restricting this product. What governs it is the federal position, which is stated above with its source.
  • Bill pendingbill_pendingNothing this state has published restricts it today, and a live bill would change that. What the bill would do, and where it has got to, are below.
  • No state restriction foundno_restrictionWe read this state's statutes, its adopted rules and its own board's documents, and none of them restricts this product.

Send no patient name, address, email, phone or date of birth. There is no field for them, and anything we do not recognise is dropped unread.

Telehealth platforms, and Cerbo

Check at the moment a prescription is signed, with how the patient was seen and what the product is for. A rule that only applies to telehealth, or to one purpose, is matched to that prescription.

On Cerbo, the clinic’s own developer makes the call and writes the answer into a chart note with the clinic’s own Cerbo access. Provkeep holds no Cerbo credential. A platform with many brands uses one key and names the brand on each call with Provkeep-Account.

A clinic on a system with no API, like OptiMantra, uses the lookup screen in Provkeep and pastes the same text into the chart.

On WooCommerce, the plugin makes the call

Install it, paste one code, and the consent box and the order sync are wired up. Without WooCommerce or without a key it registers no hooks at all, rather than registering a half-working gate.

One thing to know, and it travels with any claim you make about the gate: no order placed through the store’s checkout, classic or Blocks, is created without a consent record, and orders created by other routes do not pass through a checkout. A phone order keyed in by staff, a subscription renewal and a payment link are all other routes. Those are covered by recording consent yourself through the API.