Cowrie Research

azeth-primary-sources-2026-05-03

3 min read

Azeth primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone Azeth whitepaper or litepaper surfaced.
  • The clearest current sources of truth were the official site, the SDK README, the MCP server README, the GitHub organization profile, and the agent-starter template.
  • The materials consistently frame Azeth as a trust/discovery/payments stack for AI agents and machine participants rather than as only a wallet SDK or a single MCP integration.

Primary-source snapshots

1) Official website

  • URL: https://azeth.ai/
  • Key excerpt:
    • The homepage says one non-custodial smart account gives every AI agent a wallet, identity, guardrails, reputation, payments, discovery, messaging, and auth.
    • It repeatedly demonstrates discovery by capability and reputation plus x402-paid fetches.
    • The site also anchors the stack in standards such as ERC-4337, ERC-7579, ERC-8004, ERC-8128, ERC-7715, x402, and XMTP.

2) SDK README

  • URL: https://raw.githubusercontent.com/azeth-protocol/sdk/main/README.md
  • Key excerpt:
    • The SDK README presents AzethKit as the main interface for smart accounts, x402 payments, reputation, messaging, and service discovery.
    • It documents methods like createAccount(), fetch402(), smartFetch402(), discoverServices(), submitOpinion(), and createPaymentAgreement().
    • This is strong evidence that Azeth is packaging a multi-surface control plane rather than only an identity or wallet module.

3) MCP server README

  • URL: https://raw.githubusercontent.com/azeth-protocol/mcp-server/main/README.md
  • Key excerpt:
    • The MCP server README says Azeth provides 32 tools spanning account creation, transfers, payments, agreements, registry publishing/discovery, reputation, messaging, and guardian controls.
    • It says the server can work with zero configuration on testnet and can auto-generate/persist a private key if one is not supplied.
    • This is a useful practical clue that Azeth’s current shipped operator model is still key-based even though the website markets a smoother future-state UX.

4) GitHub organization profile

  • URL: https://github.com/azeth-protocol
  • Key excerpt:
    • The organization profile ties together the SDK, MCP server, provider package, CLI, common package, agent starter, and an agent-commerce demo.
    • Its top-level description says Azeth provides smart accounts, x402 payments, on-chain reputation, and service discovery for AI agents.
    • The repo spread reinforces that Azeth is an ecosystem/toolchain effort rather than a single-package proof of concept.

5) Agent starter template

  • URL: https://raw.githubusercontent.com/azeth-protocol/agent-starter/main/README.md
  • Key excerpt:
    • The agent-starter README shows separate consumer and provider flows, with providers registering on the trust registry and serving x402-gated APIs.
    • It explicitly says providers using plain EOAs can receive payments but cannot be rated, discovered, or guarded like smart-account-based providers.
    • That is a strong categorization clue that Azeth is selling an integrated trust layer, not just wallet connectivity.

Working conclusion

Azeth is best cataloged as machine-economy trust infrastructure: a bundled stack for smart accounts, guardrails, discovery, paid access, reputation, and messaging. The decisive evidence in this pass was the repeated combination of ERC-4337 account management, registry/discovery, x402 payment flows, reputation tooling, recurring agreements, and a 32-tool MCP surface—all presented as one coordinated operating layer for agents.

Graph View