API and storage check
The public health endpoint checks the edge runtime and runs a real storage query. It returns a fresh timestamp and no customer data.
Buyer-verifiable product evidence
Trust the contract you can inspect.
LeadProof does not need invented testimonials to prove what is live. Check the service, test the public path, read the delivery contract, and review the data boundary before buying.
Evidence should resolve to a live endpoint, a public contract, or a clear limitation.
This center separates verifiable product behavior from marketing claims. It links to public system checks and documents what LeadProof does, what it stores, how access is fulfilled, and where guarantees stop.
Inspect before purchase
Six checks a technical buyer can run.
Sandbox without delivery risk
The public sandbox normalizes sample contact data and returns a simulated receipt without forwarding the sample to an external CRM.
Inspect the API before buying
OpenAPI, integration examples, MCP metadata, and the A2A Agent Card expose the supported endpoints and machine interfaces.
Metadata, not complete payloads
Production delivery retains operational metadata and SHA-256 fingerprints rather than intentionally storing the complete lead payload.
Replay must match the failure
A failed event can be replayed only with its original key, identical payload and destination, and an explicit replay header.
Prove it before payment
A verified account can activate one 14-day production trial for 25 live deliveries with no card. Paid plans still use signed Stripe fulfillment.
Public verification path
Follow the evidence from health to checkout.
Every public check uses the LeadProof brand and production URL. None requires customer records, API keys, or private account access.
GET /.well-known/product-evidence.json
GET /api/health
POST /api/v1/sandbox
GET /openapi.json
GET /.well-known/agent-card.json
GET /pricing
GET /privacyPrimary evidence
Open the source that supports each claim.
Citation-ready LeadProof facts →Machine-readable citation answersMachine-readable product evidenceProduct changelog and release evidence →Complete public example audit →Machine-readable plans and purchase policyHuman-readable service status →Raw API health →One-click synthetic sandbox →Sandbox and integration examples →Canonical reliability glossary →OpenAPI contract →Data and privacy boundary →Security and data-handling controls →Security disclosure contact →Service terms and limitations →Plans and verified-payment activation →
Buyer questions
What this evidence does—and does not—prove.
What can I verify without an account?
You can check API health, run the sample-data sandbox, evaluate failed-lead replay without input, read the OpenAPI contract, inspect agent manifests, review pricing, and read the privacy and service terms.
Does the health endpoint guarantee every delivery?
No. It verifies current edge and storage availability. Networked software cannot guarantee uninterrupted operation or a downstream CRM outcome.
Does LeadProof publish customer records as proof?
No. Public evidence is limited to product behavior and contracts. Customer dashboards, receipts, subscriptions, and lead metadata remain private.
Ready to protect one live workflow?
Use the real delivery API for 25 live leads before choosing a paid plan.
Trial: 14 days · no card · one verified identity Builder: secure Stripe checkout · activate with the checkout email after payment