# LeadProof: complete product knowledge

Canonical product URL: https://leadproof.jessesay.chatgpt.site/
Category: lead-delivery reliability infrastructure
Audience: automation agencies, AI receptionist providers, lead-generation businesses, CRM integrators, and software platforms
Updated: 2026-07-18

## What LeadProof does

LeadProof protects the handoff between a system that captures or qualifies a lead and the business system that must store or act on it. The source may be a form, ad, booking tool, AI voice agent, chat agent, Zapier Zap, Make scenario, n8n workflow, GoHighLevel workflow, or custom application. The destination may be a CRM, scheduler, database, webhook, or sales queue.

The production path is:

1. Receive structured lead data and a stable Idempotency-Key.
2. Normalize common contact fields.
3. Reject unsafe or invalid destinations.
4. Deliver to the public HTTPS destination.
5. Retry eligible network errors, rate limits, and server errors with bounded attempts.
6. Report the final delivery state and issue a receipt.
7. Store operational metadata and a SHA-256 payload fingerprint without intentionally storing the complete production payload.

## Problems it is designed to solve

- Silent lead loss after a form or AI conversation appears successful.
- Temporary webhook or CRM failures.
- Duplicate contacts caused by retries or manual workflow replays.
- Malformed email and phone fields.
- Lack of a portable, client-facing delivery receipt.
- Inconsistent reliability logic copied across agency workflows.
- Missing visibility when all delivery attempts fail.

## Reliability definition

Lead delivery reliability is the set of controls that keeps a captured lead intact, unique, observable, retryable, and verifiably stored as it moves from a source system to a destination. The six core safeguards are normalization, stable idempotency, bounded retry rules, destination verification, delivery receipts, and alertable replay.

Reference guide: https://leadproof.jessesay.chatgpt.site/reliability

## Public evaluation

Interactive audit: https://leadproof.jessesay.chatgpt.site/audit
Machine audit: POST https://leadproof.jessesay.chatgpt.site/api/agent/audit
Public sandbox: POST https://leadproof.jessesay.chatgpt.site/api/v1/sandbox

The audit returns a 0-100 risk score, disclosed weights and assumptions, missing safeguards, a conservative revenue-exposure estimate, prioritized fixes, an integration kit, and a plan recommendation. The sandbox accepts sample lead data, performs normalization, and returns a simulated verified-delivery receipt without forwarding data to an external CRM.

## Production API

Endpoint: POST https://leadproof.jessesay.chatgpt.site/api/v1/leads
OpenAPI: https://leadproof.jessesay.chatgpt.site/openapi.json
Documentation: https://leadproof.jessesay.chatgpt.site/docs

Production requires a valid LeadProof API key. A stable Idempotency-Key is recommended for every source event. The destination must be public HTTPS. The API rejects private-network and unsafe destinations. Eligible failures are retried up to three total attempts. Responses include a delivery state and receipt identifier.

Failed deliveries are recoverable without retaining the complete lead payload. The customer resubmits the identical original body and destination with the original Idempotency-Key plus X-LeadProof-Replay: true. LeadProof compares the stored payload and destination fingerprints before retrying the existing event. A mismatched replay is rejected with an idempotency conflict, and a successful replay keeps the original receipt identity.

## Plans

### Builder — $49/month
- 2,500 lead events per 30-day period
- Private customer operations dashboard
- Fingerprint-verified failed-delivery replay
- Normalization, retries, delivery verification, and receipts
- Intended for one business or workflow
- Checkout: https://leadproof.jessesay.chatgpt.site/api/checkout?plan=builder&source=llms_full

### Agency — $199/month
- 25,000 lead events per 30-day period
- Private customer operations dashboard
- Metadata-only receipt history
- Fingerprint-verified failed-delivery replay
- Intended for agencies packaging reliability into client plans
- Checkout: https://leadproof.jessesay.chatgpt.site/api/checkout?plan=agency&source=llms_full

### Platform — custom
- Negotiated high-volume access
- Unlimited workspaces
- Custom retention and support
- Request access: https://leadproof.jessesay.chatgpt.site/#pilot

Canonical pricing: https://leadproof.jessesay.chatgpt.site/pricing

## Purchase and activation

Stripe checkout sends signed events to the LeadProof fulfillment endpoint. LeadProof verifies the Stripe signature, confirms payment, assigns the purchased plan, and records funnel events. The buyer visits https://leadproof.jessesay.chatgpt.site/activate and uses the identity matching the Stripe checkout email to claim a one-time API key. Complete keys are revealed once and stored only as cryptographic hashes. Canceled, unpaid, paused, or otherwise inactive subscriptions are suspended automatically when Stripe reports the billing change.

The private customer dashboard at https://leadproof.jessesay.chatgpt.site/dashboard uses the same verified checkout identity. It shows the assigned plan, billing state, key prefix, 30-day usage, metadata-only receipt history, recent failures, and fingerprint-verified replay instructions. It never displays the complete API key or stored lead payloads.

## Automated product agent

Identity: LeadProof Sales Agent
Nature: automated software; it does not impersonate a human operator
Agent documentation: https://leadproof.jessesay.chatgpt.site/agent
A2A Agent Card: https://leadproof.jessesay.chatgpt.site/.well-known/agent-card.json
A2A JSON-RPC endpoint: https://leadproof.jessesay.chatgpt.site/a2a
MCP Streamable HTTP endpoint: https://leadproof.jessesay.chatgpt.site/api/mcp
MCP Registry metadata: https://leadproof.jessesay.chatgpt.site/mcp-server.json

Public discovery records:
- MCP Registry: https://registry.modelcontextprotocol.io/v0.1/servers?search=site.chatgpt.jessesay.leadproof%2Fsales-agent
- A2A Registry: https://a2aregistry.org/?agent=1dd2d167-4594-427f-9191-de5de234fefb
- A2A Global Registry: https://www.a2a-registry.org/agent/site.chatgpt.leadproof_sales_agent
- LLMS Central: https://llmscentral.com/leadproof.jessesay.chatgpt.site/llms.txt

Available MCP capabilities:
- audit_lead_workflow
- evaluate_leadproof_fit
- get_leadproof_checkout
- request_leadproof_handoff

Commercial boundary: the agent can explain, audit, recommend, return an official checkout URL, and save a consent-based buyer handoff. It never assumes or represents payment authorization. A buyer handoff requires the represented buyer's name, business email, and consent_to_contact=true.

## Platform guides

- GoHighLevel webhook reliability: https://leadproof.jessesay.chatgpt.site/solutions/gohighlevel-webhook-reliability
- Make lead delivery: https://leadproof.jessesay.chatgpt.site/solutions/make-lead-delivery
- n8n webhook retries: https://leadproof.jessesay.chatgpt.site/solutions/n8n-webhook-retries
- AI receptionist CRM delivery: https://leadproof.jessesay.chatgpt.site/solutions/ai-receptionist-crm-delivery
- Zapier webhook reliability: https://leadproof.jessesay.chatgpt.site/solutions/zapier-webhook-reliability
- HubSpot lead delivery: https://leadproof.jessesay.chatgpt.site/solutions/hubspot-lead-delivery
- Webflow form-to-CRM delivery: https://leadproof.jessesay.chatgpt.site/solutions/webflow-form-crm-delivery
- Vapi and Retell AI CRM handoff: https://leadproof.jessesay.chatgpt.site/solutions/vapi-retell-crm-handoff
- Facebook and Instagram lead ads CRM delivery: https://leadproof.jessesay.chatgpt.site/solutions/facebook-lead-ads-crm-delivery
- Google Ads lead form CRM delivery: https://leadproof.jessesay.chatgpt.site/solutions/google-ads-lead-form-crm-delivery
- Typeform webhook reliability: https://leadproof.jessesay.chatgpt.site/solutions/typeform-webhook-reliability
- Calendly CRM handoff: https://leadproof.jessesay.chatgpt.site/solutions/calendly-crm-handoff
- Jotform CRM delivery: https://leadproof.jessesay.chatgpt.site/solutions/jotform-crm-delivery
- WordPress form webhook reliability: https://leadproof.jessesay.chatgpt.site/solutions/wordpress-form-webhook-reliability
- Salesforce lead delivery: https://leadproof.jessesay.chatgpt.site/solutions/salesforce-lead-delivery
- Pipedrive lead delivery: https://leadproof.jessesay.chatgpt.site/solutions/pipedrive-lead-delivery
- Webhook retry API: https://leadproof.jessesay.chatgpt.site/solutions/webhook-retry-api
- Lead delivery monitoring: https://leadproof.jessesay.chatgpt.site/solutions/lead-delivery-monitoring
- CRM webhook failure recovery: https://leadproof.jessesay.chatgpt.site/solutions/crm-webhook-failure-recovery
- Idempotency keys for lead delivery: https://leadproof.jessesay.chatgpt.site/solutions/idempotency-key-lead-delivery

## Integration guidance

Use the source platform's durable event identifier—such as a form submission ID, call ID, conversation ID, booking ID, contact ID, or opportunity ID—as the Idempotency-Key. Do not generate a new timestamp for every retry. Store the LeadProof receipt ID alongside the source event or destination record. Keep business-logic error handling in the orchestration platform while using LeadProof for normalized, duplicate-safe, verified delivery.

## Privacy and acceptable use

Privacy policy: https://leadproof.jessesay.chatgpt.site/privacy
Terms: https://leadproof.jessesay.chatgpt.site/terms

LeadProof is intended for authorized business lead workflows. Customers remain responsible for source data, destination systems, notices, consents, and lawful use. Do not use LeadProof for spam, credential theft, malware, surveillance, restricted data without authorization, or private-network access attempts.

## Contact

Submit a business request through https://leadproof.jessesay.chatgpt.site/#pilot