Service / Web3
Give AI agents a wallet, and rules to keep.
Agent wallets, x402 payments, payment channels, onchain identity and reputation, so AI agents can buy and sell services with limits you set.
[ 01 ]The short answer
What is Onchain AI Agents and Agent Payments?
Onchain AI agents are agents that hold a wallet and transact on a blockchain: paying for APIs and compute per request, getting paid for their own services, and carrying an identity and reputation other agents can check. Standards such as x402 for HTTP payments and ERC-8004 agent registries, now also on Solana, make this practical. We build agent wallets with budgets and kill switches, metered payment flows, and reputation grounded in real settled payments rather than ratings that can be farmed.
What you get
- Agent wallet and policy contracts or programs
- x402 or payment-channel integration
- Registry and reputation integration
- SDK for agent developers
- Monitoring of agent spend
[ 02 ]What we build
The pieces, built to last.
- 01
Agent wallets
Owner-funded budgets with per-session caps, allowlists, expiry and a kill switch.
- 02
Pay-per-request APIs
x402 paywalls on your endpoints, so agents pay in USDC without accounts or keys.
- 03
Payment channels
Escrow once, settle once, for high-frequency metered usage.
- 04
Identity and registries
ERC-8004 agent identity and discovery on Solana and EVM chains.
- 05
Reputation
Scores built from settled payments by unrelated counterparties, with wash trading removed.
- 06
Verifiable delivery
Settlement tied to proof of work done, such as TEE attestations for inference.
[ 03 ]Where it pays off
Where it earns its keep.
- 01
API and data providers
Sell to agents per call, with no sign-up funnel.
- 02
Agent marketplaces
Agents that discover, hire and pay each other.
- 03
Compute providers
Paid only when attested hardware proves the work ran.
- 04
DeFi for agents
Pools and vaults open only to agents with verified reputation.
[ 04 ]How we deliver
Four steps, one team, start to finish.
The same people scope it, build it and stay after launch. Timings are typical for a first release; we agree yours after the deep dive.
- 01Week 1
Threat model and spec
Who can move money, under what conditions, and what happens when a key, an oracle or a bridge fails. Written down before code.
- 02Weeks 2 to 8
Build with invariants
Contracts or programs with unit, fuzz and invariant tests, least-privilege roles, timelocks and rate limits from the first commit.
- 03Weeks 6 to 10
Review and testnet
Internal review, an independent audit where value is at stake, and a public testnet with monitoring wired in.
- 04Ongoing
Mainnet and watch
A staged launch with caps, live alerting on admin actions and outflows, and a rehearsed incident plan.
[ 05 ]Stack
Tools we reach for.
Chosen per project, and we work in yours. Nothing here is a lock-in: you own the code and the accounts.
- x402
- Solana
- Base
- Anchor
- USDC
- ERC-8004
- Solana Agent Registry
- MCP
- TEEs (Intel TDX, AMD SEV-SNP)
- Bun
- TypeScript
[ 06 ]Related work
Built by the same team.
[ 07 ]Further reading
Problems we found, and how we would solve them.
- Agent payments4 min read
Agent payments settle on promises. They should settle on proof
Problemx402 and payment channels let agents pay for APIs and compute, but settlement is blind to whether the inference ran, on which model, or how many tokens it really used.ProposalSettle only against two signatures: the agent's spending voucher and a usage receipt signed inside the provider's attested enclave, with payments stopping the moment attestation lapses.Read the proposal - Agent reputation3 min read
Half of agent payment volume is fake. Reputation has to start from money that moved
ProblemAnalysts found that roughly half of x402 transactions were wash trading or self-dealing, and star ratings are cheaper still to fake, so neither can safely gate money.ProposalScore agents on net demand: settled stablecoin payments, with self-dealing and circular flows removed and each dollar weighted by the credibility of the wallet that paid it, published as a verifiable onchain account.Read the proposal - AI securityAI3 min read
MCP servers are your new supply chain
ProblemAgents trust tool descriptions and outputs from MCP servers they install like packages, so a poisoned description, a compromised server or an over-privileged token can steer or rob them.ProposalPut an MCP gateway between agents and servers: pinned and reviewed tool manifests, per-user scoped tokens, sandboxed local servers, output sanitising, egress allowlists and a full audit log.Read the proposal
[ 08 ]FAQ
Questions buyers ask.
Early. Independent analysts found that roughly half of x402 transactions were wash trading or self-dealing, and adjusted volumes are still small. The infrastructure is maturing fast, which is why trust and verification are worth building now.
With limits enforced onchain, not in the prompt: per-session caps, rolling budgets, allowlisted recipients, expiry and a kill switch the owner holds.
Yes. Zynd AI, an open network for agent identity, discovery and x402 payments, is on our work page, and we have built attestation-gated payments and payment-grounded reputation on Solana.
[ 09 ]More Web3 services
- Smart Contract DevelopmentContracts that do exactly what they promise.
- Solana Program DevelopmentSub-second apps on the fastest major chain.
- dApp DevelopmentOnchain apps people actually enjoy using.
- DeFi Protocol DevelopmentFinancial protocols that survive real markets.
- Smart Contract Security AuditFind the flaw before an attacker does.
- Real-World Asset TokenizationAssets that settle in minutes, not days.
- Stablecoin and Crypto PaymentsGlobal payments that settle in seconds.
- Wallets and Account AbstractionSelf-custody without the seed-phrase pain.
- Layer 2, Rollup and Appchain DevelopmentYour own chain, when you really need one.
- Cross-Chain and InteroperabilityOne product across every chain your users use.
- Zero-Knowledge Proof DevelopmentProve it without revealing it.
One company at a time