
AgentServices
to.agentservices由 agentservices.to 发布官方发布者v6.0.0更新于 Oct 24, 2026
52 paid x402 API endpoints for AI agents — crypto, data, DeFi, market intelligence.
概览
远程 MCP 服务器,提供加密行情、DeFi、市场情报、AI 推理和 Hyperliquid 交易接口,多数按次通过 x402 USDC 微支付收费。
- 可以做什么
- 获取免费加密市场数据:价格、热门代币、全球指标、恐惧贪婪指数、Gas、新闻、社交热点、兑换报价和预测。获取付费数据与综合分析:技术指标、DeFi 收益、链上分析、代币风险、信号、深度研究、投资组合和市场脉搏报告。通过付费接口进行 AI 推理、图像生成和文本转语音。提交和撤销受策略约束的 Hyperliquid 订单、查询订单状态、设置执行策略,并运行模拟或评估订单。使用策略模板处理争议。
- 适用场景
- 适合需要加密或 DeFi 市场数据、链上分析、打包研究报告,或希望无需自管 API 密钥即可使用付费推理网关的助手。也适合需要对 Hyperliquid 订单做策略校验转发或模拟交易评估的代理。
- 运行要求
- 远程 Streamable HTTP 端点,无需本地运行时或 API 密钥。免费接口无需任何配置;付费接口需要支持 x402 的客户端和 Base 上的 USDC 钱包。通过 ChatGPT 或 Claude 连接器的人工访问使用 Google OAuth 和 Stripe 预付余额。Hyperliquid 交易需要本地签名、经 approveAgent 授权的代理钱包。
安装
在 SourceWeft 中
- 打开 控制台中的 AgentServices,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/to.agentservices%2Fagentservices/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"agentservices": {
"type": "http",
"url": "https://agentservices.to/mcp"
}
}
}README
AgentServices
The paid API layer for AI agents — data, intelligence, inference, and media via x402 micropayments
Canonical project: https://github.com/vbkotecha/agentservices-api Official site: https://agentservices.to License: Apache-2.0
AgentServices is an independent project. It is not affiliated with, endorsed by, or a replacement for any other x402 market-data provider.
[Version] [Network] [Payment] [MCP] [Status]
Live at: agentservices.to | MCP Server: https://agentservices.to/mcp (Streamable HTTP) | Discovery: /.well-known/x402
What is this?
AgentServices is the monetized API layer for AI agents. No API keys, no subscriptions — agents pay per-request with USDC on Base using the x402 payment protocol.
60+ endpoints across crypto data, market intelligence, DeFi analytics, on-chain analytics, 400+ LLM models, image generation, text-to-speech, portfolio intelligence, and dispute resolution. 12 are free. 48+ are paid via x402 (from $0.002 to $0.25 per call).
What's new in v6.0
- 400+ LLM models via OpenAI-compatible
/v1/chat/completions— GPT, Claude, Gemini, DeepSeek, Grok, Llama, and more - Smart router — use
model: "auto"and the gateway classifies your task and picks the cheapest model that handles it - Image generation —
/v1/images/generationsvia gpt-image-2 ($0.05) - Text-to-speech —
/v1/audio/speechwith natural voices ($0.05) - 3 new MCP tools —
chat,generate_image,text_to_speech
Buyer path: discover → try → pay → retain
Use the buyer quickstart for the complete path. The exact next action is to run the no-credential discovery check:
Then follow the same buyer journey:
- Discover: confirm the hosted MCP server and free tool catalog with the MCP discovery proof.
- Try free: retrieve a real price result with the free SDK proof.
- Inspect the paid challenge: decode the live 402 terms with the paid SDK proof. It never signs or settles payment.
- Buy an outcome: pay the returned x402 terms, retry the same request, and retain the returned paid result. See the token-risk, market-pulse, and research-brief contracts for result limits and provenance.
- Retain evidence: run the existing receipt builder with the original challenge, paid response, and your wallet authorization or transaction reference.
The four proofs have different limits: discovery and free SDK verify no-spend access; the paid SDK proof verifies challenge shape only; the receipt builder hashes buyer-held evidence and does not verify settlement. None of them claims adoption, settlement, or revenue.
For activation measurement definitions, see Activation Metrics. To probe the live funnel, run python3 examples/check_activation_funnel.py.
Buyer path: discover → try → pay → retain
Use the buyer quickstart for the complete path. The exact next action is to run the no-credential discovery check:
Then follow the same buyer journey:
- Discover: confirm the hosted MCP server and free tool catalog with the MCP discovery proof.
- Try free: retrieve a real price result with the free SDK proof.
- Inspect the paid challenge: decode the live 402 terms with the paid SDK proof. It never signs or settles payment.
- Buy an outcome: pay the returned x402 terms, retry the same request, and retain the returned paid result. See the token-risk, market-pulse, and research-brief contracts for result limits and provenance.
- Retain evidence: run the existing receipt builder with the original challenge, paid response, and your wallet authorization or transaction reference.
The four proofs have different limits: discovery and free SDK verify no-spend access; the paid SDK proof verifies challenge shape only; the receipt builder hashes buyer-held evidence and does not verify settlement. None of them claims adoption, settlement, or revenue.
Endpoints
Free (no payment required)
Trade API — venue doors (FREE — not x402)
AgentServices is building venue trade doors under /v1/trade/{venue}/…. Hyperliquid ships first; more venues and a venue-neutral /v1/trade/execute router follow.
Each door is a policy leash + forward — not a smarter router. We do not claim better fills than the venue direct. Execution is free at the call (no x402 on the order path). Builder fees are omitted so routing through us is not more expensive than going direct.
We never collect venue API keys. Agents sign orders locally with an HL-approved agent wallet (approveAgent on the main wallet is the one human bootstrap step). AgentServices policy-checks (max notional, coin allowlist, kill switch) and forwards the signed payload.
Request bodies accept market_type: spot, perp, or future. Hyperliquid implements perp and spot today; unsupported types return a machine-readable market_type_not_supported error.
Legacy hl_* MCP tool names remain as aliases. See GET /v1/trade/hyperliquid/bootstrap for the approveAgent signing model.
Roadmap: /v1/trade/{venue} for additional venues; /v1/trade/execute for venue-neutral routing later.
Paid — Data APIs (x402)
Paid — Synthesis APIs (x402)
Paid — Bundled Intelligence (x402)
Paid — AI Inference (x402)
Paid — Dispute Resolution (x402)
Use Cases — What Agents Can Build
Portfolio Monitor
DeFi Yield Optimizer
Market Intelligence Agent
Technical Analysis Bot
Developer Research Agent
AI Chat / Inference
On-Chain Analytics
Quick Start
Using curl
Using as MCP Server (Claude Desktop, Cursor, etc.)
13+ MCP tools available: crypto_prices, trending_tokens, global_market, gas_prices, market_predictions, crypto_news, social_trending, technical_indicators, defi_yields, search_web, token_risk, crypto_signals, onchain_analytics, deep_research, portfolio_intelligence, defi_strategy, market_pulse, onchain_overview
Using with Python
Using with JavaScript/TypeScript
Dispute Resolution Engine
AgentServices includes an AI-powered dispute resolution system with 7 policy templates:
Human billing door (ChatGPT / Claude)
Wallet agents continue to pay via x402 on REST — unchanged. Humans connecting through ChatGPT Developer Mode or Claude custom connectors can use Google OAuth + Stripe prepaid credits on MCP.
MCP URL for ChatGPT: https://agentservices.to/mcp
Environment variables
Copy .env.example. Required to enable the human door:
Prepaid credit balances are stored in Stripe Customer Balance (one Stripe Customer per Google sub). No Redis, Postgres, or other database is required.
Without Google/Stripe vars the API boots in x402-only mode.
Google Cloud Console redirect URIs
Add both hosts:
https://agentservices.to/oauth/google/callbackhttps://api.agentservices.to/oauth/google/callback
Stripe webhook
Point Stripe to:
https://agentservices.to/billing/webhookhttps://api.agentservices.to/billing/webhook
Event: checkout.session.completed
Discovery & Listings
- x402 Discovery — Live
- MCP Registry — Listed as
to.agentservices/agentservices - CDP Bazaar — Extension enabled
- awesome-x402 — PR submitted
Tech Stack
- FastAPI (Python 3.11+)
- x402 v2 payment middleware (Coinbase CDP facilitator)
- USDC on Base Mainnet (EIP-3009 gasless transfers)
- Deployed on Vercel (
agentservices.to+api.agentservices.to, auto-deploy frommain)
Coinbase AgentKit Integration
AgentServices includes a built-in Coinbase AgentKit action provider (agentkit/ directory). This lets any AgentKit agent use AgentServices APIs with typed, documented actions:
18 actions covering free (prices, fear-greed, trending, gas) and paid endpoints (indicators, DeFi yields, portfolio intelligence, research, onchain analytics, AI inference, and more). See agentkit/README.md for full documentation.
License
MIT — Build on it, fork it, integrate it.
Links
- API: agentservices.to
- MCP: agentservices.to/mcp
- Discovery: agentservices.to/.well-known/x402
- GitHub: github.com/vbkotecha/agentservices-api
- x402 Protocol: x402.org
- Base: base.org
来源:README.md,提交 a9a5fd8
工具
0版本历史
1- v6.0.0最新Sep 16, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具必需15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分