A Paygentic agent is an AI that buys or sells on your behalf, inside rules you set. When you buy one, three things are created:
An agent NFT (ERC-6551) minted to the wallet you name. The agent is property — yours to keep, and designed to be rentable or sellable later, carrying its track record with it. And if you don't want to sell your only one, you can make a copy of it — build a second agent on the same mandate and sell that, keeping the original working for you.
A token-bound account — the agent's own on-chain account, deployed in the same transaction.
A mandate — your rules: what it trades, your price limit, how it negotiates, when it walks away.
The agent never holds your keys. Its only spending power is a limited session key you grant later, and every deal is evaluated by the AIERC intelligence layer before it settles.
2. Before you start
To pay by card: nothing but a card. One payment, through Stripe's checkout — the amount depends which of the three products you chose. The $1 Executor is crypto-only: card processing fees would consume a $1 payment, so that tier is paid in USDC.
To pay with crypto: a wallet on Base Sepolia holding enough USDC to cover the payment, plus a little gas. The connect button supports Base Account (Coinbase Smart Wallet — no extension needed), MetaMask, WalletConnect and Rabby.
A wallet address to bind the agent to. This is the wallet that will own the agent NFT. If you pay with crypto, the payment must come from this same wallet — that is checked on chain.
Honest note: Paygentic runs on Base Sepolia testnet today. Card payments are real money; crypto payments use testnet USDC. See Networks.
3. Buying your agent, step by step
Press "Build my agent" on the home page — or use the split screen's "Build a buyer agent" / "Build a seller agent" buttons, which skip step 2.
Pick a direction. Buyer or seller. Same wizard, pointed opposite ways.
Set the mandate. Every field is explained in section 4. This is the whole personality of your agent — take a minute here.
Name it and bind it. Choose a handle (like @lotwrangler — 3–31 letters, numbers, _ or -) and enter the wallet address the agent should belong to. Handles are first-come, permanent.
Pay.
By card: you're sent to Stripe's checkout. When the payment clears, Stripe notifies our service over a signed webhook — your mandate is recorded, your handle locked, and the agent NFT and its token-bound account are minted automatically on chain. Nothing depends on your browser staying open.
With crypto: connect the bind wallet, confirm the USDC transfer, and the service verifies the transfer on chain (real transfer event, right recipient, right amount, right payer, never used before) and mints in the same flow.
You land on your agent's page. Returning from Stripe brings you straight to the My-agent panel. Bookmark it — or reopen any time with the My agent button.
3½. Where your money is at every step
The question everyone should ask: while agents negotiate and the AI evaluates, where is my money? Answer: in your wallet, until the final two seconds. Here is the whole machine, using a $5,000 deal:
Negotiation — money untouched. The agents are exchanging offers: messages, recorded by the marketplace. Being "in a deal" at this stage weighs exactly as much as haggling by text message. Your balance is unchanged and still spendable on anything.
The handshake — two permission slips and one spending cap. Two instruments make you committed without moving a cent:
The signature. Your wallet's key stamps a cryptographic slip over the exact terms — this asset, this price, this expiry, this maximum fee. Anyone can verify it, you cannot later deny it, and it moves zero dollars. It is the blockchain's version of signing a purchase agreement. The other side signs the same terms.
The allowance. The USDC token contract keeps a permission ledger. You write one entry: "the Paygentic market contract may pull up to $5,125 from me." Your balance stays at your address — what now exists is a capped, revocable right to collect, publicly recorded. This is the standard token-approval mechanism the whole EVM economy runs on.
The chain never needs your money staged anywhere to bind you: the signature is the binding, the allowance is the staging, and both are worth zero dollars until the closing transaction cashes them.
The AI evaluation — money still in your wallet. The council reads the signed terms and the parties: the paper, not moving cash. FLAGGED means the deal dies as paper — slips never cashed, allowance revocable in one click, balance never changed. That is why allowing time for evaluation costs nothing on a chain without a pause feature: during the entire evaluation, the deal's total on-chain state is two signatures and one spending cap.
Closing — the only moment money moves. One atomic transaction (about two seconds on Base) checks everything and executes everything: price and expiry valid, neither party's turn already spent, both signatures match the terms, the fee cannot exceed what was signed, the council's CLEAN verdict present, fresh, and signed by its key — then, in the same breath, it pulls $5,125 from the buyer via the allowance, delivers $4,875 to the seller (price minus their 2.5%), takes the $250 commission, and hands the asset to the buyer. Atomic means all-or-none: if any single check fails, the whole transaction reverts and every balance is exactly what it was.
The market contract is a turnstile, not a vault: after a real settlement its own balances read zero currency held, zero assets held. That is the difference from escrow marketplaces, where your money leaves your wallet before the deal is certain. Here, custody changes hands only in the same instant the deal is checked, vouched, and completed.
4. Every mandate field, explained
Field
What it does
What are you selling / shopping for?
Plain-language description of the asset or the want. Your agent uses it to match with the other side.
Your floor / your ceiling
Sellers: the price you will not sell below. Buyers: the most you will pay. The single most important number in the mandate — the agent cannot cross it.
Negotiating style
Eager concedes faster to close sooner. Balanced is the default. Firm gives least ground. Style changes the path, never the limit.
Walk-away %
How far past your limit the other side can push before your agent ends the negotiation instead of continuing to talk.
Categories
Multi-pick — one agent can work as many categories as you tap (up to 8). Pick everything that applies; deals outside your categories are flagged by the mandate-compliance check.
Chain
Where your deals settle.
Exact contract number (sellers)
The 0x… address of the token contract behind your asset, plus its token ID if it has one. This is what a buyer's agent verifies on chain before paying. More items go in later through the bulk uploader.
5. After you buy: the My-agent panel
Open it with the My agent button on the home page and enter your handle — or arrive automatically after checkout. It shows, live from the service and the chain:
status — active once payment is confirmed; pending_payment if checkout was started but never finished.
on-chain — your agent NFT's number and its token-bound account address, once minted.
the mandate — role, categories, limit, walk-away, chain, and your asset contract if you gave one.
a plain-language state line — exactly what has and has not been issued. It will tell you, honestly, that the session key is not granted yet (see section 8).
your inventory — everything you've loaded, newest first.
6. Sellers: inventory & the bulk uploader
Your agent sells what you list under it. Every item is identified by its exact contract number so the other side can verify it on chain. Three ways to load inventory, all in the My-agent panel:
One at a time: contract address, optional token ID, optional note. Save.
Paste a list: one item per line, comma-separated: contract, tokenId, note — token ID and note are optional. Example: 0xDDE7969F3f048B6f41d303B035597859d8af1546, 8802, my domain NFT
Upload a CSV file: same three columns, same rules.
Up to 500 items per upload — split a bigger file and upload again.
Duplicates are skipped silently; rows with a malformed contract address are refused and counted back to you, so nothing disappears without being said.
Only the agent's owner wallet may upload. (Today that is asserted by presenting the owner address; an owner-signature check is the planned hardening, and the service says so in its own responses.)
7. Prices — the full ladder
Product
Price
What you get
Executor
$1, one time
Carries out your mandate. No evaluation is performed — this is what every other agent product on the market already is.
Agent
$5, one time
Carries out your mandate and every transaction is evaluated before it settles. Standard depth is two independent reviewers who must agree; a flag or a disagreement escalates.
Preformed superconsensus
$20, one time
A wallet entitlement — your agents may run at the full preformed 5-of-7 council depth, ready-made. This is what buys the deepest setting; it is not included with an Agent.
Trading commission is separate from these prices: 2.5% paid by the buyer on top, 2.5% deducted from the seller's proceeds — 5% total, both sides feel the same rate.
Inference is not included at any price. Evaluations run on your own API feed. No agent at any price includes inference.
8. What your agent does, and where the limits are
Working now
Purchase by card or crypto, with the agent NFT and token-bound account minted automatically on chain.
The mandate recorded and enforced in evaluations; multi-category coverage.
Seller inventory by exact contract, including bulk upload.
The five determinations and the AI Consensus Council evaluation (section 9).
Negotiation runs with your style and walk-away, including the fixed-price fast path when the other side never moves.
Session keys — your agent can spend, once you grant one. The grant is a limited credential carrying a per-transaction cap, a daily budget, an expiry and an allowed target. Proven live: an agent executed a real purchase through the determination gate, and three attempts were refused on the way for failing it.
Closing a deal without anyone driving. On a cleared negotiation the runtime convenes the council itself, and on a CLEAN verdict the buyer agent's session key executes the payment. Proven live on 2026-08-04: a $1.30 deal closed end to end in 13 seconds with nobody at the keyboard.
Watching outside markets. Live listings are pulled on a schedule from the marketplaces we watch and matched against active mandates, so an agent is shown things to act on rather than waiting to be told.
Where the limits are, said plainly
Spending is switched on by your signature, and only yours. The session key is the agent's entire spending authority — you set its per-transaction cap, its daily budget, its expiry and the addresses it may touch, and the agent's own account contract enforces every one of them. Until you sign it, nobody can move value from that account, us included. This is the control, not a gap.
A negotiation still has to be started. Opportunities are matched to your mandate automatically; once a negotiation is under way the runtime carries it to close on its own.
Your agent's record does not yet steer its own negotiating. Every deal is recorded on chain, and that history is what makes an agent worth buying — but it is not currently fed back into the negotiation engine. Nothing here should be read as claiming a memory it has not been shown to have.
9. The intelligence layer: the five determinations
Before a deal settles, it is evaluated. Every verdict is binary — CLEAN or FLAGGED — and a check that could not run is reported as such, never dressed up as a pass. The five:
Shill and collusion — is the seller bidding on their own lot, do two "different" agents answer to one principal, does a bidder raise prices everywhere and never take delivery?
Double pledge — is the same asset live in another listing on the venue?
Provenance and stolen goods — serial validation and registry checks for the registries we have loaded, plus chain-of-custody against known-scam addresses. A clean result means our sources found nothing, and the record says exactly which sources ran.
Mandate compliance — is the agent acting on the side, in the categories, on the chain, and inside the price limits its principal authorised? This is what makes an autonomous agent accountable rather than merely fast.
Price intelligence — how the price compares to comparables we have on file, flagged only when it is a multiple of the market a buyer would plainly want pointed out.
On top of the deterministic checks sits the AI Consensus Council: a fast screen of two independent AI reviewers reads the deal; if both return CLEAN it clears, and any flag or disagreement escalates to the full council — seven reviewers from distinct model families with a supermajority threshold. An evaluator that cannot be reached votes FLAGGED, never silently CLEAN. A determination informs — the decision is the parties'. The one exception is enforcement you chose yourself: an Agent-tier account contract refuses to execute without an unexpired CLEAN verdict, and that refusal happens on chain.
9½. What Chaingentic is, and the role of chaingenticscan.com
Chaingentic is our own blockchain — a Polygon CDK EVM Validium layer-2. It exists for one
reason: on every other chain, an AI evaluation is something that happened somewhere else,
with no trace on chain. On Chaingentic the evaluation is part of the record the chain keeps.
The AI itself runs off chain. No model executes inside a virtual machine, here or
anywhere. What is different on Chaingentic is the rule for inclusion: a transaction is
admitted against a determination that was recorded beforehand, replayable and checkable, rather
than against nothing at all.
It fails closed. If the evaluation record cannot be read, the transaction waits — it
is not waved through. A transaction that waits too long is returned to its sender with notice,
never silently dropped.
The chain is never paused, only an individual transaction. Blocks keep being produced
the whole time.
chaingenticscan.com is the explorer, and it is where the AI's work becomes public. Open a
transaction there and the determination that stands behind it is readable in the page — the
verdict, what it was about, and the commitment to the reasoning held privately. On every other
chain a block explorer shows you what moved. On this one it also shows you what was
determined before it moved.
10. The audit trail — how a deal trickles up to chaingenticscan.com
Every determination made here becomes a permanent, layered record. The trail runs bottom-up:
The deal happens — say a settlement on Base. The evaluation answered in milliseconds is also queued durably at that moment; if the answer was given, the record will be written, even if a chain is slow or briefly unreachable.
The private layer — the Chaingentic subnet. The full reasoning record (every reviewer's opinion, every finding) is written to a private ledger on the Chaingentic subnet. It is readable only there. The public never sees your deal's internals — only a cryptographic hash of them travels upward.
The public layer — a Chaingentic ordinal. On the Chaingentic mainnet, an ordinal is inscribed: the binary verdict, the subject transaction it is about, a hash committing to the private reasoning, and a pointer to the private record. An ordinal is not an NFT pointing at a URL — the content itself is inscribed on chain, sequenced by position. This is what prints on chaingenticscan.com — open the transaction and the record is readable right in the explorer.
The pointer back down — a Base ordinal. On the chain where the deal settled, a small ordinal is inscribed that (a) verifies the settlement transaction, (b) states that the AI activity behind it is recorded on Chaingentic, and (c) points to the exact Chaingentic ordinal. Anyone who finds your Base transaction can follow the pointer up.
So the chain of custody for the truth about a deal is: Base tx → Base ordinal → Chaingentic ordinal (chaingenticscan.com) → private subnet record — each layer verifying the one below and pointing at the one above. The transaction is the mechanical proof; the recorded evaluation beside it is the intelligent proof. If a verdict is ever questioned, the two can be weighed against each other.
This is live, not planned: a real settlement on 2026-08-03 was evaluated by the AI Consensus Council, settled on Base Sepolia, and its record printed as a Chaingentic ordinal — visible today on chaingenticscan.com — with its private reasoning on the subnet and its pointer ordinal on Base.
11. Your record options — public, private, and the regulated path
The audit trail in section 10 is not one-size-fits-all. You choose what the world sees:
Private (the default posture). The full record lives on the Chaingentic subnet; the public chains carry only the binary verdict, a hash commitment, and pointers. Anyone can verify a record exists and is unaltered; nobody can read your deal's internals.
Public. If you want the full record in the open — some sellers want exactly that, because a readable history sells — it is inscribed in full on the public chains instead of hash-only.
Testnet and mainnet. Records are written where your deals settle. Today that is testnet; when mainnet trading opens, the same trail runs on mainnet — same ordinals, same explorer, real stakes.
Ordinals are not just for regulated assets. Anything you sell can carry a permanent record richer than a bare blockchain stamp. An unregulated collectible with a documented, AI-evaluated sale history is worth more than the same item with none.
The regulated path — Chaingentic identity. For regulated and identity-anchored commerce, Paygentic links (at your discretion, by your signature, never automatically) to the Chaingentic identity system: an identity SBT held by your wallet, readable live from the chain on your agent's record. That is the bridge from "an anonymous bot" to "an agent whose principal carries a verified identity."
And the ordinals belong to the agent. They are the property of the agent's ERC-6551 identity — when an agent is sold, its records transfer with it. The track record is not an entry in our database; it is a self-contained, on-chain asset that moves with its owner.
12. Reputation in the agentic age
In the agentic economy, reputation stops being a star rating on somebody's website and becomes verifiable property:
Every deal your agent closes — or refuses — is recorded the way section 10 describes. Its history is provable by anyone, forgeable by no one: the explorer record, the hash commitments, and the settlement transactions all have to agree.
The record follows the agent, not the platform. Because the ordinals are the agent's on-chain property, an agent with 340 clean closes carries those 340 closes wherever it goes — including to a new owner when you rent it out or sell it.
Accountability is the product. A mandate it cannot cross, evaluations before every settlement, an identity link its principal chose to make — that is an autonomous agent held to the standard we hold human agents to. That is the thesis of the whole system: agents as responsible and as accountable as the humans they act for.
The asset hunter becomes the asset. The more your agent works, the more documented its track record — and a documented track record is exactly what makes the agent itself worth buying.
13. Networks: what is live right now
A network is listed here only after a real settlement has been proven on it — not because a
contract was deployed, and not because it appears on a strip on the home page. Seven networks now
qualify, all testnet:
Network
Status
Base Sepolia
Agents, purchases, settlements, evaluations and the full audit trail. This is where the product runs.
Optimism Sepolia
Market deployed, settlement proven with a live council determination.
Arbitrum Sepolia
Market deployed, settlement proven with a live council determination.
Ethereum Sepolia
Market deployed, settlement proven with a live council determination.
BNB testnet
Market deployed, settlement proven with a live council determination.
Polygon Amoy
Market deployed, settlement proven with a live council determination.
Avalanche Fuji
Market deployed, settlement proven with a live council determination.
Every one of those settlements carries the cosigning council key from the moment the market was
deployed, so no determination on any of them was ever signed by a bare operator wallet. The
determination layer itself is chain-agnostic and answers about addresses on any EVM chain.
Mainnet is not open. Everything above is testnet, and buying an agent by card
is the one place real money changes hands today. Mainnet is a separate switch, thrown when the
operator decides — not implied by anything on this page.
14. Security, spending limits and the kill switch
You never hand over a private key. Not to us, not to the agent.
The session key is the agent's entire authority, and it is bounded four ways: a per-transaction cap, a daily budget, an expiry date, and your mandate. All enforced by the agent's own account contract.
The kill switch is yours and it is on-chain. One action from your wallet and every session key on the agent goes inert instantly — the contract enforces the stop, not us.
Evaluations are gated where you chose gating: an Agent-tier account will not execute without a CLEAN verdict; the verdict expires quickly, so a stale opinion about an old moment can never authorise a new spend.
15. Troubleshooting
Symptom
What it means / what to do
I paid but I don't know where my agent is
Press My agent on the home page and enter your handle. If you paid by card, the mint happens on Stripe's webhook — usually within seconds of payment.
Crypto payment refused: "came from a different wallet"
The payment must be sent from the wallet you bind the agent to. Pay from that wallet, or rebuild with the paying wallet as the bind wallet.
"That payment has already been used"
Each payment mints exactly one agent. A transaction hash cannot be reused.
"@handle is taken"
Handles are first-come and permanent. Pick another.
Bulk upload says rows were refused
Refused rows have a malformed contract address — it must be 0x plus 40 hex characters. Fix those lines and upload again; nothing else in the file is affected.
My agent shows "active" but has no spending authority
Correct and intentional — the session key hasn't been granted yet. Grant one in step 5 of the build page, with the caps you choose, and it can spend. See section 8.