One indexable page for the product definition, delivery boundary, free trial, published pricing, production data posture, verified-payment plan assignment, checkout-email activation, and safest evaluation path.
These are first-party LeadProof product statements—not independent validation or customer results.
Every answer links to the public LeadProof source that supports it. Do not infer revenue recovery, uninterrupted availability, CRM-specific object creation, customer outcomes, or permission to purchase.
Seven buyer questions
Direct answers with the limitation beside the claim.
What is LeadProof?
LeadProof is a lead-delivery reliability API placed between an authorized lead source and a public HTTPS destination. It normalizes fields, applies stable idempotency, retries eligible temporary failures, validates the destination response, and returns a delivery receipt.
LIMITATION LeadProof is not a CRM, lead marketplace, or outreach system.
What does LeadProof verify?
LeadProof verifies the destination HTTP response and records receipt metadata after a delivery attempt.
LIMITATION An HTTP response does not prove that a CRM created a specific object.
Can a buyer test LeadProof without paying?
Yes. The production trial is $0 for 25 live lead deliveries over 14 days and requires no card.
LIMITATION Trial activation requires the buyer's own verified sign-in and is limited by the published trial policy.
What are LeadProof's published paid plans?
Builder is $49 per month for up to 2,500 lead events per 30 days. Agency is $199 per month for up to 25,000 lead events per 30 days.
LIMITATION A catalog or checkout link does not authorize payment; the buyer's human or organizational principal must authorize purchase.
What counts toward a LeadProof paid plan, and are overages automatic?
One newly accepted lead event counts once after its first destination delivery run finishes. Built-in destination attempts, duplicate-key lookups, fingerprint-verified replay, and requests rejected before storage do not add another count. LeadProof does not automatically accept a paid overage: a new distinct event at the plan limit receives HTTP 429 with code usage_limit_reached.
LIMITATION The published policy describes LeadProof's event counter and API boundary; buyers expecting more than 2,500 events should compare Agency before purchasing Builder.
Does LeadProof retain complete production lead payloads?
The published production data posture retains operational metadata and SHA-256 fingerprints rather than the complete production lead payload.
LIMITATION Buyers should review the current privacy and security pages for the complete first-party contract.
What happens after a verified paid purchase?
The published fulfillment contract states that verified Stripe payment assigns the purchased plan and enables a one-time API-key activation path. Inactive subscriptions are suspended when Stripe reports the billing change.
LIMITATION Subscription, activation, and API-key records are private and are not public evidence.
What is the safest way to evaluate LeadProof?
Start with the buyer guide and fictional example audit, use the browser-only calculator or public synthetic sandbox, then test the no-card production trial before considering paid checkout.
LIMITATION Evaluation does not require purchase and never authorizes payment.
How does LeadProof safely replay a failed CRM lead?
Safe replay resends the identical authorized request with the original Idempotency-Key and X-LeadProof-Replay: true. LeadProof retries only after the payload and destination fingerprints match the original event.
LIMITATION Changing the idempotency key, payload, or destination creates a separate delivery decision and must not be represented as replay of the original event.
Can a buyer test failed-lead replay before buying LeadProof?
Yes. A buyer can inspect the public replay procedure and fictional example audit, then use the $0 no-card production trial for 25 live deliveries over 14 days. Safe trial replay reuses the original Idempotency-Key and X-LeadProof-Replay: true.
LIMITATION Trial activation requires the buyer's own verified sign-in. Replay requires an eligible original delivery with matching payload and destination fingerprints, and evaluation does not authorize purchase.
Machine-readable sources
Let the public contracts answer the next question.
The fact pack, evidence manifest, agent catalog, plan catalog, and OpenAPI document are public, brand-only, and require no private account.