DEV Community

aimall
aimall

Posted on Edited on

Let Your Agent Call Any AI Tool in One Click — Open-Sourcing the Souyi AIMALL MCP Server

#mcp #ai #agents #trust

Let Your Agent Call Any AI Tool in One Click

A zero-dependency MCP server that lets any MCP-capable agent (Claude, Cursor, Dify, Coze, LangChain) plug into the Souyi AIMALL AI tool marketplace — models, search, image, voice, video — pay-as-you-go, with a $1 free trial on signup (and $4 more after email verification).

The Problem: Agents Want AI Tools, but Integration Cost Kills Them

Every agent builder hits the same wall today:

  • Want to add "web search" or "image generation" to your agent? You have to sign up at each vendor, read docs, wire up SDKs, and manage separate API keys.
  • Every vendor bills differently; balances are scattered everywhere, so you can never tell how much a single agent task actually cost.
  • Switching models means code changes; switching vendors means rewriting the adapter layer.

Result: 80% of agent projects die before their first successful external AI call.

The Fix: Make AI Tools a "Plug-and-Play Standard Part"

Souyi AIMALL is an AI API marketplace built for agents. Models and tools are unified behind a single endpoint — /api/v1/ai/request — authenticated with one X-API-Key, metered per call, returning a unified order and balance.

To let agents discover and connect themselves, we shipped three machine-readable artifacts:

  1. llms.txt — an LLM/crawler overview plus a 3-step self-serve onboarding guide;
  2. openapi.json — the full OpenAPI 3.0.3 contract;
  3. .well-known/agent.json — an A2A-style Agent Card.

On top of that, we are open-sourcing the official MCP Server: it wraps the marketplace into 5 standard MCP tools that any MCP client can load in one click.

Zero Dependencies: Runs on Python 3.9+ Without pip install

Most MCP servers depend on a pile of third-party packages — if they don't install, they're useless. Ours uses only the Python standard library (stdio + JSON-RPC). Clone it and run python3 server.py.

export AIMALL_API_KEY="ak_your_key"   # from the "My Agents" page on souyi.net.cn
python3 server.py
Enter fullscreen mode Exit fullscreen mode

Five Tools Covering the Whole Flow

Tool Purpose
list_assets List every AI asset in the marketplace (ID, type, unit price)
ai_estimate Estimate the cost of a call (no charge) — use it as a budget gate
ai_request Actually call the tool; returns result + order ID + remaining balance
bootstrap_account Self-serve signup + agent creation; fetches the key end-to-end
get_onboarding Returns onboarding steps and doc links

A typical agent workflow: list_assets to find a tool → ai_estimate to price it → approve → ai_request to run it.

Connect to Claude Desktop in 30 Seconds

Edit claude_desktop_config.json:

{
  "mcpServers": {
    "aimall": {
      "command": "python3",
      "args": ["/your/path/aimall-mcp/server.py"],
      "env": { "AIMALL_API_KEY": "ak_your_key" }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Restart Claude, and it can immediately "write code with MiniMax-M3", "generate an image", or "run a web search" for you — billed from the free trial, no human approval needed.

Snippets for Cursor, LangChain, Dify, and Coze live in the repo's config-examples/.

Why This Matters for the Agent Ecosystem

  • Discovery: llms.txt / openapi.json / agent.json let agent frameworks understand automatically what this platform does and how to call it;
  • Unification: one endpoint, one key, one bill — goodbye to multi-vendor fragmentation;
  • Zero friction: $1 on signup (+$4 after email verify), self-serve top-up via x402 (USDC on Base) to remove human approval — truly unattended.

The Part Agents Actually Care About: A Verifiable Trust Layer

An MCP server that says it works is not enough. Agents need evidence. AIMALL now exposes a trust layer so an agent can judge a tool before spending:

  • Live telemetry on every asset (GET /api/v1/assets): 30-day success rate, p50/p95 latency, uptime, and last-success time — machine-readable, no guessing.
  • Verified Outcome Records: after a call, the calling agent can submit a signed outcome (POST /api/v1/outcomes) — did it succeed, how long, quality score, would-it-retry. Anti-sybil: only agents that actually used the asset can vouch for it.
  • Reputation, portable: GET /api/v1/agent-card returns an ERC-8004-style card — the agent's own real call volume, success rate, and verified outcomes.
  • Decision help: POST /api/v1/compare takes {task, budget, constraints} and returns a ranked, evidence-weighted shortlist with transparent scoring.
  • Come back later: GET /api/v1/heartbeat is a subscription feed (new assets, incidents, real-call volume); GET /api/v1/agent-docs/weekly-report is an original "what agents actually used" digest.

In short: AIMALL is not just a marketplace you call — it's one you can verify. That is the difference between a tool an agent tries once and a tool it trusts.

Get Started

Drop your first agent + AIMALL workflow in the comments.

Top comments (0)