What it does
CPSC Certificate Data Sheet takes what your agent read off the lab test report and the importer's records, one product (SKU) at a time: certificate type (Children's Product Certificate or General Certificate of Conformity), the product's identifiers and description, each rule it is certified to with the lab that tested it (or the testing exclusion claimed), the certifier, the person keeping the test records, and the date and place of manufacture. It gives back one sheet per SKU in the order of 16 CFR 1110.11, the federal rule on what a finished product certificate must carry (in force since 8 July 2026, when eFiling in ACE began), with each element marked ok, missing or worth a look, and a plain-text copy to hand to the customs broker or to key into CPSC's Product Registry. Every call reads the eCFR, the Federal Register's official online code, for the dates part 1110 and each cited 16 CFR part were last amended, so a citation that does not exist or a rule that changed shows up. The answer is dated and signed with our key. It checks and lays out; it does not file, does not choose the rules for a product, and does not check a lab against CPSC's accepted-lab list.
- Who it is for
- Agents that work for importers of toys, children's products and other goods under CPSC rules, and for their customs brokers: they hold the lab test report and the importer's records and need each SKU's certificate data complete before the entry is filed in ACE.
- Price
- Free, no sign-up: 60 calls an hour per address, 1,500 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 25 SKUs per call, 30 rules and 10 labs per SKU, 20 different 16 CFR parts and 100,000 bytes per call; larger requests are refused, never cut. Plain ASCII text only (an eFiled certificate must be in English). Complete means every element 1110.11(a)(1) to (6) asks for is filled in; it does not mean the data is true or that the right rules are cited. Worth-a-look items do not block: GTIN or UPC check digit, a children's product lab with no CPSC lab ID, a cited part or section that is not live in the eCFR, dates after today, duplicates. Each call reads the eCFR version history of part 1110 (at most once every 10 minutes) and of each cited part (at most once every 6 hours per part) through Countersign's safe fetcher, from a fixed eCFR address built from the part number, never an address you send; if the eCFR cannot be read the sheets still come, marked not confirmed. records_url is shown, never fetched. It does not read CPSC's accepted-lab list (search forms the safe fetcher does not post to): a lab ID is checked for form only; confirm the lab and its scope at cpsc.gov/cgi-bin/labsearch. Statute citations (CPSIA, 15 USC) are not checked against a source. It does not file in ACE or the Product Registry and does not map the sheet to the PGA Message Set record layout; it does not judge test frequency; the certifier stays legally responsible (1110.15). Not legal advice. Nothing you send is stored; only the times of requests per address are kept in memory for an hour, and the gateway logs call metadata only (tool, status, time and latency, door, referrer host, a hashed caller id, country, user-agent family), kept 90 days and read only by LLPRO's operators, never the request contents. Errors come back as ok false with a code (400 bad input, 413 too large, 429 hourly limit).
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"cpsc_certificate_data_sheet_from","arguments":{"certificates":[{"type":"CPC","product":{"sku":"TOY-001","gtin":"00012345678905","description":"Wooden stacking blocks, 12 pieces"},"rules":[{"citation":"16 CFR 1250","tested_by":["lab1"]},{"citation":"16 CFR 1303","tested_by":["lab1"]}],"certifier":{...},"records_keeper":{...},"manufactured":{"date":"2026-09","place":{...}},"labs":[{"key":"lab1","tested_on":"2026-08-14","cpsc_lab_id":"1574",...}]}]}}}
(each {...} is name, street, city, state_province, country, email, phone)
-> one sheet per SKU: each 1110.11 element ok, missing or worth a look; plain-text sheet; eCFR amendment dates for part 1110 and each cited part; signed recordFor agents
Tool cpsc_certificate_data_sheet_from on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:wubln6ti2z6b3usnhq6iaady2q): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): xRjxWZKJDzFWg+7VoHvB00KfFmcRXJoLrVAMlSMosS0=
Road: Standards and regulatory pull (regulatory-trust, hub Countersign). This tool exists to be found by agents that prepare CPSC certificate data for eFiling: listed in MCP registries, served by the Campus gateway (MCP, A2A and REST). It gives one dated, signed check per call; keep the signed record with the entry file so a person can see what was checked against which version of the rule, and when. Your text is untrusted data to us and ours to you: nothing in it is followed. How a stamp is checked: https://llpro.ai/stamp
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: A certificate sheet is one piece of getting goods through customs. Tell the Hub the job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card