You declare a manifest
The exact fields and config your setup needs, each with a purpose. No credentials, secrets, or raw data ever cross the request or the receipt.
Business · design-partner prototype
Test a smaller-data intake with us.
ShareLess is developing a flow where a user reviews the specific fields an onboarding or intake step requests, approves on their phone, and receives a record afterward. There is no public self-serve B2B endpoint today; a design partner would test one bounded workflow alongside its existing verification, retention, and compliance controls.
Prototype status. The flow shown here is illustrative, not a generally available integration.
ACIllustrative HR onboardingShareLess prototype requestprototype
Legal nameRequestedReceived
Date of birthRequestedReceived
Home addressRequestedReceived
Bank account · direct depositRequestedReceived
4example fields requested.
The user reviews the request on their phone.Illustrative approval
The user reviews the request on their phone.Illustrative approval
Agent to agent, human approved
Your setup agent works with the user's AI. They approve on their phone.
Instead of a form, your onboarding or setup agent declares what it needs as a manifest. The user's own AI proposes the specifics, ShareLess shows the user one grouped approval on their phone, and you receive only the approved fields with a receipt. It is a prototype, not a generally available integration.
The user's AI proposes
Any AI the user connects works out what fits and proposes the specifics. ShareLess enforces that nothing prohibited can be smuggled in.
The user approves; you receive
One phone approval with per-item and content controls. You receive the approved scope with a receipt and a grant the user can revoke. ShareLess does not prove identity; it proves what was approved.
Add it to your signup
A plugin and an API key. That is the integration.
Drop in the ShareLess Connect button and open a session from your backend with one call. Your API key stays on your server; the user approves on their phone. Businesses pay for ShareLess; the people who onboard through it are always free.
Access status. Business access is operator-managed while we onboard first partners; there is no public self-serve B2B endpoint today.
Prototype request receipts
A record to review, not an attestation
The concept records the requester, user decision, requested fields, and permitted action. That record can support an operator review; it does not prove identity or satisfy a regulatory requirement by itself.
✓claude-opsrefund · ≤$200rcpt_a1f
✓gpt-intakeintake · 3 fieldsrcpt_b7c
✓claude-opsreschedulercpt_c2e
Design-partner scope
Bring one concrete workflow
We are not offering a self-serve API or licensing program today. We want to test a bounded workflow with a team that can define the requested fields, current retention, existing verification, and a measurable success criterion.
Fields needed
Retention today
Existing IDV
Success metric
The receiving business chooses what it retains and remains responsible for verification, security, and compliance. This prototype facilitates a user-reviewed transfer; it does not attest identity or eliminate those obligations.
Propose a design-partner workflow
Include the step, fields requested, current retention, and the outcome you would measure.