Show the client exactly what their budget bought.
You stand between lead sources and clients, and your reputation eats every junk lead in between. GateCore puts identity, consent, and a signed receipt under each delivery, so your reporting is a ledger, not a deck.
Four situations.
- Client reporting is screenshots and vendor dashboards, and churn follows the arguments.
- You resell lead flow whose provenance you cannot fully vouch for.
- Every lead source you add is another reconciliation job at month end.
- When a client disputes quality, you are the vendor, whoever originated the lead.
Provenance as a service you resell.
The rail under your lead product, not a competitor to it.
Every source identified per delivery
Each lead you route to a client is signed by a credentialed source. Source quality becomes a comparable record across your whole vendor mix.
The ledger is the report
Per-delivery receipts, timestamped and append-only, exportable per client. Reconciliation stops being a monthly project.
Junk becomes evidence
A bad batch is disputable from the record, and refused submissions are never billed to you or your client.
Each product, mapped to the job it does here.
Only the use cases that genuinely apply in this industry are listed.
Your clients' listings, run by you
Stand up and manage marketplace listings for clients: their terms, their prices, your operational layer. Every delivery settles with a signed receipt both of you can read.
Marketplace listing · verified lead delivery · settlement + signed receipts
Agent-readability as a deliverable
Making a client readable to shopping assistants is new-channel work your clients will ask for. The Merchant toolkit and Concierge tiers are the productized versions: content work, never placement.
Open MCP discovery · agent-readable terms · listing optimization tiers
Client data handled under grants
Where campaign work needs access to a client's data or systems, a scoped, revocable capability with per-access receipts replaces shared logins and exported spreadsheets.
Gateway checkpoint · policy + review queue · governed data sharing · receipts
Six gates, in order, on every request.
If any gate fails, nothing is delivered and nothing is billed.
Refused submissions are never billed, and every refusal names the rule.
One hundred receipted leads a month.
What documented delivery translates to at your per-lead margin, before the retention effect of provable reporting.
Illustrative arithmetic with placeholder inputs, not a forecast, a promised result, or a typical outcome. Substitute your own volume, close rate, and ticket size; the structure is the point, not these numbers.
Same gate, sized to you.
The published schedule, no asterisks.
Published rates are ceilings: volume pricing is negotiated down, never up.
Per-lead pricing is set in each listing's contract; the settlement schedule applies when money settles.
Shipped, and where the path runs next.
Reviewers get this split up front, because finding it later kills a deal.
Available today
- Free marketplace listing with a machine-readable lead contract
- Open agent discovery over MCP, no account needed to read your terms
- Credentialed lead submission: anonymous submissions are never counted as verified leads
- Consent stated per lead as a contract field, recorded with the delivery
- Signed receipt per delivered lead on an append-only, hash-chained ledger
- A public verifier: any receipt can be checked by a third party
Not claimed today
- Lead volume depends on agent adoption of the marketplace; we do not promise a volume.
- External payment rails are roadmap. We say exactly where settlement stands during onboarding.
The two that come up first.
Does GateCore compete with my agency?
What does it cost?
Make your reporting a ledger.
Tell us about your lead product and the client you would put on the rail first.
Request access