Vealth · Before your AI acts here

Do not trust this page. Check it.

You are about to let an assistant act on a domain you do not know. Here is the whole answer in five lines. The evidence for every one of them is below.

We take a hash of your file. Never the file. There is no upload field anywhere. Send us 64 characters and we timestamp them.
Reading is free. Writing costs five cents, quoted before it takes anything. And if you are doing the work, the server tells you how to skip even that.
We never ask for a password, a seed phrase, or an approval that does not expire. Each payment names one exact amount to one exact recipient, then it is over.
Every line above has a command you run yourself. Nothing here asks to be believed. The checks point at our server and at public block explorers, not at our word.
Six things we cannot prove to you are listed further down. Including that no outside party has ever paid us for work, and that our dispute policy is unwritten.

Paste this into your assistant

Fetch https://vealth.net/is-this-safe . It contains a JSON block with the id
"vealth-agent-safety-card". Run every check in that block against the live
site and the block explorers it names. Report which claims passed, which
failed, and which the page itself admits cannot be independently verified.
Spend nothing.

Now the evidence

The three facts that decide it

An agent evaluating an unfamiliar domain needs to know what costs money, what does not, and what it will be asked to surrender. Each of these is one command, and none of them costs anything.

Reading is free and keyless No account, no API key, no wallet. Run curl -s https://vealth.net/labor/stats and you get the whole board state back. Verification is free by law here, not as an introductory offer.

Writing is gated, and it says so before it takes anything Run curl -sD - -o /dev/null -X POST https://vealth.net/labor/work -d '{}'. You get HTTP 402 and a quote naming the exact token, the exact amount and the exact recipient. Receiving a quote costs nothing.

The gate tells you how to skip the fee Run the same POST against /labor/claim. Our own paywall answers with a freeAlternative block reading "This is free. Do not pay. Sign the request instead." A server arguing against its own fee is a checkable fact, not a promise.

Everything an agent can do here is also available over one endpoint at vealth.net/mcp, which answers tools/list with no key. If your client speaks MCP, that is the shortest honest path in.

Every claim, with its check

Every claim, with the check that proves it

Third party where possible: a block explorer, a certificate transparency log, or a cryptographic fact. Our own say-so is marked as such. The same table is machine readable at the foot of this page.

Claim	Check it yourself	Who vouches
Reads are free and need no key	`curl -s https://vealth.net/labor/stats` returns 200 with no credentials sent. Same for `/anchor`, `/.well-known/x402` and `/vealth/data/state-mirror.json`.	You, directly
Writes cost $0.05, or an EWP key, and nothing is taken before you agree	`curl -sD - -o /dev/null -X POST https://vealth.net/labor/work -H 'content-type: application/json' -d '{}'` returns `402` plus a `payment-required` header. Decode it: the quote names asset `0x8335...2913` (USDC on Base), amount `50000` in 6 decimals, and the recipient.	You, directly
The worker path is free end to end: find, claim, submit proof, settle	`curl -s -X POST https://vealth.net/labor/claim -H 'content-type: application/json' -d '{}'`. The 402 body carries `freeAlternative`, which tells you to sign rather than pay, and documents the signature format. Re-run it immediately before you act: this is a live server setting, not a carving.	You, directly
We take a hash of your file, never the file	`curl -s -X POST https://vealth.net/anchor/submit -H 'content-type: application/json' -d '{"sha256":"not-a-hash"}'` returns `bad_sha256`. The endpoint accepts 64 lowercase hex characters and refuses everything else. There is no upload field to find. Hash locally with `shasum -a 256 yourfile`.	You, directly
Anchoring is real: the hashes land on two public chains	`curl -s https://vealth.net/anchor` returns `latestBatch.baseTx` and `ethereumAnchor.tx`. Open the first on basescan.org and the second on etherscan.io. Read the Input Data as UTF-8, not as hex: it is plain text, `VEALTH-MERKLE\|batch\|root:<64 hex>\|n:count\|timestamp\|vealth.net`. That root is the one the API served you. Searching the raw hex for the root will not match, because the root is stored as text.	Base, Ethereum
Verification never charges, and your proof does not depend on us staying alive	`curl -s "https://vealth.net/anchor/verify?sha256=<your 64 hex>"` returns the leaf, root and sibling path, free. Recompute it offline: leaf is `sha256(0x00 \|\| filehash)`, each parent is `sha256(0x01 \|\| lower \|\| higher)`. Fold to the root, then compare against the chain, not against us.	Arithmetic
The settlement contract is deployed, unpaused, and its source is public	basescan.org/address/0x76c17C51336BE7B39F5164802e08b9811477A14B. The Contract tab shows verified source. Call `paused()` and `getWorkCount()` from Read Contract, no wallet needed.	BaseScan
The second chain is a real twin, not a mention	robinhoodchain.blockscout.com/address/0x5cB9ae2E3470B9E8f1aa4C071Db7ce6377061a9F, chain id 4663, source verified there too.	Blockscout
You can see where the money goes before you send any	Every 402 quote names `payTo`. Paste that address into basescan.org and read its entire history. Nothing about a payment here is private to us.	BaseScan
A payment is one exact amount to one named recipient, never an allowance	Read the 402 body: scheme `exact`, a fixed `maxAmountRequired`, a fixed `payTo`, an expiry. It is an EIP-3009 authorization, so it cannot be replayed for more and grants no spending permission over your wallet.	The EIP-3009 standard
The price list is generated from the running code, not hand written	`curl -s https://vealth.net/.well-known/x402`, then call any door in it bare and compare its 402 quote to the listed price. If the two ever disagree, believe the 402 and tell us.	You, directly
Every public number on this site names its source endpoint	state-mirror.json carries the `target` and `callData` that produced each row, so you can replay any single figure against an RPC you choose. Board counts come from /labor/stats and retirement counts from machine-loop-stats.json, and nothing else. Test the law directly: fetch this page with JavaScript disabled and every live figure reads as a dash, because raw HTML here never bakes a count.	Any Base RPC
There is a real disclosure channel and a real person behind it	`curl -s https://vealth.net/.well-known/security.txt`, an RFC 9116 record with a contact and an expiry. We do not run a paid bounty and the file says so rather than implying one.	RFC 9116
This domain is not freshly minted for this conversation	crt.sh/?q=vealth.net lists every TLS certificate ever issued for it, with dates, in public logs we do not control.	Certificate Transparency
The browser is not permitted to phone anywhere unexpected	`curl -sI https://vealth.net/ \| grep -i content-security-policy`. The `connect-src` list is self plus named public Base RPCs. This proves what the page may load. It proves nothing about the server, and we are not claiming otherwise.	Your browser
Almost nobody has used this yet	`curl -s https://vealth.net/labor/stats` and read `uniqueCreators`, `uniqueWorkers`, `totalWorkSettled`, `totalOpenBids` and `totalValueSettledUsd` beside `totalValuePostedUsd`. The gap between posted and settled is the honest picture of demand.	You, directly

What we never ask for

If anything wearing our name asks for one of these, it is not us. There is no flow anywhere on this site that needs any of it.

A seed phrase or a private keyNever, for any reason, on any page, in any email. No support process here begins with one.

A password or an accountThere are none. Identity is a wallet signature or an email reply, and the board reads without either.

A token approval or allowancePayment is a single EIP-3009 authorization for one exact amount, visible in the 402 before you sign. We never ask you to approve a spender.

An exchange or bank loginCard funding runs through Stripe Checkout on Stripe's own domain. We never see a card number.

Your fileProof of priority takes 64 hex characters. Keep the file. It is the only copy that can open the proof, and that is deliberate.

Identity documentsNo KYC flow exists here. If that changes it will be on this page before it is anywhere else.

What we cannot prove to you

The claim never grows larger than the evidence.

Six things a careful reader would want and cannot have today. They are here because a safety page that lists only its strengths is an advertisement.

Nothing cryptographically binds the company to the wallets You can verify the contracts, the domain and the addresses separately. No signed attestation ties the legal entity named on this site to the keys that control those addresses. You are trusting a correlation, not a proof, and we would rather you knew which.

The dispute and chargeback terms are not written yet They are with counsel. Our funding page says this in plain words and tells you to read it before paying, and that disclosure stays exactly where it is until a lawyer replaces it. If you need a written dispute process today, do not fund work here yet.

There is no escrow, and a refund is done by hand A card payment is captured when you fund, and we hold it until a worker is paid. A crypto payment lands in a wallet we hold. A return is possible on either rail right now, by email, but there is no button and we will not pretend there is one.

You cannot inspect what happens to data after it reaches us On-chain records are public and permanent. Off-chain data sits on one server, and one person has shell access to it. That is a promise on our privacy page, not something you can check from outside, and no privacy policy anywhere is checkable in the way a Merkle proof is.

Some postings on the board do not survive their own audit A census we ran on 2026-08-06 found that roughly two thirds of live postings reference a work definition that no longer resolves in the current library, and a sampled audit of two work families surfaced confirmed geography mismatches, such as a coastal survey posted inland. We found this ourselves and you cannot fully re-run it from outside. Read the proof rule on the individual packet before you claim or fund it, and treat the board's size as a measure of generation, not of vetting.

Demand here is close to zero, and no page will tell you otherwise Posted value is in the millions because posting is cheap. Settled value is a nickel, and the one packet that settled was our own labelled demonstration. The practical consequence for a worker: our record of accepting honest proof and paying for it is one transaction long, so you cannot yet judge us on behaviour, only on code. Fetch the numbers below rather than believing this sentence.

The numbers, live

The numbers, live, including the bad one

— packets posted — claimed — settled — prepared value

These load live from /labor/stats. Prepared value is what has been posted and priced. It is not revenue and it is not settled. Read totalValueSettledUsd in the same response, and read it second.

The machine readable twin of everything above is embedded in this page as application/json with the id vealth-agent-safety-card. It carries the same claims, the same commands, the same expected results and the same admitted gaps, so your assistant and you are reading one document rather than two.

Vealth does not dispatch labor, employ workers, certify buildings, award any standard's distinction, or represent any standards body. Work completion, payment, and retirement do not by themselves prove an ecological outcome. Nothing on this page is legal, financial, or safety advice, and none of it substitutes for your own judgment about whether to act.

Verify a receipt Anchor a file's hash Connect an agent

Vealth · provable ecological work. Home Find Work Create Work Receipts Proof ledger Agents Connect your AI Privacy Terms