AI Agents Hub: Use Cases showcase

[konopkja]

Parent: #17615

Page Details

• URL: /ai-agents/use-cases/
• Template: static
• Word count: ~800
• Phase: 3 (Ecosystem)

Purpose

Showcase real applications of AI agents on Ethereum. Each use case includes a brief description, example project, and link to relevant sub-page.

Content Outline

• Automated DeFi — Portfolio management, yield optimization, liquidation protection
• Agent-to-agent commerce — Agents hiring other agents for specialized tasks
• Autonomous governance — DAO vote participation based on programmed strategies
• Risk management — Scam monitoring, front-running protection, rebalancing
• Creative work — Autonomous art (Botto), content with on-chain provenance
• Identity verification — Agents verifying other agents' credentials before transacting

Files to Create

• public/content/ai-agents/use-cases/index.md

Interlinking

Links to: /frameworks/, /data/, /faq/, /payments/

[douglasborthwick-crypto]

For the "Identity verification" use case, InsumerAPI is a production example of agents verifying on-chain credentials before transacting. It provides boolean token verification across 31 EVM chains with ECDSA-signed attestation responses. The AI Agent Verification API guide walks through the full workflow.

The full autonomous agent workflow: discover API via standard files (llms.txt, OpenAPI, ai-plugin.json) -> verify counterparty's on-chain holdings -> proceed with transaction. No human in the loop.

Available as an MCP server (npm) and LangChain toolkit (PyPI), both MIT licensed.

[douglasborthwick-crypto]

For the Identity verification use case ("Agents verifying other agents' credentials before transacting"):

DJD Agent Score + InsumerAPI is a production example of this pattern in the x402 ecosystem. The AI Agent Verification API guide covers the full integration approach.

DJD scores AI agent wallets 0–100 based on on-chain settlement history (behavioral trust). As one of its scoring dimensions, it calls InsumerAPI's POST /v1/attest to verify whether the agent wallet holds governance tokens, stablecoins, or NFTs across 31 EVM chains (credential trust). The attestation response is ECDSA P-256 signed, so the calling agent can verify it offline without re-querying the chain.

The flow:

1. Agent A wants to transact with Agent B
2. Agent A calls DJD to get Agent B's composite score (behavior + credentials)
3. DJD calls InsumerAPI to check Agent B's on-chain holdings as an identity signal
4. InsumerAPI returns a signed boolean per condition — no balances exposed
5. Agent A verifies the ECDSA signature client-side and decides whether to proceed

Both are live APIs with MCP servers and LangChain toolkits, so agents on any framework can call them natively.

This could serve as a concrete example alongside the more general description of the use case.

[douglasborthwick-crypto]

Quick update on the Identity verification use case: InsumerAPI now supports EAS attestation verification alongside token/NFT checks. A single API call can verify both on-chain holdings and Coinbase Verified Account status (KYC via Ethereum Attestation Service on Base).

This means the identity verification use case has two concrete patterns:

1. Credential verification — does this agent's wallet hold governance tokens, stablecoins, NFTs? (token gating)
2. Compliance verification — has this agent's wallet completed KYC via Coinbase Verifications? (EAS attestation)

Both return ECDSA-signed booleans, verifiable offline. Pre-configured compliance templates at GET /v1/compliance/templates — no EAS integration needed by the consuming agent.

If useful for the page, this is a concrete example of agents using Ethereum's own attestation infrastructure (EAS) for identity verification before transacting.

Full guide: AI Agent Verification API