GOVERNMENT AGENCIES · BENEFITS PLATFORMS · GOVTECH

Verify once. Reuse across programs.

Help people access services without proving the same facts at every step. Turn income, residency, and enrollment records into reusable, source-backed evidence—with the applicant’s consent.

Talk to us Explore the workflows ↓

One set of evidence. Multiple applications. Each program keeps its own rules.

VERIFY ONCE. REUSE WITH CONSENT.ILLUSTRATION

IncomeAddressEnrollment

ONE SET OF SOURCE-BACKED RECORDS

Evidence that can go further.

SourceVerified fieldsTimestamp

Housing support

Fee waivers

Benefit renewals

Shared with permission. Accepted by each program.
Refreshed when current evidence is required.

IN YOUR EXISTING PROCESS

Less repeated paperwork. More people moving forward.

An applicant should not have to upload the same records for housing support, a fee waiver, and a renewal. Add a reusable verification layer to your intake: retrieve evidence from the accounts they already use, then share the relevant fields across participating programs with their permission.

01Applicant connects a source
02Verify and reuse evidenceRECLAIM
03Programs apply their rules

WATCH THE VIDEO

Plaid for Government Benefits.

The case for connecting people’s verified records to the programs that need them.

Watch on YouTube

THREE PLACES TO START

Reach the records traditional checks miss.

Income beyond payroll databases

“My income comes from gig work.”

Candidate source: The applicant’s gig-platform earnings account, such as a delivery or rideshare account, where the required records are available.
Information returned, where available: EarningsEarnings periodSourceVerification date
In your service workflow: Fill a missing income check for an applicant outside your payroll coverage. Reuse the evidence for another program when consent and freshness requirements allow.

Residency beyond uploaded bills

“I live in the area this program serves.”

Candidate source: An authenticated utility or telecom account that displays the account holder and service address.
Information returned, where available: Account holderService addressAccount status
In your service workflow: Retrieve an address record directly when a document upload is missing or hard to authenticate. Let each program assess whether it meets its residency requirements.

Enrollment beyond manual letters

“I’m currently enrolled at this institution.”

Candidate source: The applicant’s university or training-provider portal, where current enrollment is shown.
Information returned, where available: InstitutionEnrollment statusTerm or dates
In your service workflow: Support a student travel concession, training allowance, or fee waiver with the same enrollment evidence instead of requesting another letter.

YOUR WORKFLOW STAYS YOURS

Keep the checks that work. Fill the gaps.

When a payroll connection, database lookup, or document check cannot answer a question, add a source-account check at that point. Return the evidence to the same case-management workflow your team already uses.

KNOW WHAT THE EVIDENCE MEANS

Reusable evidence. Program-specific decisions.

Each participating program defines which evidence it accepts and how recent it must be. Store the verification along with the audit trail, for reuse later.

FITS YOUR EXISTING WORKFLOW

A verification step.
Inside your product.

Add Reclaim at the point you need more evidence: a difficult eligibility criterion, a receipt exception, or an agent waiting on a user-authorized check.

Choose a source and the information to retrieve.
Let your user authorize the connection.
Verify returned proofs on your backend and apply your rules.

Developer documentation

CREATE A VERIFICATION REQUESTNode.js · server

import { ReclaimProofRequest } from '@reclaimprotocol/js-sdk';

const reclaimProofRequest = await ReclaimProofRequest.init(
    process.env.RECLAIMPROTOCOL_APP_ID,
    process.env.RECLAIMPROTOCOL_APP_SECRET,
    'ff4d7afe-4b78-4795-9429-d20df2deaad7' // Example. Replace with provider ID
)

const exportedProofRequestJsonString = reclaimProofRequest.toJsonString();

Building for AI agents?

Use Reclaim when a workflow needs source evidence with a user’s authorization. Explore the verification letters API and MCP instructions.

Agent instructions

BUILT FOR YOUR REVIEW PROCESS

Evidence you can examine.
A team you can evaluate.

YBacked by Y Combinator

AI retrieves the requested information. Cryptographic verification helps your application check the returned evidence.

Explore the Trust Center

SOC 2 Type IIIndependent audit

ISO 27001Information security

GDPRReadiness

A FEW USEFUL ANSWERS

Before your first test.

Discuss your workflow

What does reusable verification mean?

A verified record can support more than one participating service without asking the applicant to retrieve the same information again. Each use depends on the applicant’s consent, the receiving program’s accepted evidence, and its freshness requirements.

Where can this fill a gap in our current verification?

Start with a claim your current checks cannot resolve: gig income outside a payroll database, a service address behind a utility login, or enrollment in an institution without an integration. We test whether the applicant’s source account exposes the fields your program needs.

Can this work with our benefits portal or case-management system?

Add a verification link to intake or a caseworker’s request for more evidence. Return structured fields and source context to your existing workflow, where your team applies program rules.

Does verified evidence automatically establish eligibility?

Your program determines eligibility. A source record answers a specific question; your team still assesses all program requirements and maintains a review path for applicants who cannot connect an account.

ONE CLAIM. ONE SOURCE. A PLACE TO START.

Which verification gap is holding up your service?

Talk to us