name: agent-ecosystem-landscape
description: "Comprehensive map of agent skills, tools, and MCP servers across big tech, crypto/Web3, agent frameworks, and developer infrastructure. Use when evaluating competitors, planning integrations, or positioning AgentHQ."
metadata:
openclaw:
emoji: "🗺️"

Agent Ecosystem Landscape

Last updated: 2026-02-08 — sourced from a comprehensive registry sweep of MCP servers, agent frameworks, and tool ecosystems.

Overview

The agent tooling ecosystem has exploded. Every major platform now exposes capabilities via MCP servers, function calling, or SDK integrations — letting AI agents interact with payments, databases, identity, code execution, and thousands of SaaS apps.

This skill maps the landscape across five categories:

Key Findings

1. MCP is the dominant integration pattern

Every major platform (Stripe, Supabase, Cloudflare, Circle, Anthropic) now ships an MCP server. Function calling remains for LLM-native tools (OpenAI, Meta), but MCP is the universal connector.

2. Crypto/Web3 are among the earliest MCP adopters

Circle, ENS, Chainlink, Uniswap, and Base all have production MCP servers — often before their Web2 counterparts.

3. Coordination is solved; payments are not

These integrations primarily support coordination and productivity, with limited direct payment features. The two payment-adjacent platforms:
- Stripe (#2 ranked) — fiat rails, centralized, KYC-gated
- Circle (#5 ranked) — on-chain but walled garden (their wallets, their infra)

4. Nobody has open, permissionless agent-to-agent payments

This is the gap. No platform offers a protocol where any agent can pay any other agent without intermediaries.

5. AgentHQ positioning

AgentHQ/x402 sits between Stripe (#2 fiat) and Circle (#5 walled garden) but is permissionless:
- Settlement: EIP-3009 (USDC transferWithAuthorization)
- Receipts: EAS attestations (on-chain, verifiable)
- Discovery: HTTP 402 status code (standards-based)

Top 20 Agent Tool Integrations

1. OpenAI (function calling + MCP connectors)
2. Stripe MCP (fiat payments)
3. Supabase MCP (database + auth)
4. Cloudflare MCP (infrastructure)
5. Circle MCP (on-chain payments)
6. ENS MCP (identity)
7. Chainlink MCP (price feeds)
8. Uniswap MCP (DEX prices)
9. GitHub MCP (code)
10. Supabase MCP (edge functions)
11. Slack MCP (messaging)
12. Twilio MCP (SMS/MMS)
13. Notion MCP (knowledge)
14. Zapier MCP (~8000 apps)
15. Postman MCP (API testing)
16. LangChain (framework + MCP adapters)
17. CrewAI (30+ built-in tools)
18. AutoGen (multi-agent coordination)
19. Phidata (40+ toolkits)
20. Base Builder MCP (Web3 dev)

When to Use This Skill

• Competitive analysis: Understanding what tools agents already have access to
• Integration planning: Picking which MCP servers or frameworks to support
• Positioning AgentHQ: Articulating the gap x402 fills vs Stripe/Circle
• Discovery: Finding the right MCP registry or server for a specific need
• Architecture decisions: Choosing between MCP, function calling, SDK approaches