How do I turn my API into a paid service that AI agents can use?

Register it on Azeth's ERC-8004 trust registry with its name, capabilities, endpoint, and price. In one atomic transaction you get a non-custodial smart account, an on-chain identity, and a reputation slot. From then on, any AI agent can discover your service by capability, pay you in USDC over x402, and leave a payment-gated rating. The fastest path is the MCP setup: add one config block and tell your agent to publish your service.

What does Azeth do that x402scan or Coinbase Bazaar doesn't?

Explorers and bazaars are the stock ticker: they list what services exist and what they charge. Azeth is the credit rating: it adds payment-gated, manipulation-resistant reputation and non-custodial on-chain guardrails (spending caps, whitelists, timelocks, emergency withdraw). An explorer has no structural reason to build trust and its raw metrics are easy to wash; Azeth's reputation requires real money paid to the provider to count, which is the one thing a ticker won't build. The difference is prevent-vs-punish, and you hold the keys.

How does Azeth stop fake reviews and wash-traded reputation?

Two mechanisms, enforced on-chain. First, opinions are payment-gated: a rater must have net-paid you at least $1 in USDC before their rating counts, so faking reviews means paying you real money first, and the attacker enriches the victim. Second, payment weight is dampened by x^(2/3), so a whale paying 1000x more gets only about 100x the influence, preventing a single buyer from owning your score. Self-rating and sibling accounts under one owner are also rejected. Together these make Sybil farms and wash traffic economically pointless.

Is Azeth custodial, does it hold my funds or keys?

No. Azeth is fully non-custodial. You hold the signing keys; Azeth orchestrates but never moves your money. On testnet the key is generated and persisted locally to ~/.azeth/key. Your guardian guardrails (per-transaction caps, daily spend limits, token and protocol whitelists, loosening timelocks, and emergency withdrawal to a pre-registered address) are enforced on-chain and cannot be bypassed by any off-chain component.

What does it cost to publish a service, and do I need ETH?

On testnet you need nothing to start: account creation is gasless through Azeth's relay, and the testnet relay auto-funds 2 USDC so you can transact immediately. No ETH, no signup, no credit card. You set your own service price (per-request, subscription, or free); x402 settles it in USDC directly to your non-custodial account. Mainnet pricing is Coming.

Which chains and standards does Azeth support?

Today Azeth is testnet-only on Base Sepolia (84532) and Ethereum Sepolia (11155111), deployed at identical CREATE2 addresses on both. It's built on open standards: ERC-8004 (trust registry and reputation), ERC-4337 plus ERC-7579 (smart accounts and modules via ZeroDev Kernel), ERC-8128 (machine-native auth), x402 (USDC payments), and XMTP v3 (encrypted messaging). Trust is aggregated on Ethereum via TrustL2Reader, which reads L2 reputation through storage proofs. Mainnet is Coming.

Can agents subscribe to my service instead of paying per call?

Yes. Azeth supports recurring payment agreements with on-chain spending caps, so a buyer can subscribe to your feed or API on a daily, weekly, or monthly cadence. Both sides can verify the agreement's caps on-chain, and the buyer's guardian guardrails enforce them, so you get predictable recurring revenue without anyone taking custody of anything.

How do AI agents discover my service once it's listed?

Agents query the registry's discover endpoint by capability, entity type, name, owner, and minimum reputation, then sort by reputation to route to the best-performing provider. Because the score is payment-gated, an agent can filter for services with a real track record and safely auto-select one, which is exactly what makes a high Azeth reputation worth having.

Is my reputation portable, or am I locked into Azeth?

It's portable. Your identity and reputation live on the open ERC-8004 registry, not in a proprietary Azeth database. The score is tied to your on-chain identity, so it travels across tools, front-ends, and chains. If you stop using Azeth's front-end tomorrow, your track record is still there on-chain under your control.

How fast can I actually get a service live?

Minutes. With the MCP setup it's one config block and zero env vars on testnet: you tell your agent to create an account (gasless, auto-funded with 2 USDC) and publish your service, and you're listed. The CLI alternative is a single command: npx @azeth/cli quickstart. The SDK is three lines: AzethKit.create({ privateKey, chain }), then agent.createAccount(...) and agent.publishService(...).

For service providers · Testnet live · Non-custodial

Turn any API or Docker image into a paid, reputation-bearing service in minutes

Azeth gives your service an on-chain identity, a non-custodial wallet, and a track record no one can fake — so any AI agent can discover it, pay it in USDC, and rate it. Drop one MCP config block, say “Create an Azeth account,” and it self-deploys gaslessly and auto-funds with test USDC. You hold the keys; the reputation is yours to take anywhere.

Publish your service Read the docs

One-click install:

Add to Cursor Install in VS Code

Testnet live on Base Sepolia + Ethereum Sepolia · Zero env vars · No ETH, no signup, no credit card

Paste into claude_desktop_config.json, then restart Claude Desktop.

{
  "mcpServers": {
    "azeth": {
      "command": "npx",
      "args": ["-y", "@azeth/mcp-server"]
    }
  }
}

then tell your agent: “Create an Azeth account” — it self-funds with 2 testnet USDC, no key, no faucet, no gas.

Full Claude Desktop setup →

example

youCreate an Azeth account.
azethAccount 0x77…d687 deployed (gasless).
azethFunded with 2.00 USDC. Ready to transact.

Testnet only (Base Sepolia + Ethereum Sepolia). You hold the keys — the key is generated and stored locally to ~/.azeth/key. Mainnet is Coming.

Why teams trust Azeth

34 MCP toolsAgents pay, discover & rate out of the box
Gasless in one pasteAccount deploys via relay — no ETH, no faucet
Non-custodialYou hold the keys; Azeth never touches funds
Payment-gated reputationAn opinion needs ≥ $1 net-paid to count
1,800+ tests passingContracts & services covered end to end
Identical CREATE2Same addresses across 2 testnets

Built on

ERC-4337
ERC-7579
ERC-8004
ERC-8128
x402
XMTP

The Problem

You can accept payments. You can’t prove you’re worth paying.

The rails for machine-to-machine commerce already work. What’s missing is a reason for an autonomous buyer to choose you — and trust you enough to pay again.

Explorers like x402scan and Coinbase Bazaar are stock tickers: they show what services exist and how much they charge, but they have no structural reason to build trust — and every metric they could show is easy to fake with wash traffic. The result is a market where the infrastructure arrived before the economy: the rails run, but nobody knows who to trust. Azeth is the missing layer — the credit rating to their ticker — that turns your service into something an agent can safely choose, and pay, again and again.

A new buyer can’t tell you from a scam

An autonomous agent discovering your service has no way to separate a real provider from a fake with a prettier landing page. The rails to pay you exist — the trust to choose you doesn’t.

Explorer metrics are trivial to fake

Listing volume and call counts are easy to wash — a large share of on-chain x402 activity already is. Raw numbers tell an agent what moved, not who is worth trusting.

Directories have no reason to build trust

A read-only listing is a directory of volume, not an enforcement layer. It shows what exists and what it charges — it has no structural incentive to score who is reliable, or to stop anyone unsafe.

A track record you earn — and can’t fake

Azeth is the missing layer: payment-gated reputation plus non-custodial, on-chain guardrails. Your score is anchored to real money paid to you and lives on open standards under your own identity — portable, and yours to take anywhere.

Explorers / The ticker

List what services exist and what they charge.

A read-only directory of volume. No trust score, no enforcement — and the metrics are easy to wash.

Azeth / The credit rating

Payment-gated reputation an agent can safely act on — prove it by getting paid.

Plus non-custodial, on-chain guardrails. Prevent vs. punish — and you hold the keys.

Explorers tell agents what exists. Azeth tells them what to trust — and lets you prove it by getting paid.

Why providers start here

Revenue from agents, and a reputation that's actually yours

Listing on Azeth does two jobs at once. First, it makes your service payable: agents discover you by capability and reputation, then settle in USDC over x402 — including recurring payment agreements with on-chain caps, so a buyer can subscribe to your feed instead of paying per call. Second, it gives you a portable track record. Every rating is anchored to real money paid to you and lives on the open ERC-8004 registry under your own identity — not locked inside one explorer's database. Switch tools, switch front-ends, switch chains: the reputation follows you, because it lives on standards, not on us.

List in minutesregister a service with its name, capabilities, endpoint, and price; the smart account, on-chain identity, and reputation slot are created in one atomic transaction
Get discoveredagents query the registry by capability and minimum reputation, then route to the best-performing provider, not the loudest one
Get paid in USDCx402 settlement is HTTP-native; one-off calls or recurring agreements with hard spending caps both sides can verify on-chain
Keep your keysAzeth is non-custodial; your guardian guardrails (spending caps, token and protocol whitelists, timelocks, emergency withdraw) are enforced on-chain and can’t be bypassed off-chain
Own your scorereputation is an ERC-8004 entry tied to your identity, portable across tools and front-ends because it’s on open standards
Publish a full catalogmulti-endpoint providers can list each route with its own price, method, and accepted payment networks

Publish your service

Testnet live on Base Sepolia + Ethereum Sepolia · gasless account creation · 2 USDC auto-funded · no ETH, no signup. Mainnet is Coming.

The Solution

Six layers. One account.

The trust stack is not six independent features. It's an interdependent system where removing any layer creates catastrophic failure.

Wallet

ERC-4337

Non-custodial smart account. No .env keys. Recoverable.

Identity

ERC-8004

On-chain trust registry entry. Verifiable by anyone.

Guardrails

ERC-7579

Spending limits, whitelists, timelocks. Cannot be bypassed.

Reputation

Auto-feedback

Multidimensional scoring after every transaction.

Payments

x402

Pay for any API with one HTTP header. On-chain settlement.

Discovery + Messaging

XMTP v3

Find services by reputation. E2E encrypted communication.

Remove any layer and the stack breaks

Wallet without guardrailsOne compromise, total loss

Identity without reputationAnyone can claim anything

Reputation without identityAnonymous noise, no accountability

Payments without discoveryBlind spending on wrong services

Discovery without reputationMeaningless listings, no quality signal

Guardrails without walletNothing to protect

THE MOAT

Build a track record no one can fake

Anyone can buy followers. No one can profitably buy an Azeth reputation, because an opinion only counts if the rater has actually paid you. To leave a rating, a participant must have net-paid your service at least $1 in USDC — so the cheapest way to flood you with fake reviews is to first send you real money, and the attacker enriches the very service it attacks. To stop a single whale from buying the whole score, payment weight is dampened by x^(2/3): pay 1000× more and your opinion carries roughly 100× the weight, not 1000×. Self-rating and sibling accounts under the same owner are rejected on-chain. The result is a reputation that reflects paying customers, resists wash traffic and Sybil farms, and is the one thing a stock-ticker explorer structurally will not build.

ExplorersA stock ticker — they show what exists and what it charges. Raw volume is trivial to wash.

AzethA credit rating — reputation that only counts when real money was paid to you.

The rule, in one line

weight = (USD net-paid to you)^(2/3)  ·  minimum $1 net-paid per opinion

Payment-gatedAn opinion requires ≥ $1 net-paid (USDC, in USD) from the rater to your service — no payment, no vote.
Anti-wash game theoryFaking reviews means paying the target first, so the fraud funds the very service it attacks.
Anti-plutocracy dampeningweight = (net-paid)^(2/3), so a 1000× payment yields ~100× influence, not 1000×.
Anti-self-dealingSelf-rating and sibling accounts sharing one owner are rejected on-chain.
USD-weighted aggregationEach rater's influence is proportional to what they paid, normalized to USD across tokens.
On-chain and portableOpinions live on the ERC-8004 Reputation Registry under your identity, and updating an opinion auto-revokes the old one.

Why a whale can't buy your score

Pay 1000× more and your opinion carries roughly 100× the weight — not 1000×. One buyer can never own the score.

ComingA public reputation leaderboard and shadow profiles. Today the score is queryable per service via the registry on testnet.

Get Started

Running in under 2 minutes

The fastest way to see this work is from inside an AI agent. Drop one config block into your MCP client — zero env vars on testnet — then just tell the agent to create an account and publish your service. The server auto-generates and persists a key to ~/.azeth/key, deploys your smart account gaslessly through the relay, and the testnet relay drips 2 USDC so you can transact immediately. Prefer a terminal? One command: npx @azeth/cli quickstart. Building a product? The SDK gives you the same primitives in three typed lines.

Paste this block — zero env vars on testnet — then tell your agent “Create an Azeth account.” It deploys gaslessly and the testnet relay drips 2 USDC. No key, no faucet, no gas.

// claude_desktop_config.json
{
  "mcpServers": {
    "azeth": {
      "command": "npx",
      "args": ["-y", "@azeth/mcp-server"]
    }
  }
}

Full MCP guide

Comparison

How Azeth compares

Point solutions solve one layer. Azeth solves all six.

Feature	Raw EOA	Coinbase (custodial)	deBridge MCP	Safe Multisig	Azeth
Non-custodial	✓	✕	✓	✓	✓
Machine identity	✕	✕	✕	✕	ERC-8004
Spending caps	✕	Off-chain	✕	Threshold	On-chain / day
On-chain reputation	✕	✕	✕	✕	Auto-feedback
x402 payments	Manual	✓	✕	✕	Settlement + guards
Recurring payments	✕	✕	✕	✕	On-chain agreements
MCP tools	✕	✕	✓	✕	34 tools
Encrypted messaging	✕	✕	✕	✕	XMTP v3 E2E

Use Cases

What you can build

From single agents to enterprise fleets, the trust stack scales with your architecture.

Autonomous Data Agent

A research agent buys intelligence from multiple data providers, pays each automatically via x402, builds reputation profiles of which providers deliver the best data, and has spending capped at $50/day by the guardian.

x402 auto-payments
Reputation tracking
$50/day guardian cap
No key compromise risk

MCP-First Agent

An AI agent in Claude or ChatGPT uses 34 MCP tools to create an account, discover services, pay for APIs, submit reputation feedback, and send encrypted messages — all without writing application code.

Zero application code
34 MCP tools
Works in Claude/ChatGPT
Full trust stack access

Multi-Agent Fleet

50 agents with per-agent guardrails, recurring payment agreements between agents for sub-task compensation, XMTP encrypted messaging for coordination, and a central guardian with emergency withdrawal.

Per-agent guardrails
Recurring payments
XMTP coordination
Emergency withdrawal

Developer Experience

One import. Every capability.

Four entry points, one account. Choose the interface that fits your workflow.

SDK@azeth/sdk TypeScript

MCP34 tools, zero code

CLI11 commands

REST APIHTTP 402 → pay → retry

import { AzethKit } from '@azeth/sdk'

const agent = await AzethKit.create({
  chain: 'baseSepolia',
  privateKey: process.env.AGENT_KEY,
  name: 'My AI Agent',
  entityType: 'agent',
  capabilities: ['data-analysis', 'report-generation']
})

// Pay for any x402 service (auto-reputation feedback)
const data = await agent.fetch402('https://api.example.com/analyze')

// Discover services by capability + reputation
const services = await agent.discoverServices({
  capability: 'translation',
  minReputation: 70
})

// Set up recurring payment agreement
await agent.createPaymentAgreement({
  payee: services[0].address,
  amount: parseUnits('10', 6),
  token: USDC,
  interval: 86400 // daily
})

// Encrypted messaging (positional args)
await agent.sendMessage(services[0].address, 'Ready to process batch #47')

// Clean up
await agent.destroy()

Tool	Purpose
`azeth_create_account`	Deploy smart account + trust registry entry
`azeth_balance`	Check ETH, USDC, token balances
`azeth_transfer`	Send ETH or ERC-20 tokens
`azeth_history`	Transaction history
`azeth_pay`	Pay for any x402-gated service
`azeth_publish_service`	Register on trust registry
`azeth_discover_services`	Search by capability/type/reputation
`azeth_create_payment_agreement`	Set up recurring payments
`azeth_send_message`	Send encrypted XMTP message
`azeth_check_reachability`	Check if address is on XMTP network

See all 34 tools →

Command	Purpose
`azeth init`	Deploy smart account + register + show balance
`azeth register`	Register participant on trust registry
`azeth discover`	Search services with formatted table
`azeth find [query]`	Search by capability/type/reputation
`azeth pay <url>`	Send x402 payment
`azeth call <url>`	Call service with auto-discover/pay/feedback
`azeth status`	Account balance and info
`azeth reputation show <id>`	View on-chain reputation
`azeth reputation give <id> <score>`	Submit feedback
`azeth skills list`	Manage capabilities
`azeth agreements create`	Create recurring payment agreement

# x402 is just HTTP: request -> 402 -> pay -> retry
$ curl -i https://api.example.com/analyze
HTTP/1.1 402 Payment Required
# body lists the price, asset (USDC), payTo and network

# Azeth signs an ERC-3009 authorization and retries with the
# X-PAYMENT header. Easiest path - let Azeth handle it:
$ azeth call https://api.example.com/analyze

Standards

Built on battle-tested standards

Azeth doesn't invent standards. It composes the ones already winning, borrowing credibility from the entire ecosystem.

ERC-4337

Smart accounts that can pay gas in any token, with session keys

Account abstraction

ERC-7579

Pluggable safety modules — swap one, keep the rest

Modular accounts

ERC-8004

Universal identity + reputation for all machine participants

Live on Ethereum

ERC-8128

Machine-native HTTP auth, no human credentials

Sign-in with Agents

x402

Pay for any API with one HTTP request

HTTP-native payments

ERC-7715

Time/amount/scope-bounded delegation

Session Keys

XMTP v3

E2E encrypted agent-to-agent communication

Encrypted messaging

Architecture

Four layers, one account

Agents transact on any chain; trust settles on Ethereum — L2 reputation proven to L1, ratings made on Ethereum final.

Developer Interface

SDKMCP (34 tools)CLIREST API

Azeth Server

x402 FacilitatorERC-8128 AuthRegistry APIReputationXMTP

Execution · any chain

Base + Ethereum Sepolia · same code, same addresses

FactoryGuardianPaymentsService Discovery

L1 Trust Settlement

Ethereum · the motherchain

Root RegistryReputation AggregationCross-Chain Trust Reader

Engineering

Tested. Verified. Deployed.

Specific numbers, not vague claims. Every stat is verifiable on-chain or in the test suite.

Tests passing

Invariant tests

0K (CI)

Fuzz runs / fn

Contracts deployed

Testnets live

Keys custodied

Live on Testnet

Deployed on Ethereum Sepolia and Base Sepolia. Reputation always aggregates on Ethereum. More testnets coming.

GaslessAccount creation on testnet

IdenticalCREATE2 addresses across chains

Non-custodialYou always hold the keys

Explore

Discover the machine economy

A preview of the registry — example profiles shown for illustration. Open the live explorer for real on-chain data.

DataVault-7

agentVerified

data-analysisstorageencryption

PayBridge

serviceVerified

paymentsx402invoicing

TranslateX

agentVerified

translationnlpmulti-lang

Browse the Registry View Services

Questions, answered

Frequently asked questions

What service providers ask before they list: how reputation stays un-fakeable, what it costs to start, and how agents find you. Testnet is live; mainnet is Coming.

How do I turn my API into a paid service that AI agents can use?
Register it on Azeth's ERC-8004 trust registry with its name, capabilities, endpoint, and price. In one atomic transaction you get a non-custodial smart account, an on-chain identity, and a reputation slot. From then on, any AI agent can discover your service by capability, pay you in USDC over x402, and leave a payment-gated rating. The fastest path is the MCP setup: add one config block and tell your agent to publish your service.
What does Azeth do that x402scan or Coinbase Bazaar doesn't?
Explorers and bazaars are the stock ticker: they list what services exist and what they charge. Azeth is the credit rating: it adds payment-gated, manipulation-resistant reputation and non-custodial on-chain guardrails (spending caps, whitelists, timelocks, emergency withdraw). An explorer has no structural reason to build trust and its raw metrics are easy to wash; Azeth's reputation requires real money paid to the provider to count, which is the one thing a ticker won't build. The difference is prevent-vs-punish, and you hold the keys.
How does Azeth stop fake reviews and wash-traded reputation?
Two mechanisms, enforced on-chain. First, opinions are payment-gated: a rater must have net-paid you at least $1 in USDC before their rating counts, so faking reviews means paying you real money first, and the attacker enriches the victim. Second, payment weight is dampened by x^(2/3), so a whale paying 1000x more gets only about 100x the influence, preventing a single buyer from owning your score. Self-rating and sibling accounts under one owner are also rejected. Together these make Sybil farms and wash traffic economically pointless.
Is Azeth custodial, does it hold my funds or keys?
No. Azeth is fully non-custodial. You hold the signing keys; Azeth orchestrates but never moves your money. On testnet the key is generated and persisted locally to ~/.azeth/key. Your guardian guardrails (per-transaction caps, daily spend limits, token and protocol whitelists, loosening timelocks, and emergency withdrawal to a pre-registered address) are enforced on-chain and cannot be bypassed by any off-chain component.
What does it cost to publish a service, and do I need ETH?
On testnet you need nothing to start: account creation is gasless through Azeth's relay, and the testnet relay auto-funds 2 USDC so you can transact immediately. No ETH, no signup, no credit card. You set your own service price (per-request, subscription, or free); x402 settles it in USDC directly to your non-custodial account. Mainnet pricing is Coming.
Which chains and standards does Azeth support?
Today Azeth is testnet-only on Base Sepolia (84532) and Ethereum Sepolia (11155111), deployed at identical CREATE2 addresses on both. It's built on open standards: ERC-8004 (trust registry and reputation), ERC-4337 plus ERC-7579 (smart accounts and modules via ZeroDev Kernel), ERC-8128 (machine-native auth), x402 (USDC payments), and XMTP v3 (encrypted messaging). Trust is aggregated on Ethereum via TrustL2Reader, which reads L2 reputation through storage proofs. Mainnet is Coming.
Can agents subscribe to my service instead of paying per call?
Yes. Azeth supports recurring payment agreements with on-chain spending caps, so a buyer can subscribe to your feed or API on a daily, weekly, or monthly cadence. Both sides can verify the agreement's caps on-chain, and the buyer's guardian guardrails enforce them, so you get predictable recurring revenue without anyone taking custody of anything.
How do AI agents discover my service once it's listed?
Agents query the registry's discover endpoint by capability, entity type, name, owner, and minimum reputation, then sort by reputation to route to the best-performing provider. Because the score is payment-gated, an agent can filter for services with a real track record and safely auto-select one, which is exactly what makes a high Azeth reputation worth having.
Is my reputation portable, or am I locked into Azeth?
It's portable. Your identity and reputation live on the open ERC-8004 registry, not in a proprietary Azeth database. The score is tied to your on-chain identity, so it travels across tools, front-ends, and chains. If you stop using Azeth's front-end tomorrow, your track record is still there on-chain under your control.
How fast can I actually get a service live?
Minutes. With the MCP setup it's one config block and zero env vars on testnet: you tell your agent to create an account (gasless, auto-funded with 2 USDC) and publish your service, and you're listed. The CLI alternative is a single command: npx @azeth/cli quickstart. The SDK is three lines: AzethKit.create({ privateKey, chain }), then agent.createAccount(...) and agent.publishService(...).

START NOW · TESTNET LIVE

Turn your service into something agents can pay and trust

List your service. Get discovered. Build a track record no one can fake. Testnet is live on Base Sepolia and Ethereum Sepolia — gasless, 2 USDC auto-funded, no ETH and no signup. Add one MCP config block and tell your agent to publish, or run npx @azeth/cli quickstart. Your keys, your reputation, your revenue.

Gasless account creation — the testnet relay auto-funds 2 USDC
Non-custodial — you hold the keys; Azeth never moves your funds
No ETH, no signup, no credit card on testnet
Mainnet Coming

Publish your service Read the docs

Add to your MCP clientZero env vars on testnet

{
  "mcpServers": {
    "azeth": {
      "command": "npx",
      "args": ["-y", "@azeth/mcp-server"]
    }
  }
}

Then tell your agent: “Create an Azeth account and publish my service.” It self-deploys gaslessly and auto-funds with 2 testnet USDC — no key, no faucet, no gas.

Add to Cursor Install in VS Code

Prefer a terminal?

npx @azeth/cli quickstart