Hummingbot
Hummingbot is an open source Python framework, maintained by the Hummingbot Foundation, that lets traders build and run automated, high-frequency crypto trading strategies across both centralized (CEX) and decentralized (DEX) venues. The project ships several developer-facing components: the Hummingbot client (a CLI trading bot), Gateway (a TypeScript middleware that standardizes DEX/blockchain endpoints behind one REST API on port 15888, documented with a published OpenAPI spec), the Hummingbot API (a FastAPI REST server on port 8000 that orchestrates multiple bots, accounts, portfolios, and market data), an async Python API client, an official Model Context Protocol (MCP) server, and a set of open Agent Skills for AI trading agents. With 300+ exchange connectors and Apache-2.0 licensing, Hummingbot reports having facilitated tens of billions of dollars in trade volume across 100K+ deployed instances.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Hummingbot the way a machine reads it — 38 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Hummingbot scores 35.2/100 (thin), with a separate agent-readiness read of 30/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Hummingbot's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hummingbot/"
title="Hummingbot on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hummingbot.svg"
alt="Hummingbot Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/hummingbot/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hummingbot/"
title="Hummingbot on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hummingbot/card.svg"
alt="Hummingbot Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Hummingbot
Each block below is one kind of artifact we hold for Hummingbot. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Hummingbot API
The Hummingbot API is a FastAPI backend service (default port 8000) that orchestrates multiple trading bots and exposes REST routers for accounts and exchange credentials, tradi...
Hummingbot /chain/ethereum API
Ethereum and EVM-based chain endpoints
Hummingbot /chain/solana API
Solana and SVM-based chain endpoints
Hummingbot /config API
System configuration endpoints
Hummingbot /connector/0x API
0x connector endpoints
Hummingbot /connector/jupiter API
Jupiter connector endpoints
Hummingbot /connector/meteora API
Meteora connector endpoints
Hummingbot /connector/orca API
Orca connector endpoints
Hummingbot /connector/pancakeswap API
PancakeSwap EVM connector endpoints
Hummingbot /connector/pancakeswap-sol API
PancakeSwap Solana connector endpoints
Hummingbot /connector/raydium API
Raydium connector endpoints
Hummingbot /connector/uniswap API
Uniswap connector endpoints
Hummingbot /pools API
Pool management endpoints
Hummingbot /tokens API
Token management endpoints
Hummingbot /trading/clmm API
Unified cross-chain CLMM (Concentrated Liquidity) endpoints
Hummingbot /trading/swap API
Unified cross-chain swap endpoints
Hummingbot /wallet API
Wallet management endpoints
Scroll within the panel for all 17 ·
Open Collections 17
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONScroll within the panel for all 17 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Hummingbot MCP Server
Hummingbot maintains an official Model Context Protocol (MCP) server that lets MCP clients (Claude, Gemini CLI, Claude Code) drive Hummingbot for automated crypto trading across...
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Hummingbot Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Hummingbot — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/hummingbot · machine-readable index on apis.io
This is an independent, third-party profile of Hummingbot, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.