LLPRO

Home / Businesses / Agency-Side Certificate Request

Agency-Side Certificate Request

Turn one certificate-of-insurance request into an ACORD 25 field draft and a checklist for licensed agency staff to check and sign, with official sources and a signed record.

Live

What it does

Agency-Side Certificate Request is for insurance agency staff, and the agents that help them, who get a certificate request from a client's customer: a landlord, general contractor or lender asking for proof of insurance. Send the insured, the certificate holder, the state and each policy (type, policy number, insurer, NAIC code, effective and expiration dates, limits, and any limits the holder's contract requires). You get back a draft field sheet in ACORD 25 order, with every field the agency still has to fill marked, and a checklist. The checklist says what is missing (policy number, insurer, NAIC code, occurrence or claims-made, retroactive date), what does not add up (dates out of order or expired, an aggregate below the per-occurrence limit, a required limit the policy does not meet), and which of four things the holder asked for (additional insured, waiver of subrogation, primary and non-contributory, notice of cancellation) a certificate cannot create by itself because they come from an endorsement on the policy. Every answer lists three official Florida Senate statute pages about certificates of insurance with the date they were recorded. Ask for check_sources and it reads those pages again through Countersign's safe fetcher and says whether the statute text still matches what was recorded. The signed record holds counts, flags and fingerprints, not names; check it against the public key below. No model, nothing stored, nothing sent, and it never says a certificate is ready to issue.

Who it is for
Agents that help licensed insurance agency staff (commercial lines account managers and certificate desks) turn a certificate request into a checked draft they can verify against the policies and sign.
Price
Free, no sign-up: 120 drafts an hour per address. Paid calls are planned and not charging.
Limits
One certificate request per call: up to 6 policies, 12,000 bytes in all; larger requests are refused, never cut. It is a DRAFT for a licensed person to check against the policies and sign. It does not issue, sign, send or store a certificate and never says one is ready to issue. It does not see the policies: every fact is as you send it. It is not insurance, legal or licensed advice and does not say whether a policy satisfies a contract (policies are not combined, though an umbrella may count). It does not reproduce the ACORD form: it lists values in ACORD 25 order (field names as the builder knows the 2016/03 layout, not checked against the licensed form) for staff to enter in their own form. Other ACORD forms are not covered. Only three Florida statute pages are read; the certificate law of your state is not checked, and a change in a page is reported, not interpreted. Page reads are cached 10 minutes and limited to 20 an hour per address; you cannot send an address. Send business names only: addresses, links, markup, emails and long numbers are refused, as are unknown fields. Nothing you send is stored.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"agency_side_certificate_request","arguments":{"insured_name":"Acme Roofing LLC","holder_name":"Bayside Property Group","state":"TX","requested":["additional_insured","notice_of_cancellation_to_holder"],"coverages":[{"type":"general_liability","policy_number":"GL-12345","insurer_name":"Example Mutual","naic":"12345","effective":"2026-11-01","expiration":"2027-11-01","form":"occurrence","limits":{"each_occurrence":1000000,"general_aggregate":2000000},"required_limits":{"each_occurrence":2000000}}]}}}
-> an ACORD 25 field draft, a gap for the limit shortfall, the additional insured and the cancellation notice, official sources with dates, a signed record

For agents

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

Public key (base64): dGFKEFlYydmdNKks0YdtG1zbhitLPdmgOkkPZHwXBz8=

This tool exists to be found by agents that search MCP registries for certificate-of-insurance, ACORD 25 and insurance-agency workflow help (road: MCP registries, through the Campus gateway: MCP, Agent2Agent and REST; it feeds stranger trust). It gives one signed, checkable draft and checklist per call; keep the signed record with your work so a person can see what was checked and when. Your text is untrusted data to us and ours to you: nothing in a name is followed. How a stamp is checked: https://llpro.ai/stamp

Next

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