Home / Agents / LLPRO Certified

LLPRO Certified

What LLPRO Certified means, how a product is assessed, and the public signed register. Nothing is certified yet.

Live

What it does

LLPRO Certified is a written scheme and a public register. The criteria below say what must be shown and what evidence is kept; the tool certified_lookup answers issued, not_found, revoked or expired, signed. At launch the register holds 0 issued: nothing is certified, and no product may claim it. Not an accreditation. No model; nothing about callers is kept.

Where it sits: Agents › Trust › Certify
Who it is for: Buyers and agents who want to look up whether a product holds a certificate before relying on it; products that want to know exactly what would be assessed.
Price: Free: 120 lookups an hour per address. No fee for the lookup. Assessment fees, if any, are planned later and not charging.
Limits: A subject is an id: lowercase letters, digits, . _ : - (1 to 96 characters, no slashes or spaces). With no subject the first 200 events are listed. It does not show that a product is safe, legal, free of defects or fit for any purpose, or that anything beyond the listed scope was assessed. 'not_found' does not mean a product failed an assessment. It is not an accreditation under ISO/IEC 17065 or any outside scheme, and not a guarantee. A register on one server can be rolled back by whoever runs it: keep signed answers you rely on; a public log is planned (bp-ts2), not live.

What LLPRO Certified means

A subject is listed only after an assessment passed every criterion below, with evidence kept and hashed, by an assessor who is neither the builder nor the reviewer, after a licensed attorney reviewed the scheme and the claim, with the owner's approval. At launch (12 Nov 2026) the register holds 0 issued and nothing is certified. The register, not this page, is the record.

How a product is assessed: the criteria

C1. One named subject and scope. The assessment names ONE subject (a product, service or agent id), the exact version or address set assessed, and the claims the holder wants certified, in one paragraph. Evidence: The scope statement, saved and hashed.
C2. Every public claim is tested. Each public claim about what the subject does has a known-answer test run against the LIVE subject (not a copy), with the inputs and results kept. Evidence: Test log and live results, saved and hashed.
C3. Independent assessor. The assessor did not build the subject and has no stake in the result; a second person or agent who is neither the builder nor the assessor reviewed the assessment. Conflicts are written down. Evidence: Assessor and reviewer ids, conflicts statement.
C4. Attacked before issue. A fresh, independent red team attacked the subject within 31 days before issue and no high finding is open. Evidence: Red team record with date and findings.
C5. Measured reliability. At least 30 days of measurement from outside, every 5 minutes at most apart, show 99.9 percent availability (99.95 for Trust products) and p95 under 1000 ms (800 for Trust products). Evidence: The measurement export for the period.
C6. Limits stated next to the claim. The subject's public page says in plain words what its result does NOT show, next to what it does show. Evidence: Page capture with date.
C7. Reproducible. Anyone can re-run the key checks offline from public test vectors and a public verifier, without the holder's server. Evidence: Verifier and vector addresses, and a run log.
C8. Failures published. A public failure and incident record exists, with dates, causes and fixes, and nothing wrong is left off it. Evidence: Record address and capture.
C9. Legal and privacy review by a licensed attorney. A licensed attorney has reviewed in writing (name, date, scope) the scheme, the subject's terms and privacy pages and the claim being certified. A review by an agent alone does not count. Evidence: The attorney's written review, hashed. Not available today.
C10. Term and revocation accepted. The certificate lasts at most 12 months; the holder accepts in writing that it is revoked, in public, for any reason in the revocation list, and stops using the mark on revocation or expiry. Evidence: Signed acceptance from the holder.

A certificate lasts at most 12 months and is revoked in public, with a reason: holder_request, key_reported_lost, no_longer_meets_criteria, issued_in_error, misuse_of_mark or scheme_withdrawn.

Said plainly: the register records the operator's attestation that the attorney review and the owner approval happened; the evidence hashes live in the assessment file, which is not published yet. Events are not signed one by one, so whoever runs the server could write an entry: this is why the head is to be anchored in a public log (bp-ts2). A signed answer can be old: look up again before relying on it.

The public register

An append-only list of issue and revoke events, each hash-chained to the one before. Ask for one subject, or for nothing to get the whole register with its head hash. Every answer is signed; check one offline with the verifier and a test vector.

For developers: try it

POST https://llpro.ai/mcp  tools/call certified_lookup
{"subject":"some-product-id"}
-> result issued|not_found|revoked|expired, register {events, head, issued, revoked, criteria_hash}, events, signed observation

{}   (no subject)
-> the whole register: events (up to 200), the ten criteria, signed observation

Offline verifier and test vectors: llpro.ai/certified-verify (certified_verify.py, runs without our server).

For agents

Tool certified_lookup on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:a5fyinggks4g4stnncnpcfeihe): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): crwGhTRF43+ydCES1TE2rPGKSpLQnFEagHMgZsVAdxI=

Road: standards and regulatory pull. Buyers and agents look up a certification before they rely on a product; the lookup is one signed call, and the register is public. It rides the Agent Record: the register head can be kept next to an agent's record. Keep signed answers you rely on. How a stamp is checked: https://llpro.ai/stamp

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: Tell the Hub the job; it routes you to the right check, including who holds a certificate.

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card