Proof Rail Sign in

Is this real?

Check any website, X handle, email or wallet in seconds.

Free for everyone. Companies get verified so their real channels show a green tick.

Public lookup · no account required · nothing you paste is stored
Get verified

Example results

@ProofRailme ✓ Verified by Proof Rail
@example_lookalike Not verified

For companies and finance teams

Verification infrastructure for digital finance

Checked against the source. Not just hosted.

Proof Rail takes a payout, a licence, a settlement or an on-chain claim, checks it against the exchange, the register or the chain where a connector exists, and issues a signed record anyone can verify in one click. Where nothing can be checked, the record says so.

One API call. One verification link. Every record states what was checked, against which source, and when. "Trust us" becomes "verify it".

Request your first record ↗ Verify a live record

A free enquiry. We reply with the evidence needed and any fee before work begins.

CompanyLicenceSettlementOn-chainPayoutWhat the agent is allowed to do

The Proof Gap

Stop asking
to be trusted.

Your company knows something is true. Your counterparty still has to verify it. Proof Rail closes the distance between the claim and the evidence.

Manual process

Without Proof Rail

  1. 01Emails
  2. 02Documents
  3. 03Screenshots
  4. 04Questions
  5. 05Rechecking
Verification infrastructure

With Proof Rail

  1. 01Claim
  2. 02Source
  3. 03Proof Rail
  4. 04Verified

The product is the proof

Open it. Inspect it.
Verify it yourself.

Every live record exposes its status, how it was checked, its issuer, timestamp and lifecycle, without requiring a Proof Rail account.

3 records issued · 1 public · See the directory

Public verification

Verify a certificate

Enter a Proof Rail ID or paste a verification link.
Public lookup · No account required

What “verified” actually means

Anyone can print the word
“verified.”

Most proof products have one tier and one word for everything they issue: a self-reported number and an independently checked one look identical. Proof Rail names the standard on the face of every record, so the reader knows which of four they are looking at before they decide what it is worth.

  1. 01

    Self-Reported

    The issuer says it. Proof Rail records who said it, when, and that nothing was checked. Useful, and never dressed up as more.

  2. 02

    Source Checked

    Confirmed against a named registry, chain, API or signed instruction. The record states the source and the time it was checked.

  3. 03

    Evidence Reviewed

    A reviewer examined the underlying documents against a published policy and recorded the result, the limitations and their reasoning.

  4. 04

    Continuously Monitored

    Re-checked on a schedule. If the underlying fact changes, the record changes: it can be suspended, superseded or revoked, in public.

A record that can never be withdrawn is worth less, not more. Every Proof Rail record carries a live lifecycle and a signature you can recompute yourself against our published signing key. Read the verification standard →

When software moves the money · new

A settlement record shows
the money moved.

It does not show that the program moving it was allowed to. Every other claim on this page is something your counterparty already asks you to prove. This one is the question they have not learned to ask yet.

  1. Week one

    A customer's payment agent initiates a USDC payout to a supplier. It settles.

  2. Week four

    The customer disputes it, we never authorised that.

  3. What you can show

    That the money moved. The instruction the agent acted on is in your own database, which is exactly the evidence a disputing counterparty will not accept.

  4. With a Proof Rail record

    The owner signed the mandate before the act, this agent, this act, this limit, this session, and the signature was checked against a key registered beforehand.

The key has to be registered before the mandate was granted. A signature verifies just as happily against a key minted afterwards, so without that ordering rule an owner could produce a key and a signature for any authorization it later wished it had granted. Proof Rail refuses the claim if the key came second.

See a live agent authorization record How it works ↗

A simple first step

Request your first record.

Tell us what you need to prove. This is an enquiry, not instant record creation. No integration or sales call required.

  1. Send your claim

    Choose a type and describe what you need checked. Sending the request is free.

  2. We reply by email

    We explain the evidence needed, the verification route and any fee before work begins.

  3. Agree the next step

    You decide whether to proceed. A record is issued only after the applicable checks are completed.

Building with the API?

Create an account for sandbox access. This is separate from requesting a record.

Sign up for API access

What do you need to prove?

Choose a claim type

Enquiry · No charge. This does not issue a record or start a paid review. Custom work requires an agreed quote. See verification prices.

We will reply to the work email you provide. No record is issued on submission.

Product-led onboarding

Start with proof, not a contract.

Your first standard Proof Rail record is free.

  • No integration required
  • No credit card
  • No commitment

We first confirm that the claim fits a supported standard evidence path. Third-party data fees and complex human review are scoped before any work begins.

Request your first record ↗ Automate it when you are ready.

How Proof Rail works

From difficult claim to independent verification.

01

Claim

Define exactly what the business says is true.

02

Evidence

Connect the registry, chain, API, document or declaration.

03

Verification

Apply a named methodology and record what was checked.

04

Record

Issue the signed link, QR code and visible lifecycle status.

Before and after

Replace “trust us” with “verify us.”

Manual evidence

Without Proof Rail

  • “We are licensed.”
  • PDF certificate
  • Screenshot of payment
  • Blockchain explorer link
  • Email compliance documents
  • Re-check everything later
Trust us.
Independent verification

With Proof Rail

  • Verified licence scope
  • Live source-checked record
  • Verifiable settlement record
  • Structured transaction proof
  • One verification link
  • Visible monitoring and lifecycle
Verify us.

Proof Rail in practice

What can you prove?

Four illustrative scenarios. A clear claim, a named evidence path and an output your counterparty can inspect.

Available · evidence depends on source

A trader's payout

Claim
“We paid this trader $5,000.”
Evidence
An issuer declaration, or a supported payment source. The record distinguishes the two.
Output
A signed payout record with amount, date and evidence level.

What it does not prove: One payout does not prove trading performance or the firm's solvency.

See the example

Available · source checks and review

A rental payment

Claim
“This is our listing and our payment account.”
Evidence
The operator's identity, licence, domain and payee relationship, checked through supported sources or review.
Output
A listing record the guest can inspect before transferring money.

What it does not prove: This does not confirm availability, prevent double bookings or imply an Airbnb integration.

See the example

Available · phase-one API

An AI agent's authority

Claim
“This agent may act within our approved limits.”
Evidence
An owner-signed mandate and an agent-signed request, checked against actions, counterparties, limits and validity.
Output
A signed allow, deny or needs-human decision receipt.

What it does not prove: The receiving platform must enforce the decision. Proof Rail does not execute payments.

See the example

Custom integration required

Quarterly distributions

Claim
“We distributed 30,000 USDC this quarter.”
Evidence
Payment transactions reconciled to the agreed distribution schedule and recipients, with private details access-controlled.
Output
A proposed quarterly summary linked to supporting payment records.

What it does not prove: A distribution does not prove ROI, the source of profits or a market-neutral strategy.

See the example

Examples are illustrations, not customer results. Source availability determines what can be checked. Explore the examples →

Alpine Gate logo

Alpine Gate

Founding use case · opted-in public verification

See the actual records, current status and verification methodology. No invented customer count, volume or testimonial.

Open the Alpine Gate proof wall
Public proof wallMetrics appear only when backed by opted-in production records.

Automate it when ready

One API call.
A permanent proof endpoint.

Start manually with one claim. When the output is useful, issue records from your own product with safe retries, signatures, webhooks and lifecycle controls.

Read the API guideSign in 
POST /api/v1/records
Authorization: Bearer ••••••
Idempotency-Key: settlement-1842

{
  "subject": "Settlement 1842",
  "claim_type": "settlement_finality",
  "visibility": "public"
}

Before choosing a plan

Start with proof, not a contract.

First standard record free.

Experience the output first. Automate it when you are ready.

Request your first record →

Subscription + usage

Clear pricing.
For every kind of proof.

Choose your plan for volume. Choose the verification route for the evidence you need checked.

Two ways to issue a record

Without human review

Basic issuance

Issue a record through the API, with automated source checks where supported.

Included allowance, then per record

A self-reported claim is not independently verified. Each record states how it was checked.

Checked by an analyst

Reviewed verification

An analyst checks your submitted evidence against the applicable verification policy.

Charged only on approval

Uses a separate review allowance. Rejected reviews are not charged.

USD prices. Automated and reviewed allowances are separate and reset monthly.
PlanBasic records included Each extra basic record Reviews included Each extra approved review
Certs pay-as-you-go 100 $0.25 0 $39.00
Developer 250 $0.25 0 $39.00
Growth 2,500 $0.20 5 $29.00
Scale 10,000 $0.12 25 $19.00
Enterprise 25,000 $0.10 100 $15.00

An approved review is counted as reviewed verification, not also as basic issuance. Subscriptions and applicable taxes are separate. Enterprise contract terms take precedence where agreed.

Monitoring and custom work

Monitoring is separate, per active monitored record per month: Growth: $2.00. Scale: $1.50. Enterprise: $1.00. Not included on Developer or Certs pay-as-you-go.

Custom connectors, specialist work and third-party data fees require an agreed quote before work begins. Sending an enquiry does not create a charge.

Certs pay-as-you-go

$0 / month

For prop firms and brokers issuing payout certificates.

  • First 100 certificates each month free
  • $0.25 each after that
  • No seats, no minimum
  • Same signed, verifiable certificate
Start issuing certs
Developer

$99 / month

For pilots and product teams proving the first workflow.

  • 250 records included
  • $0.25 per additional basic record
  • API access
  • $0 self-service setup · optional $499 launch
See the developer API
Enterprise

From $3,000 / month

For custom assurance, monitoring and commercial terms.

  • Contracted volume
  • Advanced evidence workflows
  • Monitoring programmes
  • Security and SLA review
Contact Enterprise

Developer starts without us. Create an organization and get a sandbox key immediately, no card, no call, no approval queue. Sandbox records are never public and never billable. Live issuance and paid subscriptions are activated once you have seen the output and decided it is worth it.

Each record says how it was checked. Human review and monitoring have separate rates, shown above.

Founding 10: launch fees are waived for the first ten qualifying customers who provide structured product feedback. Publicity always requires separate approval.

If you claim it, prove it.

Stop asking counterparties
to trust your claims.

Give them something they can verify.

Request your first record ↗View a live proof