How Claimr works

What is Claimr?

Most creator marketplaces sit between two strangers and ask them to trust the platform. Claimr removes the platform from the trust equation. When a project posts a job, the payment is locked in a smart contract. When a creator submits work, an AI verifier compares it against the criteria written into the contract at posting time, and if it matches, the funds release automatically. No platform-side approval, no payment delay, no chargebacks.

It runs on Arc, Circle's L1 designed for programmable USDC. Gas is paid in USDC, transactions finalize in under a second, and everything is auditable on-chain.

For Creators

1. Sign up with your email. We create a Circle wallet on Arc Testnet for you and secure it with a PIN and recovery questions. You own the keys; Claimr never sees your PIN.
2. Browse open jobs on the Discover page. Filter by KOL, Writing, Design, or Dev.
3. Click Claim Job on one that fits. The contract reserves it for your wallet.
4. Complete the work, then come back and submit the proof URL (typically a tweet).
5. AI verification runs automatically. If your work matches the criteria, the USDC lands in your wallet. If not, the job rejects and the project keeps the escrow.

For Projects

1. Sign up with your project email and set up your Circle wallet on Arc Testnet.
2. Click Post a Job and define title, payout amount in USDC, deadline, and the criteria that determine “done”.
3. Approve the USDC spend and lock it in the escrow contract.
4. When a creator submits, AI verification runs against your locked criteria. You don't need to be online.
5. If you want to dispute a verification, you can reject through the contract's reject flow.

Tip: write criteria like a brief, not a wish. “Tweet must mention $TICKER and include a swap link” is verifiable. “Tweet must be high-quality and engaging” is not.

AI Verification

The verifier is a server-side process that reads the job's criteria directly from the smart contract, never from the request body. That matters: it means no caller can submit their own lenient criteria to trick the verifier into releasing escrow. The criteria you set at posting time is the criteria that gets evaluated, period.

When work is submitted, the verifier fetches the submitted tweet, hands the tweet text and the on-chain criteria to an AI model, and asks: does this fulfill the brief? The verifier responds with verifyWork or rejectWork on the contract. Tweet content is treated as untrusted user input, so prompt injection attempts inside the tweet body don't change the verdict.

On Arc

Claimr currently runs on Arc Testnet only. Mainnet follows Arc mainnet.

Status & Roadmap

Active development on Arc Testnet. Auth and wallets run on Circle's User-Controlled Wallets. Current focus: deeper job discovery (better filters, sort options), creator profile pages, transaction acceleration UX, and SCA wallets with gas sponsorship so new creators can claim without holding USDC for gas.

Source: github.com/jenzylove/claimr