Access0x1 · the company

Commerce with its promises enforced in code.

We are the company behind the open-source rail for onchain identity and USD-priced payments in USDC. Everything we build passes one test: the guarantee must live in the contract — not in our goodwill, our uptime, or our terms of service.

access0x1.com

The company. Private, opinionated, accountable for the vision on this page. This site is our word.

access0x1.click

The product — the open-source rail itself. Onboard, get a branded checkout link, and use the contracts directly. Runs on test networks today; mainnet is gated on audit. Open it →

What we’re building

Six products. One bar: the rule lives in a published contract you can inspect and call yourself — not in a policy you have to take on trust.

  1. 01

    The refund a merchant can't withhold

    Once a refund is authorized, claiming it is a call, not a request.

    A merchant funds and authorizes a refund on-chain, and the contract holds that amount from the moment it is funded. The customer then claims it directly against the published contract — there is no Access0x1 server in the claim path to approve, delay, or reverse it. A hosted processor can approve a refund and still sit on the payout; once funded here, the claim is the customer's to make inside the refund window. What the contract does not do is force a merchant to offer a refund in the first place — that stays the merchant's decision — and access still depends on the network, wallet, and settlement asset in use.

  2. 02

    One human, one X

    Commerce that can prove a person, not a bot.

    A discount each human can claim exactly once across every merchant on the rail. Reviews that are provably written by a unique human who provably paid — the receipt is on-chain. Fair-queue ticket drops where a second entry costs a second proof of personhood, so scripting one wallet into a thousand stops paying. It takes zero-knowledge proof of personhood joined to a payment record, and that join only exists here.

  3. 03

    The Unruggable Ticket

    The rules live inside the ticket, not in our terms of service.

    A ticket whose resale price cap, organizer royalty, and automatic refund-if-cancelled live inside the asset itself — and the only market it trades on enforces those rules at swap time. Scalpers can't scalp and venues can't rug, because those rules are fixed in the ticket's own contract at mint rather than in a policy page — and shipping it means freezing that contract's upgrade path first. Property rights and market rules fused into the object.

  4. 04

    The Immortal Business

    A treasury with succession built in.

    A merchant whose treasury streams payroll and pays suppliers on its own. If the owner's heartbeat stops — no signed check-in — the contract executes succession: funds stream to heirs and staff on a schedule. No probate and no custodian in the loop — the schedule runs from the contract, not from an office that can close.

  5. 05

    Pay-per-second work

    Earnings that accrue by the second and settle once.

    Wages or usage metered off-chain per second with cryptographic finality, settled on-chain in a single transaction. Self-custody payroll with no processor in the loop — micro-granularity economics that card rails cannot express.

  6. 06

    The AI that owns itself

    An economic organism, not a SaaS.

    An agent with its own wallet: it earns fees on the rail, pays for its own inference and storage, and renews its own existence through decentralized automation. It is not an employee to fire or a subscription to cancel — it keeps running as long as it can pay its own bills.

The “never taken down” recipe

Every product above has to clear the same bar before we ship it. This is the requirement, not a description of what is already live — today’s testnet contracts are still upgradeable by their deployer:

  • Frozen contracts — no live upgrade path; ownership renounced or held by a timelock.
  • Frontend on IPFS + ENS — no host to seize, no DNS to hijack.
  • Permissionless indexing — anyone can rebuild the history from the chain.
  • Receipts and documents anchored on public networks — provable forever.

The bar: you shouldn't have to trust us.