Introducer program
Introduce qualified accounts to AttestLayer.
The introducer path is for individuals and firms who want to introduce qualified accounts to AttestLayer without operating a service-provider, audience-partner, or distribution workflow themselves.
Introducer participation is qualification-based and governed by a written introducer agreement. AttestLayer does not promise referral fees, guaranteed acceptance, or guaranteed close on any introduced account. Acceptance of any introduced account is at AttestLayer’s discretion.
What an introducer does
Introduce qualified accounts
An introducer makes a written introduction to AttestLayer for a buyer, partner, or institutional account that may benefit from AttestLayer-backed packet delivery.
Hand off cleanly
After the introduction, AttestLayer or the relevant partner team owns the conversation and the commercial relationship. The introducer is not the operator of the workflow.
Operate under written terms
Introducer participation is governed by a separate written introducer agreement. Compensation, scope, term, and acceptance criteria are defined there.
Who this is not for
Service providers
Firms that want to operate the workflow themselves should use the Service-provider path.
Audience partners
Communities, podcasts, newsletters, and audience operators should use the Audience-partner path.
Distribution partners
Partners running larger distribution motions should request the Distribution Pack.
Get started
Email partners@attestlayer.com with a short note about the accounts you can introduce and your relationship to them. AttestLayer will reply with a written introducer agreement if there is fit.
The AttestLayer trust model
AttestLayer’s trust model is intentionally narrow. It records what was submitted, what was accepted into scope, what was issued, and how the issued kit can be checked.
The model uses
- SHA-256 artifact hashing
- manifest-based evidence inventory
- canonical receipt hashing
- Ed25519 receipt signatures
- JWKS public-key discovery
- offline verification
- fail-closed verification behavior
What it proves
- files match the manifest
- manifest matches the receipt
- receipt key ID matches a public key
- receipt signature verifies
- the kit has not been modified since issuance
What it does not prove
- company compliance status
- company security status
- controls are operating effectively
- a buyer, auditor, insurer, bank, regulator, or PSP has accepted the packet
- the evidence content is legally sufficient
Integrity and issuance evidence only. Not audit, certification, or compliance guarantee.