
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 分