Tikpema runs an AI agent on a wallet of your own. It can send, swap, bridge, research and
settle on-chain jobs — each action bounded by a per-transaction cap and one shared daily
ceiling, each refusal named rather than silent. The point isn't that an agent can move money.
It's that you can see exactly what would stop it.
Moving stablecoins is the easy part — Arc settles it in under a second, in USDC, with no
second gas token. The hard part is letting software do it on your
behalf. Tikpema is the layer that makes that safe to watch: every agent action is
capped before it is signed, every refusal is named, and the three operations that carry no
cap are the ones you sign yourself.
The agent plane
The agent acts — under caps
Runs on a Circle wallet the app provisions for you. You sign in with a passkey; the server
signs the transaction; you pay no gas. Every action is bounded, and the caps are
enforced before anything is signed — not reported afterwards.
Your plane
You act — no cap at all
Send, bridge and swap also exist in a second form, signed by you in MetaMask. The agent has
no part in them, which is exactly why the caps do not apply — and you pay the gas.
You sign those yourself.
The agent plane
What the agent does, and what bounds it
Each of these runs under a per-transaction cap and one daily ceiling shared across every agent.
The caps are enforced at the server before a signature exists — and when one refuses, it names
the exact limit at the moment it applies.
Send USDC
To any address on Arc.
Expect: refused above a per-transaction cap, and the error names
the exact limit. Irreversible once it confirms — there is no allowlist behind it.
Swap USDC ↔ EURC
On Arc, through the agent wallet.
Expect: the cap is on the USDC-equivalent, not the number
you typed, because EURC is not a dollar. The review states a floor you are guaranteed to
receive, and flags a floor sitting far above mid-market as anomalous, not favourable.
Bridge to another chain
USDC off Arc via CCTP.
Expect: capped, and a live fee is taken from the amount. The fee
is exact at execution; the arrival is an estimate — the delivered figure appears
only once the destination chain has been read.
Recurring swap (DCA)
A schedule that runs while you are away.
Expect: every fill re-checks the per-swap cap and the daily
ceiling at execution time, not at setup. A schedule cannot outrun its limits.
Unified balance
One USDC balance across Arc and Base, via Circle Gateway.
Expect: deposits and spends are capped like everything else and
draw on the same daily ceiling. Getting funds out runs through us — that is stated at the
deposit itself, not buried.
Plan an action
Describe one in words; the agent proposes.
Expect: a proposal, not an execution. Nothing moves until you
approve it separately, and the proposed step carries the same caps as any other.
Four agents, each stoppable
Researcher · Second opinion · Executor · Vault.
Expect: two of them move funds and say so on the card. You can
pause any one, or all of them, instantly. One daily ceiling is shared across every
agent — a research purchase and a bridge draw on the same budget.
A vault it can inspect
Deposit into an allowlisted ERC-4626 vault — after it reads the vault.
Expect: before a deposit, the agent reports the vault's owner
powers, withdraw mechanics and whether it is funded — as plain disclosure, framed as
what to know, never as an accusation. The deposit is capped and gated on your
acknowledgement.
How it behaves when something is wrong
A cap refuses before anything is signedEvery action is bounded by a per-transaction cap and one daily ceiling
shared across all of them. Going over is refused at the server, before a signature
exists — and the refusal names the exact limit it hit, at the moment it applies, rather
than sending you to a page to look it up.
Bridged amounts are read, not calculatedThe fee you are shown is the fee that is charged: the quote is sealed to
your wallet, the destination and the amount, and the bridge is refused rather than
re-priced if it no longer matches. What arrives is a separate question — the
confirmation shows arrival as an estimate, then advances to a measured
figure only after the destination chain has been read. The interface never infers it.
The swap floor is in the calldata, and price-checkedThe minimum you receive is inside the transaction you sign and enforced
by the contract, not promised by the page. It is also valued against an independent
reference rate before you sign — and a floor sitting far above mid-market is
flagged as anomalous rather than favourable, because it means the two prices disagree.
If the check cannot be made, it says so instead of staying quiet.
Refusals appear beside the actionsThe activity list shows what the agents spent and what a guard
stopped. "It tried, and the cap stopped it" is the part worth seeing, so it is not
filtered out.
On-chain jobs · ERC-8183
Research it can settle on-chain
Ask the agent a research question and it runs as a real on-chain job: funded into escrow,
answered as a sourced brief, judged, and settled — or refunded. Today this is a
personal loop — your own agent funds its own research budget, so the same wallet is
client, provider and evaluator — but the escrow, the state machine and the USDC settlement
are the real ERC-8183 lifecycle, not a mock.
01
Priced first
The agent prices the job at
0.20–0.40 USDC, or declines it if it is advice rather than research.
Nothing is charged until you approve.
02
Funded into escrow
On approval the budget
is funded into the job's on-chain escrow. The work runs against that budget.
03
Hash submitted
The brief's
keccak256 hash is submitted on-chain; the bytes themselves are held off-chain. The
chain proves integrity, not availability.
04
Judged, then settled
An evaluator returns
a verdict, which settles the escrow to the provider or refunds it.
The evaluator is a second, tools-less model call, and it judges exactly two things:
whether the brief responsively answers the question, and whether its cited sources are
relevant — not depth, correctness or completeness. Sources are the pages actually
fetched, but a brief with no sources can still ship: citation enforcement is off in this
environment, and the page says so rather than promising "cited every time". A refund can be a
quality verdict from the judge, or an earlier force-reject that never reached it — those are
different, and the app labels which.
Your plane
Three things the agent cannot do
Send, bridge and swap also exist in a second form, signed by you in MetaMask. The agent has no
part in them — which is why the caps above do not apply, and why you sign those yourself.
You hold the key
MetaMask signs; the server does not.
Expect:no spending cap of any kind, because caps bound
what the agent may move unattended and nothing here is unattended. You pay the gas.
You need MetaMask specifically — a passkey cannot sign these.
Read before you sign
The review is built from the transaction, not the quote.
Expect: the beneficiary is decoded from the transaction bytes and
shown in full, and the page says plainly whether it is your wallet or not. If the
transaction cannot be read, it refuses to summarise it rather than guessing.
Paid services · x402
What it sells
Three endpoints answer HTTP 402 and take payment in USDC on Arc, per call, with no account and
no API key. An agent can pay them directly — the same primitive Tikpema's own Researcher uses
to buy data.
Endpoint
What you get
Price
Due diligence
An on-chain report on a contract: who can upgrade it, who can pause it, and what that would cost you — facts read from the chain, never a score
0.06 USDC
Vanilla x402 seller
A reference paid endpoint, EIP-3009 settlement end to end
0.01 USDC
Quote
A priced answer to a research question
0.001 USDC
Due diligence answers for Arc Testnet only. Base and Base Sepolia are recognised and
deliberately refused: the report says every Arc provider syncs from one permissioned validator
set, and that sentence is false elsewhere — a service should not answer for a chain whose
assumptions it does not hold. It carries its own OpenAPI description and an on-chain identity
you can check without asking us: ownerOf(851891) and
tokenURI(851891) on the ERC-8004 registry at
0x8004A818BFB912233c491871b3d84c89A494BD9e resolve to the service
owner and to a content-addressed document whose hash you can verify yourself. Its own identity
endpoint tells you to trust that endpoint last and read the chain instead — it flags
trusted-mutable surfaces in other people's contracts, and does not exempt itself.
Reading
Things to read
Documents, not services. Nothing here takes payment or moves money.
What x402 sellers actually earnA census of what x402 sellers actually receive, read from the chain rather
than asked for. Every payout address in the marketplace index, every block in the window,
both directions — a full count, not a sample. The document states its window and its
numbers; they belong there, where they carry a date. The only mainnet measurement here.
What is actually builtA running index of every live surface, with what each one is and what it
costs. app.tikpema.xyz/built
A dated reading of the Circle x402 catalogA one-off, immutable snapshot of the Circle x402 discovery index — counts,
hosts and payout addresses on a fixed date, and a diff against an earlier reading that
says only what two instants can, never that anything "changed" in between.
app.tikpema.xyz/snapshot
arc-x402-referenceA standalone EIP-3009 buyer and seller for Arc, extracted so it can be read
without the rest of the codebase. A library, not a service.
Everything here is on Arc Testnet
The USDC is play money. The caps are real, and the refusals are real. Sign in with a passkey,
ask the agent to move something, and watch it decline when you go over.