Compare commits
15 Commits
ecf6532a03
...
08a48dc047
| Author | SHA1 | Date |
|---|---|---|
|
|
08a48dc047 | |
|
|
1c5fba3ae9 | |
|
|
6a79e1765d | |
|
|
098dd04159 | |
|
|
cce49579d7 | |
|
|
04216864a2 | |
|
|
fa220a1824 | |
|
|
b8cadd281b | |
|
|
9ea0b6e928 | |
|
|
395cb8e20b | |
|
|
a220151853 | |
|
|
28bfaeeee3 | |
|
|
ef01c5ccc3 | |
|
|
09eb0e877e | |
|
|
6b43587627 |
|
|
@ -45,5 +45,5 @@ body:
|
|||
required: true
|
||||
- label: "我已经在本地测试过这个提示词,并确认其有效性。"
|
||||
required: true
|
||||
- label: "我同意将这个提示词以项目所使用的 [MIT License](LICENSE) 授权给社区。"
|
||||
required: true
|
||||
- label: "我同意将这个提示词以项目所使用的 [MIT License](../../LICENSE) 授权给社区。"
|
||||
required: true
|
||||
|
|
|
|||
14
AGENTS.md
14
AGENTS.md
|
|
@ -144,11 +144,13 @@ git push origin develop
|
|||
│ │ ├── config.toml # Codex CLI 配置文件
|
||||
│ │ └── AGENTS.md # Codex/Agent 指南(本目录)
|
||||
│ ├── documents/ # 文档库
|
||||
│ │ ├── 05-哲学与方法论/ # 最高思想纲领与方法论
|
||||
│ │ ├── 00-基础指南/ # 核心原则与底层逻辑
|
||||
│ │ ├── 01-入门指南/ # 从零开始教程
|
||||
│ │ ├── 02-方法论/ # 具体工具与技巧
|
||||
│ │ └── 03-实战/ # 项目实战案例
|
||||
│ │ ├── principles/ # 原则与思想(fundamentals + philosophy)
|
||||
│ │ │ ├── fundamentals/ # 原 00-基础指南
|
||||
│ │ │ └── philosophy/ # 原 05-哲学与方法论
|
||||
│ │ ├── guides/ # 入门与方法(getting-started + playbook)
|
||||
│ │ │ ├── getting-started/ # 原 01-入门指南
|
||||
│ │ │ └── playbook/ # 原 02-方法论
|
||||
│ │ └── case-studies/ # 原 03-实战
|
||||
│ ├── prompts/ # 提示词库(指向云端表格)
|
||||
│ │ ├── README.md # 在线表格链接
|
||||
│ │ └── AGENTS.md # prompts/ 目录规则
|
||||
|
|
@ -282,7 +284,7 @@ bash assets/repo/backups/一键备份.sh
|
|||
### Core Directories
|
||||
- **`assets/prompts/`**: 提示词库入口(指向云端表格)
|
||||
- **`assets/skills/`**: 扁平化技能库(详见 assets/skills/README.md)
|
||||
- **`assets/documents/`**: 知识库(05-哲学与方法论、00-基础指南、01-入门指南、02-方法论、03-实战)
|
||||
- **`assets/documents/`**: 知识库(principles、guides、case-studies)
|
||||
- **`assets/`**: 外部资源(在线表格)入口与使用说明
|
||||
- **`assets/repo/prompts-library/`**: Excel ↔ Markdown 转换工具
|
||||
- **`assets/repo/chat-vault/`**: AI 聊天记录保存工具
|
||||
|
|
|
|||
79
README.md
79
README.md
|
|
@ -31,19 +31,19 @@
|
|||
<!-- 资源直达 - 按重要性分组 -->
|
||||
<!-- 🔴 核心理念 (红色系) -->
|
||||
<p>
|
||||
<a href="./assets/documents/05-哲学与方法论/README.md"><img src="https://img.shields.io/badge/🔮_哲学方法论-底层协议-purple?style=for-the-badge" alt="哲学与方法论"></a>
|
||||
<a href="./assets/documents/01-入门指南/00-Vibe%20Coding%20哲学原理.md"><img src="https://img.shields.io/badge/🧠_核心哲学-必读-crimson?style=for-the-badge" alt="核心哲学"></a>
|
||||
<a href="./assets/documents/00-基础指南/胶水编程.md"><img src="https://img.shields.io/badge/🧬_胶水编程-银弹-red?style=for-the-badge" alt="胶水编程"></a>
|
||||
<a href="./assets/documents/02-方法论/图形化AI协作-Canvas白板驱动开发.md"><img src="https://img.shields.io/badge/🎨_Canvas白板-图形驱动-orange?style=for-the-badge" alt="Canvas白板驱动开发"></a>
|
||||
<a href="./assets/documents/01-入门指南/README.md"><img src="https://img.shields.io/badge/🚀_从零开始-新手入门-red?style=for-the-badge" alt="从零开始"></a>
|
||||
<a href="./assets/documents/00-基础指南/血的教训.md"><img src="https://img.shields.io/badge/🩸_血的教训-必看-red?style=for-the-badge" alt="血的教训"></a>
|
||||
<a href="./assets/documents/00-基础指南/语言层要素.md"><img src="https://img.shields.io/badge/📊_语言层要素-12层框架-gold?style=for-the-badge" alt="语言层要素"></a>
|
||||
<a href="./assets/documents/00-基础指南/常见坑汇总.md"><img src="https://img.shields.io/badge/🕳️_常见坑-避坑指南-yellow?style=for-the-badge" alt="常见坑汇总"></a>
|
||||
<a href="./assets/documents/00-基础指南/强前置条件约束.md"><img src="https://img.shields.io/badge/🚫_硬约束-铁律-darkred?style=for-the-badge" alt="强前置条件约束"></a>
|
||||
<a href="./assets/documents/principles/philosophy/README.md"><img src="https://img.shields.io/badge/🔮_哲学方法论-底层协议-purple?style=for-the-badge" alt="哲学与方法论"></a>
|
||||
<a href="./assets/documents/guides/getting-started/Vibe%20Coding%20哲学原理.md"><img src="https://img.shields.io/badge/🧠_核心哲学-必读-crimson?style=for-the-badge" alt="核心哲学"></a>
|
||||
<a href="./assets/documents/principles/fundamentals/胶水编程.md"><img src="https://img.shields.io/badge/🧬_胶水编程-银弹-red?style=for-the-badge" alt="胶水编程"></a>
|
||||
<a href="./assets/documents/guides/playbook/图形化AI协作-Canvas白板驱动开发.md"><img src="https://img.shields.io/badge/🎨_Canvas白板-图形驱动-orange?style=for-the-badge" alt="Canvas白板驱动开发"></a>
|
||||
<a href="./assets/documents/guides/getting-started/README.md"><img src="https://img.shields.io/badge/🚀_从零开始-新手入门-red?style=for-the-badge" alt="从零开始"></a>
|
||||
<a href="./assets/documents/principles/fundamentals/血的教训.md"><img src="https://img.shields.io/badge/🩸_血的教训-必看-red?style=for-the-badge" alt="血的教训"></a>
|
||||
<a href="./assets/documents/principles/fundamentals/语言层要素.md"><img src="https://img.shields.io/badge/📊_语言层要素-12层框架-gold?style=for-the-badge" alt="语言层要素"></a>
|
||||
<a href="./assets/documents/principles/fundamentals/常见坑汇总.md"><img src="https://img.shields.io/badge/🕳️_常见坑-避坑指南-yellow?style=for-the-badge" alt="常见坑汇总"></a>
|
||||
<a href="./assets/documents/principles/fundamentals/强前置条件约束.md"><img src="https://img.shields.io/badge/🚫_硬约束-铁律-darkred?style=for-the-badge" alt="强前置条件约束"></a>
|
||||
<a href="./assets/README.md"><img src="https://img.shields.io/badge/📡_信息源-聚合-teal?style=for-the-badge" alt="信息源聚合"></a>
|
||||
<a href="./assets/documents/00-基础指南/A%20Formalization%20of%20Recursive%20Self-Optimizing%20Generative%20Systems.md"><img src="https://img.shields.io/badge/📐_元方法论-递归优化-darkorange?style=for-the-badge" alt="元方法论"></a>
|
||||
<a href="./assets/documents/00-基础指南/编程之道.md"><img src="https://img.shields.io/badge/🧭_编程之道-道法术-orange?style=for-the-badge" alt="编程之道"></a>
|
||||
<a href="./assets/documents/03-实战/README.md"><img src="https://img.shields.io/badge/🎬_实战案例-项目实操-orange?style=for-the-badge" alt="实战案例"></a>
|
||||
<a href="./assets/documents/principles/fundamentals/A%20Formalization%20of%20Recursive%20Self-Optimizing%20Generative%20Systems.md"><img src="https://img.shields.io/badge/📐_元方法论-递归优化-darkorange?style=for-the-badge" alt="元方法论"></a>
|
||||
<a href="./assets/documents/principles/fundamentals/编程之道.md"><img src="https://img.shields.io/badge/🧭_编程之道-道法术-orange?style=for-the-badge" alt="编程之道"></a>
|
||||
<a href="./assets/documents/case-studies/README.md"><img src="https://img.shields.io/badge/🎬_实战案例-项目实操-orange?style=for-the-badge" alt="实战案例"></a>
|
||||
<a href="./assets/README.md"><img src="https://img.shields.io/badge/🛠️_工具集-速查-teal?style=for-the-badge" alt="工具集"></a>
|
||||
<a href="./assets/prompts/"><img src="https://img.shields.io/badge/💬_提示词-精选-purple?style=for-the-badge" alt="提示词精选"></a>
|
||||
<a href="./assets/skills/"><img src="https://img.shields.io/badge/⚡_Skills-技能大全-forestgreen?style=for-the-badge" alt="skills技能大全"></a>
|
||||
|
|
@ -66,7 +66,7 @@
|
|||
|
||||
## 🎲 前言
|
||||
|
||||
**这是一个不断生长和自我否定的项目,当下的一切经验和能力都可能因 AI 能力的变化而失去意义,所以请时刻保持以 AI 为主的思维,重视这次宇宙级的变革,所有的经验都可能失效,辩证的看🙏🙏🙏**,**Vibe Coding** 是一个与 AI 结对编程的终极工作流程,旨在帮助开发者丝滑地将想法变为现实。本指南详细介绍了从项目构思、技术选型、实施规划到具体开发、调试和扩展的全过程,强调以**规划驱动**和**模块化**,**索引构建**为核心(受限于模型上下文窗口而生成的解决策略),避免让 AI 失控导致项目混乱,Vibe Coding(氛围编程)是一种以自然语言驱动、让LLM生成大部分代码的开发方式,主张“先沉浸式做出能跑的东西”,以极低门槛快速产出原型但也伴随可控性与可靠性风险,由由计算机科学家 [Andrej Karpathy](https://x.com/karpathy) 首次提出。
|
||||
**这是一个不断生长和自我否定的项目,当下的一切经验和能力都可能因 AI 能力的变化而失去意义,所以请时刻保持以 AI 为主的思维,重视这次宇宙级的变革,所有的经验都可能失效,辩证的看🙏🙏🙏**,**Vibe Coding** 是一个与 AI 结对编程的终极工作流程,旨在帮助开发者丝滑地将想法变为现实。本指南详细介绍了从项目构思、技术选型、实施规划到具体开发、调试和扩展的全过程,强调以**规划驱动**和**模块化**,**索引构建**为核心(受限于模型上下文窗口而生成的解决策略),避免让 AI 失控导致项目混乱,Vibe Coding(氛围编程)是一种以自然语言驱动、让LLM生成大部分代码的开发方式,主张“先沉浸式做出能跑的东西”,以极低门槛快速产出原型但也伴随可控性与可靠性风险,由计算机科学家 [Andrej Karpathy](https://x.com/karpathy) 首次提出。
|
||||
|
||||
> **核心理念**: *规划就是一切。* 谨慎让 AI 全局自主规划,否则你的代码库会变成一团无法管理的乱麻。
|
||||
|
||||
|
|
@ -109,11 +109,11 @@
|
|||
|
||||
完全新手?按顺序完成以下步骤:
|
||||
|
||||
0. [00-Vibe Coding 哲学原理](./assets/documents/01-入门指南/00-Vibe%20Coding%20哲学原理.md) - 理解核心理念
|
||||
1. [01-网络环境配置](./assets/documents/01-入门指南/01-网络环境配置.md) - 配置网络访问
|
||||
2. [02-开发环境搭建](./assets/documents/01-入门指南/02-开发环境搭建.md) - 复制提示词给 AI,让 AI 指导你搭建环境
|
||||
3. [03-IDE配置](./assets/documents/01-入门指南/03-IDE配置.md) - 配置 VS Code 编辑器
|
||||
4. [04-OpenCode-CLI配置](./assets/documents/01-入门指南/04-OpenCode-CLI配置.md) - 免费 AI CLI 工具,支持 GLM-4.7/MiniMax M2.1 等模型
|
||||
0. [Vibe Coding 哲学原理](./assets/documents/guides/getting-started/Vibe%20Coding%20哲学原理.md) - 理解核心理念
|
||||
1. [网络环境配置](./assets/documents/guides/getting-started/网络环境配置.md) - 配置网络访问
|
||||
2. [开发环境搭建](./assets/documents/guides/getting-started/开发环境搭建.md) - 复制提示词给 AI,让 AI 指导你搭建环境
|
||||
3. [IDE配置](./assets/documents/guides/getting-started/IDE配置.md) - 配置 VS Code 编辑器
|
||||
4. [OpenCode-CLI配置](./assets/documents/guides/getting-started/OpenCode-CLI配置.md) - 免费 AI CLI 工具,支持 GLM-4.7/MiniMax M2.1 等模型
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -136,7 +136,7 @@
|
|||
|
||||
> 一句话:用“生成器/优化器”的递归闭环,构建一个能持续自我优化的 AI 系统。
|
||||
>
|
||||
> 延伸阅读:[A Formalization of Recursive Self-Optimizing Generative Systems](./assets/documents/00-基础指南/A%20Formalization%20of%20Recursive%20Self-Optimizing%20Generative%20Systems.md)
|
||||
> 延伸阅读:[A Formalization of Recursive Self-Optimizing Generative Systems](./assets/documents/principles/fundamentals/A%20Formalization%20of%20Recursive%20Self-Optimizing%20Generative%20Systems.md)
|
||||
|
||||
### 核心角色
|
||||
- **α-提示词(生成器)**:一个“母体”提示词,其唯一职责是生成其他提示词或技能。
|
||||
|
|
@ -166,7 +166,7 @@
|
|||
| 🧩 复杂性爆炸 | ✅ 每个模块都是久经考验的轮子 |
|
||||
| 🎓 门槛过高 | ✅ 你只需要描述"连接方式" |
|
||||
|
||||
👉 [深入了解胶水编程](./assets/documents/00-基础指南/胶水编程.md)
|
||||
👉 [深入了解胶水编程](./assets/documents/principles/fundamentals/胶水编程.md)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -187,7 +187,7 @@ Canvas方式:**代码 ⇄ 白板 ⇄ AI ⇄ 人类**,白板成为单一真
|
|||
|
||||
**核心理念**:图形是第一公民,代码是白板的序列化形式。
|
||||
|
||||
👉 [深入了解Canvas白板驱动开发](./assets/documents/02-方法论/图形化AI协作-Canvas白板驱动开发.md)
|
||||
👉 [深入了解Canvas白板驱动开发](./assets/documents/guides/playbook/图形化AI协作-Canvas白板驱动开发.md)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -208,7 +208,7 @@ Canvas方式:**代码 ⇄ 白板 ⇄ AI ⇄ 人类**,白板成为单一真
|
|||
|
||||
**核心突破**:AI 不再是孤立的,而是可以互相感知、通讯、控制的集群。
|
||||
|
||||
👉 [深入了解AI蜂群协作](./assets/documents/02-方法论/AI蜂群协作-tmux多Agent协作系统.md)
|
||||
👉 [深入了解AI蜂群协作](./assets/documents/guides/playbook/AI蜂群协作-tmux多Agent协作系统.md)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -229,7 +229,7 @@ Canvas方式:**代码 ⇄ 白板 ⇄ AI ⇄ 人类**,白板成为单一真
|
|||
|
||||
**核心理念**:哲学不是空谈,是可落地的工程方法。
|
||||
|
||||
👉 [深入了解哲学方法论工具箱](./assets/documents/05-哲学与方法论/README.md)
|
||||
👉 [深入了解哲学方法论工具箱](./assets/documents/principles/philosophy/README.md)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -241,6 +241,7 @@ Canvas方式:**代码 ⇄ 白板 ⇄ AI ⇄ 人类**,白板成为单一真
|
|||
## 🧭 经验
|
||||
|
||||
* **状态,变换;数据,函数;输入,处理,输出;抽象/收敛,展开;可解释性;层级;过程;全称/特称,肯定/否定**
|
||||
* **明确任务中的:目的,对象,约束**
|
||||
* **人下 AI 上**
|
||||
* **一切问题问 AI**
|
||||
* **目的主导:开发过程中的一切动作围绕"目的"展开**
|
||||
|
|
@ -310,12 +311,12 @@ Canvas方式:**代码 ⇄ 白板 ⇄ AI ⇄ 人类**,白板成为单一真
|
|||
* [**第三方系统提示词学习库**](https://github.com/x1xhlol/system-prompts-and-models-of-ai-tools): 用于学习和参考其他 AI 工具的系统提示词。
|
||||
* [**Skills 制作器**](https://github.com/yusufkaraaslan/Skill_Seekers): 可根据需求生成定制化 Skills 的工具。
|
||||
* [**元提示词**](https://docs.google.com/spreadsheets/d/1Ifk_dLF25ULSxcfGem1hXzJsi7_RBUNAki8SBCuvkJA/edit?gid=1254297203#gid=1254297203): 用于生成提示词的高级提示词。
|
||||
* [**通用项目架构模板**](./assets/documents/00-基础指南/通用项目架构模板.md): 可用于快速搭建标准化的项目目录结构。
|
||||
* [**通用项目架构模板**](./assets/documents/principles/fundamentals/通用项目架构模板.md): 可用于快速搭建标准化的项目目录结构。
|
||||
* [**元技能:Skills 的 Skills**](./assets/skills/skills-skills/SKILL.md): 用于生成 Skills 的元技能。
|
||||
* [**SOP 生成 Skill**](./assets/skills/sop-generator/SKILL.md): 将资料/需求整理为可执行 SOP 的技能。
|
||||
* [**tmux快捷键大全**](./assets/documents/02-方法论/tmux快捷键大全.md): tmux 的快捷键参考文档。
|
||||
* [**LazyVim快捷键大全**](./assets/documents/02-方法论/LazyVim快捷键大全.md): LazyVim 的快捷键参考文档。
|
||||
* [**手机远程 Vibe Coding**](./assets/documents/02-方法论/关于手机ssh任意位置链接本地计算机,基于frp实现的方法.md): 基于 frp 实现手机 SSH 远程控制本地电脑进行 Vibe Coding。
|
||||
* [**tmux快捷键大全**](./assets/documents/guides/playbook/tmux快捷键大全.md): tmux 的快捷键参考文档。
|
||||
* [**LazyVim快捷键大全**](./assets/documents/guides/playbook/LazyVim快捷键大全.md): LazyVim 的快捷键参考文档。
|
||||
* [**手机远程 Vibe Coding**](./assets/documents/guides/playbook/关于手机ssh任意位置链接本地计算机,基于frp实现的方法.md): 基于 frp 实现手机 SSH 远程控制本地电脑进行 Vibe Coding。
|
||||
|
||||
### 外部教程与资源
|
||||
|
||||
|
|
@ -329,14 +330,14 @@ Canvas方式:**代码 ⇄ 白板 ⇄ AI ⇄ 人类**,白板成为单一真
|
|||
|
||||
### 项目内部文档
|
||||
|
||||
* [**胶水编程 (Glue Coding)**](./assets/documents/00-基础指南/): 软件工程的圣杯与银弹,Vibe Coding 的终极进化形态。
|
||||
* [**胶水编程 (Glue Coding)**](./assets/documents/principles/fundamentals/): 软件工程的圣杯与银弹,Vibe Coding 的终极进化形态。
|
||||
* [**Chat Vault**](./assets/repo/chat-vault/): AI 聊天记录保存工具,支持 Codex/Kiro/Gemini/Claude CLI。
|
||||
* [**prompts-library 工具说明**](./assets/repo/prompts-library/): 支持 Excel 与 Markdown 格式互转,包含数百个精选提示词。
|
||||
* [**编程提示词集合**](https://docs.google.com/spreadsheets/d/1Ifk_dLF25ULSxcfGem1hXzJsi7_RBUNAki8SBCuvkJA/edit?gid=1254297203#gid=1254297203): 适用于 Vibe Coding 流程的专用提示词(云端表格)。
|
||||
* [**系统提示词构建原则**](./assets/documents/00-基础指南/系统提示词构建原则.md): 构建高效 AI 系统提示词的综合指南。
|
||||
* [**开发经验总结**](./assets/documents/00-基础指南/开发经验.md): 变量命名、文件结构、编码规范、架构原则等。
|
||||
* [**通用项目架构模板**](./assets/documents/00-基础指南/通用项目架构模板.md): 多种项目类型的标准目录结构。
|
||||
* [**Augment MCP 配置文档**](./assets/documents/02-方法论/auggie-mcp配置文档.md): Augment 上下文引擎配置说明。
|
||||
* [**系统提示词构建原则**](./assets/documents/principles/fundamentals/系统提示词构建原则.md): 构建高效 AI 系统提示词的综合指南。
|
||||
* [**开发经验总结**](./assets/documents/principles/fundamentals/开发经验.md): 变量命名、文件结构、编码规范、架构原则等。
|
||||
* [**通用项目架构模板**](./assets/documents/principles/fundamentals/通用项目架构模板.md): 多种项目类型的标准目录结构。
|
||||
* [**Augment MCP 配置文档**](./assets/documents/guides/playbook/auggie-mcp配置文档.md): Augment 上下文引擎配置说明。
|
||||
* [**系统提示词集合**](https://docs.google.com/spreadsheets/d/1Ifk_dLF25ULSxcfGem1hXzJsi7_RBUNAki8SBCuvkJA/edit?gid=1254297203#gid=1254297203): AI 开发的系统提示词,含多版本开发规范(云端表格)。
|
||||
* [**外部资源(在线表格)**](./assets/README.md): 外部资源的唯一真相源(按类型分表),本地 Markdown 保留为历史参考。
|
||||
|
||||
|
|
@ -382,11 +383,13 @@ Canvas方式:**代码 ⇄ 白板 ⇄ AI ⇄ 人类**,白板成为单一真
|
|||
│ │ ├── config.toml # Codex CLI 配置文件
|
||||
│ │ └── AGENTS.md # Codex/Agent 指南(本目录)
|
||||
│ ├── documents/ # 文档库
|
||||
│ │ ├── 05-哲学与方法论/ # 最高思想纲领与方法论
|
||||
│ │ ├── 00-基础指南/ # 核心原则与底层逻辑
|
||||
│ │ ├── 01-入门指南/ # 从零开始教程
|
||||
│ │ ├── 02-方法论/ # 具体工具与技巧
|
||||
│ │ └── 03-实战/ # 项目实战案例
|
||||
│ │ ├── principles/ # 原则与思想(fundamentals + philosophy)
|
||||
│ │ │ ├── fundamentals/ # 原 00-基础指南
|
||||
│ │ │ └── philosophy/ # 原 05-哲学与方法论
|
||||
│ │ ├── guides/ # 入门与方法(getting-started + playbook)
|
||||
│ │ │ ├── getting-started/ # 原 01-入门指南
|
||||
│ │ │ └── playbook/ # 原 02-方法论
|
||||
│ │ └── case-studies/ # 原 03-实战
|
||||
│ ├── prompts/ # 提示词库(指向云端表格)
|
||||
│ │ ├── README.md # 在线表格链接
|
||||
│ │ └── AGENTS.md # prompts/ 目录规则
|
||||
|
|
@ -453,7 +456,7 @@ assets/prompts/
|
|||
assets/skills/
|
||||
README.md # skills 总览与索引
|
||||
assets/documents/
|
||||
00-基础指南/代码组织.md, 00-基础指南/通用项目架构模板.md, 00-基础指南/开发经验.md, 00-基础指南/系统提示词构建原则.md 等知识库
|
||||
principles/fundamentals/*, principles/philosophy/*, guides/*, case-studies/* 等知识库
|
||||
assets/
|
||||
README.md # 外部资源(在线表格)唯一真相源入口
|
||||
assets/repo/backups/
|
||||
|
|
|
|||
|
|
@ -0,0 +1,9 @@
|
|||
# Config(`assets/config/`)
|
||||
|
||||
本目录用于集中存放“工具/开发环境配置”的仓库内基线,便于多人同步、审阅与回滚。
|
||||
|
||||
## Codex CLI
|
||||
|
||||
- 配置位置:`assets/config/.codex/`
|
||||
- 使用说明:`assets/config/.codex/README.md`
|
||||
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
# 🚀 入门指南
|
||||
|
||||
> 从零开始学习 Vibe Coding,配置环境
|
||||
|
||||
## 📚 学习路径
|
||||
|
||||
1. [Vibe Coding 哲学原理](./00-Vibe%20Coding%20哲学原理.md) - 理解核心理念
|
||||
2. [网络环境配置](./01-网络环境配置.md) - 配置网络访问
|
||||
3. [开发环境搭建](./02-开发环境搭建.md) - 搭建开发环境
|
||||
4. [IDE 配置](./03-IDE配置.md) - 配置编辑器
|
||||
|
||||
## 🔗 相关资源
|
||||
- [基础指南](../00-基础指南/) - 核心理念与方法论
|
||||
- [方法论](../02-方法论/) - 工具与经验
|
||||
- [实战](../03-实战/) - 动手实践项目
|
||||
|
|
@ -8,11 +8,13 @@
|
|||
|
||||
```
|
||||
assets/documents/
|
||||
├── 05-哲学与方法论/ # 最高思想纲领
|
||||
├── 00-基础指南/ # 核心原则与底层逻辑
|
||||
├── 01-入门指南/ # 从零开始教程
|
||||
├── 02-方法论/ # 具体工具与技巧
|
||||
└── 03-实战/ # 项目实战案例
|
||||
├── principles/ # 原则与思想(fundamentals + philosophy)
|
||||
│ ├── fundamentals/ # 原 00-基础指南
|
||||
│ └── philosophy/ # 原 05-哲学与方法论
|
||||
├── guides/ # 入门与方法(getting-started + playbook)
|
||||
│ ├── getting-started/ # 原 01-入门指南
|
||||
│ └── playbook/ # 原 02-方法论
|
||||
└── case-studies/ # 原 03-实战
|
||||
```
|
||||
|
||||
## 操作规范
|
||||
|
|
@ -25,11 +27,10 @@ assets/documents/
|
|||
|
||||
### 禁止
|
||||
- 删除现有文档(除非明确要求)
|
||||
- 修改目录编号前缀规则
|
||||
- 大规模重命名/移动文件导致链接失效(如必须调整,需同步更新引用)
|
||||
- 大规模重命名/移动文件导致链接失效(如必须调整,需同步更新引用)
|
||||
|
||||
## 命名规范
|
||||
|
||||
- 文件名使用中文
|
||||
- 使用 Markdown 格式
|
||||
- 编号前缀保持一致性
|
||||
- 目录名使用简短英文(便于跨平台与链接稳定)
|
||||
|
|
|
|||
|
|
@ -6,32 +6,32 @@
|
|||
|
||||
```
|
||||
assets/documents/
|
||||
├── 05-哲学与方法论/ # 最高思想纲领,底层逻辑
|
||||
├── 00-基础指南/ # 核心理念,胶水编程,方法论
|
||||
├── 01-入门指南/ # 从零开始,环境配置
|
||||
├── 02-方法论/ # 工具教程,开发经验
|
||||
└── 03-实战/ # 项目实战经验
|
||||
├── principles/ # 原则与思想(fundamentals + philosophy)
|
||||
│ ├── fundamentals/ # 原 00-基础指南
|
||||
│ └── philosophy/ # 原 05-哲学与方法论
|
||||
├── guides/ # 入门与方法(getting-started + playbook)
|
||||
│ ├── getting-started/ # 原 01-入门指南
|
||||
│ └── playbook/ # 原 02-方法论
|
||||
└── case-studies/ # 原 03-实战
|
||||
```
|
||||
|
||||
## 🚀 快速导航
|
||||
|
||||
| 目录 | 说明 | 适合人群 |
|
||||
|:---|:---|:---|
|
||||
| [05-哲学与方法论](./05-哲学与方法论/) | 思想纲领、认识论工具 | 架构师与深度开发者 |
|
||||
| [00-基础指南](./00-基础指南/) | 胶水编程、核心理念 | 理解本质 |
|
||||
| [01-入门指南](./01-入门指南/) | 环境配置、从零开始 | 新手入门 |
|
||||
| [02-方法论](./02-方法论/) | 工具教程、开发经验 | 提升效率 |
|
||||
| [03-实战](./03-实战/) | 项目经验、案例复盘 | 动手实践 |
|
||||
| [principles](./principles/) | 原则与思想(基础 + 哲学) | 架构师与深度开发者 |
|
||||
| [guides](./guides/) | 入门与方法(上手 + 工具与经验) | 新手入门与效率提升 |
|
||||
| [case-studies](./case-studies/) | 项目经验、案例复盘 | 动手实践 |
|
||||
|
||||
## 📖 推荐学习路径
|
||||
|
||||
1. **思维** → [05-哲学与方法论](./05-哲学与方法论/README.md)
|
||||
2. **理念** → [胶水编程](./00-基础指南/胶水编程.md)
|
||||
3. **入门** → [Vibe Coding 哲学原理](./01-入门指南/00-Vibe%20Coding%20哲学原理.md)
|
||||
3. **配置** → [开发环境搭建](./01-入门指南/02-开发环境搭建.md)
|
||||
4. **工具** → [tmux 快捷键](./02-方法论/tmux快捷键大全.md)
|
||||
5. **远程** → [VS Code Remote Tunnel(WSL)](./02-方法论/REMOTE_TUNNEL_GUIDE.md)
|
||||
5. **实践** → [项目实战经验](./03-实战/)
|
||||
1. **思维** → [philosophy](./principles/philosophy/README.md)
|
||||
2. **理念** → [胶水编程](./principles/fundamentals/胶水编程.md)
|
||||
3. **入门** → [Vibe Coding 哲学原理](./guides/getting-started/Vibe%20Coding%20哲学原理.md)
|
||||
4. **配置** → [开发环境搭建](./guides/getting-started/开发环境搭建.md)
|
||||
5. **工具** → [tmux 快捷键](./guides/playbook/tmux快捷键大全.md)
|
||||
6. **远程** → [VS Code Remote Tunnel(WSL)](./guides/playbook/REMOTE_TUNNEL_GUIDE.md)
|
||||
7. **实践** → [项目实战经验](./case-studies/)
|
||||
|
||||
## 🔗 相关资源
|
||||
|
||||
|
|
|
|||
|
|
@ -6,12 +6,12 @@
|
|||
|
||||
| 项目 | 说明 |
|
||||
|:---|:---|
|
||||
| [fate-engine-dev](./fate-engine-dev/) | Fate Engine 开发记录 |
|
||||
| [polymarket-dev](./polymarket-dev/) | Polymarket 数据分析 |
|
||||
| [telegram-dev](./telegram-dev/) | Telegram Bot 开发 |
|
||||
| [web-app](./web-app/) | Web 应用开发 |
|
||||
|
||||
## 🔗 相关资源
|
||||
- [基础指南](../00-基础指南/) - 核心理念与方法论
|
||||
- [入门指南](../01-入门指南/) - 环境配置
|
||||
- [方法论](../02-方法论/) - 工具与经验
|
||||
- [基础指南](../principles/fundamentals/) - 核心理念与方法论
|
||||
- [入门指南](../guides/getting-started/) - 环境配置
|
||||
- [方法论](../guides/playbook/) - 工具与经验
|
||||
- [外部资源(在线表格)](../../README.md) - 外部资源唯一真相源入口
|
||||
|
|
@ -11,8 +11,8 @@ Polymarket 预测市场数据的采集、分析和可视化,包含 K 线图 AS
|
|||
| 文件 | 说明 |
|
||||
|:---|:---|
|
||||
| [ascii可视化-prompt.md](./ascii可视化-prompt.md) | ASCII 字符绘制 K 线图的提示词 |
|
||||
| [prompt-system-bazi-kline.md](./prompt-system-bazi-kline.md) | 系统提示词:K 线分析 |
|
||||
| [prompt-user-bazi-kline.md](./prompt-user-bazi-kline.md) | 用户提示词:K 线分析 |
|
||||
| [prompt-system-bazi-kline.md](../fate-engine-dev/prompt-system-bazi-kline.md) | 系统提示词:K 线分析 |
|
||||
| [prompt-user-bazi-kline.md](../fate-engine-dev/prompt-user-bazi-kline.md) | 用户提示词:K 线分析 |
|
||||
| [胶水开发要求-prompt.md](./胶水开发要求-prompt.md) | 胶水代码开发规范提示词 |
|
||||
| [完整性检查-prompt.md](./完整性检查-prompt.md) | 代码完整性检查提示词 |
|
||||
| [复查-prompt.md](./复查-prompt.md) | 代码复查提示词 |
|
||||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
> 使用方法:复制下方对应你 IDE 的提示词,粘贴到任意 AI 对话框,AI 会一步步指导你完成配置。
|
||||
|
||||
**前置条件**:请先完成 [02-开发环境搭建](./02-开发环境搭建.md)
|
||||
**前置条件**:请先完成 [开发环境搭建](./开发环境搭建.md)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -0,0 +1,15 @@
|
|||
# 🚀 入门指南
|
||||
|
||||
> 从零开始学习 Vibe Coding,配置环境
|
||||
|
||||
## 📚 学习路径
|
||||
|
||||
1. [Vibe Coding 哲学原理](./Vibe%20Coding%20哲学原理.md) - 理解核心理念
|
||||
2. [网络环境配置](./网络环境配置.md) - 配置网络访问
|
||||
3. [开发环境搭建](./开发环境搭建.md) - 搭建开发环境
|
||||
4. [IDE 配置](./IDE配置.md) - 配置编辑器
|
||||
|
||||
## 🔗 相关资源
|
||||
- [基础指南](../../principles/fundamentals/) - 核心理念与方法论
|
||||
- [方法论](../playbook/) - 工具与经验
|
||||
- [实战](../../case-studies/) - 动手实践项目
|
||||
|
|
@ -26,4 +26,4 @@
|
|||
|
||||
## 下一步
|
||||
|
||||
→ [04-OpenCode-CLI配置](./04-OpenCode-CLI配置.md) - 获得你的"一"
|
||||
→ [OpenCode-CLI配置](./OpenCode-CLI配置.md) - 获得你的"一"
|
||||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
> 使用方法:复制下方对应你设备的提示词,粘贴到任意 AI 对话框(ChatGPT、Claude、Gemini 网页版等),AI 会一步步指导你完成配置。
|
||||
|
||||
**前置条件**:请先完成 [01-网络环境配置](./01-网络环境配置.md)
|
||||
**前置条件**:请先完成 [网络环境配置](./网络环境配置.md)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -155,4 +155,4 @@ alias g='gemini --yolo'
|
|||
|
||||
环境搭建完成后,继续下一步:
|
||||
|
||||
→ [03-IDE配置](./03-IDE配置.md) - 配置 VS Code 开发环境
|
||||
→ [IDE配置](./IDE配置.md) - 配置 VS Code 开发环境
|
||||
|
|
@ -110,4 +110,4 @@ export http_proxy=http://127.0.0.1:7890
|
|||
|
||||
## 下一步
|
||||
|
||||
网络配置完成后,继续阅读 [02-开发环境搭建](./02-开发环境搭建.md)。
|
||||
网络配置完成后,继续阅读 [开发环境搭建](./开发环境搭建.md)。
|
||||
|
|
@ -19,10 +19,10 @@
|
|||
|
||||
## 🛠️ 开发经验
|
||||
|
||||
- [开发经验](./开发经验.md) - 变量命名、文件结构、编码规范
|
||||
- [开发经验](../../principles/fundamentals/开发经验.md) - 变量命名、文件结构、编码规范
|
||||
- [Vibe Coding 经验收集](./vibe-coding-经验收集.md) - 社区经验汇总
|
||||
|
||||
## 🔗 相关资源
|
||||
- [基础指南](../00-基础指南/) - 核心理念与方法论
|
||||
- [入门指南](../01-入门指南/) - 从零开始
|
||||
- [实战](../03-实战/) - 动手实践
|
||||
- [基础指南](../../principles/fundamentals/) - 核心理念与方法论
|
||||
- [入门指南](../getting-started/) - 从零开始
|
||||
- [实战](../../case-studies/) - 动手实践
|
||||
|
|
@ -188,7 +188,7 @@ Canvas方式:
|
|||
### 🔗 相关资源
|
||||
|
||||
- [Canvas白板生成提示词](https://docs.google.com/spreadsheets/d/1Ifk_dLF25ULSxcfGem1hXzJsi7_RBUNAki8SBCuvkJA/edit?gid=1777853069#gid=1777853069&range=A1) - 自动生成架构白板的完整提示词
|
||||
- [白板驱动开发系统提示词(在线提示词库入口)](../../prompts/README.md) - 系统提示词已迁移到云端表格
|
||||
- [白板驱动开发系统提示词(在线提示词库入口)](../../../prompts/README.md) - 系统提示词已迁移到云端表格
|
||||
- [Obsidian Canvas 官方文档](https://obsidian.md/canvas)
|
||||
- [胶水编程](../00-基础指南/胶水编程.md) - 能抄不写,能连不造
|
||||
- [通用项目架构模板](../00-基础指南/通用项目架构模板.md) - 标准化目录结构
|
||||
- [胶水编程](../../principles/fundamentals/胶水编程.md) - 能抄不写,能连不造
|
||||
- [通用项目架构模板](../../principles/fundamentals/通用项目架构模板.md) - 标准化目录结构
|
||||
|
|
@ -26,6 +26,6 @@
|
|||
- [开发经验](./开发经验.md) - 实战经验总结
|
||||
|
||||
## 🔗 相关资源
|
||||
- [入门指南](../01-入门指南/) - 从零开始
|
||||
- [方法论](../02-方法论/) - 工具与经验
|
||||
- [实战](../03-实战/) - 动手实践
|
||||
- [入门指南](../../guides/getting-started/) - 从零开始
|
||||
- [方法论](../../guides/playbook/) - 工具与经验
|
||||
- [实战](../../case-studies/) - 动手实践
|
||||
|
|
@ -135,7 +135,7 @@ nvm use 18
|
|||
|
||||
| 问题 | 原因 | 解决方案 |
|
||||
|:---|:---|:---|
|
||||
| GitHub 访问慢/超时 | 网络限制 | 配置代理,参考 [网络环境配置](../从零开始vibecoding/01-网络环境配置.md) |
|
||||
| GitHub 访问慢/超时 | 网络限制 | 配置代理,参考 [网络环境配置](../../guides/getting-started/网络环境配置.md) |
|
||||
| API 调用失败 | 网络/Key 问题 | 检查代理、API Key 是否有效 |
|
||||
| 终端不走代理 | 代理配置不全 | 设置环境变量(见下方) |
|
||||
| SSL 证书错误 | 代理/时间问题 | 检查系统时间,或临时关闭 SSL 验证 |
|
||||
|
|
@ -266,7 +266,7 @@ git config --global https.proxy http://127.0.0.1:7890
|
|||
|:---|:---|:---|
|
||||
| 代码越写越乱 | 没有架构设计 | 先画架构图,再写代码 |
|
||||
| 改一处坏多处 | 耦合太紧 | 拆分模块,定义清晰接口 |
|
||||
| 不知道代码放哪 | 目录结构混乱 | 参考 [通用项目架构模板](../模板与资源/通用项目架构模板.md) |
|
||||
| 不知道代码放哪 | 目录结构混乱 | 参考 [通用项目架构模板](./通用项目架构模板.md) |
|
||||
| 重复代码太多 | 没有抽象 | 提取公共函数/组件 |
|
||||
| 状态管理混乱 | 全局状态滥用 | 用状态管理库,单向数据流 |
|
||||
| 配置散落各处 | 没有统一管理 | 集中到 config 文件或环境变量 |
|
||||
|
|
@ -151,8 +151,8 @@ AI 不再需要"发明"任何东西。它只需要:
|
|||
## 📚 延伸阅读
|
||||
|
||||
- [语言层要素](./语言层要素.md) - 看懂 100% 代码必须掌握的 12 层要素
|
||||
- [胶水开发提示词(在线提示词库入口)](../../prompts/README.md)
|
||||
- [项目实战:polymarket-dev](../03-实战/polymarket-dev/)
|
||||
- [胶水开发提示词(在线提示词库入口)](../../../prompts/README.md)
|
||||
- [项目实战:polymarket-dev](../../case-studies/polymarket-dev/)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -22,8 +22,8 @@ AI 不再是孤立的,而是可以互相感知、通讯、控制的集群。
|
|||
|
||||
## 详细文档
|
||||
|
||||
👉 [深入了解AI蜂群协作](../02-方法论/AI蜂群协作-tmux多Agent协作系统.md)
|
||||
👉 [深入了解AI蜂群协作](../../guides/playbook/AI蜂群协作-tmux多Agent协作系统.md)
|
||||
|
||||
## 相关资源
|
||||
|
||||
- [tmux快捷键大全](../02-方法论/tmux快捷键大全.md)
|
||||
- [tmux快捷键大全](../../guides/playbook/tmux快捷键大全.md)
|
||||
|
|
@ -826,8 +826,8 @@ The correct command uses the local `cli/package_skill.py` in the repository root
|
|||
- **[CHANGELOG.md](CHANGELOG.md)** - Release history and v2.0.0 details **UPDATED!**
|
||||
- **[FUTURE_RELEASES.md](FUTURE_RELEASES.md)** - Roadmap for v2.1.0+ **NEW!**
|
||||
- **[FLEXIBLE_ROADMAP.md](FLEXIBLE_ROADMAP.md)** - Complete task catalog (134 tasks)
|
||||
- **[NEXT_TASKS.md](NEXT_TASKS.md)** - What to work on next
|
||||
- **[TODO.md](TODO.md)** - Current focus
|
||||
- **[ROADMAP.md](ROADMAP.md)** - What to work on next
|
||||
- **[FLEXIBLE_ROADMAP.md](FLEXIBLE_ROADMAP.md)** - Current focus
|
||||
- **[STRUCTURE.md](STRUCTURE.md)** - Repository structure
|
||||
|
||||
## Notes for Claude Code
|
||||
|
|
|
|||
|
|
@ -247,4 +247,4 @@ ADDITIONAL REQUIREMENTS:
|
|||
|
||||
- [README.md](../README.md) - Main documentation
|
||||
- [CLAUDE.md](CLAUDE.md) - Architecture guide
|
||||
- [doc_scraper.py](../doc_scraper.py) - Main scraping tool
|
||||
- [doc_scraper.py](../src/skill_seekers/cli/doc_scraper.py) - Main scraping tool
|
||||
|
|
|
|||
|
|
@ -583,9 +583,9 @@ After successful setup:
|
|||
|
||||
## Getting Help
|
||||
|
||||
- **Documentation**: See [mcp/README.md](../mcp/README.md)
|
||||
- **Documentation**: See [src/skill_seekers/mcp/README.md](../src/skill_seekers/mcp/README.md)
|
||||
- **Issues**: [GitHub Issues](https://github.com/yusufkaraaslan/Skill_Seekers/issues)
|
||||
- **Examples**: See [.github/ISSUES_TO_CREATE.md](../.github/ISSUES_TO_CREATE.md) for test cases
|
||||
- **Examples**: See [TEST_MCP_IN_CLAUDE_CODE.md](TEST_MCP_IN_CLAUDE_CODE.md) for test cases
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -314,7 +314,7 @@ When building PDF-based skills, images will be:
|
|||
|
||||
See diagram below for the complete API flow:
|
||||
|
||||

|
||||
> 图示提示:上游文档引用了 `assets/images/api_flow.png`,但该文件未包含在当前仓库镜像中。
|
||||
|
||||
The diagram shows...
|
||||
```
|
||||
|
|
|
|||
|
|
@ -332,9 +332,9 @@ Once MCP integration works:
|
|||
|
||||
## Reference
|
||||
|
||||
- **Full Setup Guide:** [docs/MCP_SETUP.md](docs/MCP_SETUP.md)
|
||||
- **MCP Documentation:** [mcp/README.md](mcp/README.md)
|
||||
- **Main README:** [README.md](README.md)
|
||||
- **Full Setup Guide:** [MCP_SETUP.md](MCP_SETUP.md)
|
||||
- **MCP Documentation:** [src/skill_seekers/mcp/README.md](../src/skill_seekers/mcp/README.md)
|
||||
- **Main README:** [README.md](../README.md)
|
||||
- **Setup Script:** `./setup_mcp.sh`
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -581,10 +581,10 @@ For API-based enhancement (requires Anthropic API key):
|
|||
|
||||
## Documentation
|
||||
|
||||
- **Full Setup Guide**: [docs/MCP_SETUP.md](../docs/MCP_SETUP.md)
|
||||
- **Main README**: [README.md](../README.md)
|
||||
- **Usage Guide**: [docs/USAGE.md](../docs/USAGE.md)
|
||||
- **Testing Guide**: [docs/TESTING.md](../docs/TESTING.md)
|
||||
- **Full Setup Guide**: [docs/MCP_SETUP.md](../../../docs/MCP_SETUP.md)
|
||||
- **Main README**: [README.md](../../../README.md)
|
||||
- **Usage Guide**: [docs/USAGE.md](../../../docs/USAGE.md)
|
||||
- **Testing Guide**: [docs/TESTING.md](../../../docs/TESTING.md)
|
||||
|
||||
## Support
|
||||
|
||||
|
|
@ -593,4 +593,4 @@ For API-based enhancement (requires Anthropic API key):
|
|||
|
||||
## License
|
||||
|
||||
MIT License - See [LICENSE](../LICENSE) for details
|
||||
MIT License - See [LICENSE](../../../LICENSE) for details
|
||||
|
|
|
|||
|
|
@ -0,0 +1,10 @@
|
|||
# 贡献指南
|
||||
|
||||
欢迎贡献!
|
||||
|
||||
## 如何贡献
|
||||
|
||||
1. 修复 Bug / 改进功能:请在 `README.md` 的“快速开始/使用方式”验证脚本可运行。
|
||||
2. 新增功能:请同时补充最小示例与必要的依赖说明。
|
||||
3. 提交 PR:描述改动内容、使用方式与验证步骤。
|
||||
|
||||
|
|
@ -157,7 +157,7 @@ XHS-image-to-PDF-conversion/
|
|||
|
||||
## 📜 许可证
|
||||
|
||||
本项目采用 [MIT](LICENSE) 许可证。
|
||||
本项目采用 [MIT](https://opensource.org/licenses/MIT) 许可证。
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@
|
|||
<p>
|
||||
<a href="https://github.com/tukuaiai/prompt-library/actions/workflows/sync.yml"><img src="https://img.shields.io/github/actions/workflow/status/tukuaiai/prompt-library/sync.yml?style=for-the-badge" alt="构建状态"></a>
|
||||
<a href="https://github.com/tukuaiai/prompt-library/releases"><img src="https://img.shields.io/github/v/release/tukuaiai/prompt-library?style=for-the-badge" alt="最新版本"></a>
|
||||
<a href="LICENSE"><img src="https://img.shields.io/github/license/tukuaiai/prompt-library?style=for-the-badge" alt="许可证"></a>
|
||||
<a href="https://github.com/tukuaiai/prompt-library/blob/main/LICENSE"><img src="https://img.shields.io/github/license/tukuaiai/prompt-library?style=for-the-badge" alt="许可证"></a>
|
||||
<a href="https://github.com/tukuaiai/prompt-library"><img src="https://img.shields.io/github/languages/top/tukuaiai/prompt-library?style=for-the-badge" alt="主要语言"></a>
|
||||
<a href="https://github.com/tukuaiai/prompt-library"><img src="https://img.shields.io/github/languages/code-size/tukuaiai/prompt-library?style=for-the-badge" alt="代码大小"></a>
|
||||
</p>
|
||||
|
|
@ -214,7 +214,7 @@ gantt
|
|||
|
||||
我们热烈欢迎各种形式的贡献!如果您对本项目有任何想法或建议,请随时开启一个 [Issue](https://github.com/tukuaiai/prompt-library/issues) 或提交一个 [Pull Request](https://github.com/tukuaiai/prompt-library/pulls)。
|
||||
|
||||
在您开始之前,请花点时间阅读我们的 [**贡献指南 (CONTRIBUTING.md)**](CONTRIBUTING.md) 和 [**行为准则 (CODE_OF_CONDUCT.md)**](CODE_OF_CONDUCT.md)。
|
||||
在您开始之前,请花点时间阅读我们的 [**贡献指南 (CONTRIBUTING.md)**](https://github.com/tukuaiai/prompt-library/blob/main/CONTRIBUTING.md) 和 [**行为准则 (CODE_OF_CONDUCT.md)**](https://github.com/tukuaiai/prompt-library/blob/main/CODE_OF_CONDUCT.md)。
|
||||
|
||||
### ✨ 贡献者们
|
||||
|
||||
|
|
@ -241,7 +241,7 @@ gantt
|
|||
|
||||
## 📜 许可证
|
||||
|
||||
本项目采用 [MIT](LICENSE) 许可证。
|
||||
本项目采用 [MIT](https://github.com/tukuaiai/prompt-library/blob/main/LICENSE) 许可证。
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -17008,17 +17008,17 @@ XX 局
|
|||
- 具有知识性、可读性与教育性
|
||||
- 在文章结束时, 思考该文章的最核心关键词, 插入一个如下形式的链接内容:
|
||||
|
||||
不要有反斜线,不要用代码块,使用 Unsplash api (source.unsplash.com<PUT YOUR QUERY HERE>)
|
||||
不要有反斜线,不要用代码块,使用 Unsplash api(`https://source.unsplash.com/<PUT YOUR QUERY HERE>`)
|
||||
|
||||
例如:
|
||||
|
||||
- 如果思考该段落的核心关键词为"hero", 那就插入如下内容:
|
||||
|
||||
[](source.unsplash.com%C3%97900?hero)
|
||||
[](https://source.unsplash.com/900x900?hero)
|
||||
|
||||
- 如果思考该段落的核心关键词为"fire", 那就插入如下内容:
|
||||
|
||||
[](source.unsplash.com%C3%97900?fire)
|
||||
[](https://source.unsplash.com/900x900?fire)
|
||||
|
||||
## Initializatoin:
|
||||
|
||||
|
|
|
|||
|
|
@ -569,7 +569,7 @@ class PromptLibrarySyncer:
|
|||
# 生成版本链接
|
||||
links = []
|
||||
for col, filename in sorted(versions.items()):
|
||||
links.append(f"[v{col}](./{filename})")
|
||||
links.append(f"v{col}: ./{filename}")
|
||||
|
||||
links_str = " / ".join(links)
|
||||
f.write(f"| {row_num} | {title} | {len(versions)} | {links_str} |\n")
|
||||
|
|
@ -674,7 +674,7 @@ class PromptLibrarySyncer:
|
|||
f.write("- 列号: 表示版本号 (1=原始版本, 2+=迭代版本)\n\n")
|
||||
|
||||
f.write("## 🔄 同步信息\n\n")
|
||||
f.write(f"- 数据源: [Google Sheets]({self._get_sheet_url()})\n")
|
||||
f.write(f"- 数据源: Google Sheets ({self._get_sheet_url()})\n")
|
||||
f.write("- 同步方式: GitHub Actions / 手动\n")
|
||||
f.write("- 同步频率: 每日 / 手动触发\n\n")
|
||||
|
||||
|
|
@ -1344,4 +1344,4 @@ pytest tests/
|
|||
2. **版本管理**: 实现a/b/c版本命名规范
|
||||
3. **工具集成**: 考虑集成OpenAI优化API
|
||||
4. **社区建设**: 利用社交媒体进行推广和用户反馈收集
|
||||
5. **支持机制**: 建立可持续的项目支持渠道
|
||||
5. **支持机制**: 建立可持续的项目支持渠道
|
||||
|
|
|
|||
|
|
@ -34,6 +34,6 @@ canvas-dev/
|
|||
|
||||
## 相关资源
|
||||
|
||||
- [Canvas白板驱动开发详解](../../documents/02-方法论/图形化AI协作-Canvas白板驱动开发.md)
|
||||
- [Canvas白板驱动开发详解](../../documents/guides/playbook/图形化AI协作-Canvas白板驱动开发.md)
|
||||
- [Canvas开发工作流](../../workflow/canvas-dev/)
|
||||
- [元技能: skills-skills](../skills-skills/SKILL.md)
|
||||
|
|
|
|||
|
|
@ -208,7 +208,7 @@ Canvas:代码 ⇄ 白板 ⇄ AI ⇄ 人类(白板为单一真相源)
|
|||
|
||||
- [AI架构总师完整提示词](../../workflow/canvas-dev/Obsidian%20Canvas%20AI驱动的项目架构洞察与生成引擎.md) - 最新最完整的提示词
|
||||
- [Canvas驱动开发完整工作流](../../workflow/canvas-dev/workflow.md) - 15步完整流程
|
||||
- [Canvas白板驱动开发详解](../../documents/02-方法论/图形化AI协作-Canvas白板驱动开发.md) - 方法论详解
|
||||
- [Canvas白板驱动开发详解](../../documents/guides/playbook/图形化AI协作-Canvas白板驱动开发.md) - 方法论详解
|
||||
- [白板驱动开发系统提示词(在线提示词库入口)](../../prompts/README.md) - 系统提示词已迁移到云端表格
|
||||
- [Obsidian Canvas 官方文档](https://obsidian.md/canvas)
|
||||
- `references/index.md` - 本地参考文档导航
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@
|
|||
|
||||
| 文档 | 路径 | 说明 |
|
||||
|:---|:---|:---|
|
||||
| Canvas白板驱动开发详解 | `../../../documents/02-方法论/图形化AI协作-Canvas白板驱动开发.md` | 方法论详解 |
|
||||
| Canvas白板驱动开发详解 | `../../../documents/guides/playbook/图形化AI协作-Canvas白板驱动开发.md` | 方法论详解 |
|
||||
| 白板驱动开发系统提示词(在线提示词库入口) | `../../../prompts/README.md` | 系统提示词已迁移到云端表格 |
|
||||
| Canvas JSON 规范 | [canvas-json-spec.md](./canvas-json-spec.md) | Obsidian Canvas JSON 格式 |
|
||||
|
||||
|
|
@ -63,4 +63,4 @@
|
|||
|
||||
- [Obsidian Canvas 官方文档](https://obsidian.md/canvas)
|
||||
- [Obsidian 下载](https://obsidian.md/download)
|
||||
- [胶水编程](../../../documents/00-基础指南/胶水编程.md) - 能抄不写,能连不造
|
||||
- [胶水编程](../../../documents/principles/fundamentals/胶水编程.md) - 能抄不写,能连不造
|
||||
|
|
|
|||
|
|
@ -157,7 +157,7 @@ jobs:
|
|||
|
||||
## 相关资源
|
||||
|
||||
- [Canvas白板驱动开发详解](../../../documents/02-方法论/图形化AI协作-Canvas白板驱动开发.md)
|
||||
- [Canvas白板驱动开发详解](../../../documents/guides/playbook/图形化AI协作-Canvas白板驱动开发.md)
|
||||
- [架构分析提示词](../../../workflow/canvas-dev/prompts/01-架构分析.md)
|
||||
- [白板驱动编码提示词](../../../workflow/canvas-dev/prompts/02-白板驱动编码.md)
|
||||
- [白板同步检查提示词](../../../workflow/canvas-dev/prompts/03-白板同步检查.md)
|
||||
|
|
|
|||
|
|
@ -0,0 +1,7 @@
|
|||
# CCXT Manual(外链)
|
||||
|
||||
本仓库未内置 CCXT 的完整 Manual 原文;请使用官方文档:
|
||||
|
||||
- Docs(推荐):https://docs.ccxt.com/
|
||||
- GitHub Wiki Manual:https://github.com/ccxt/ccxt/wiki/Manual
|
||||
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
# CCXT Manual(外链)
|
||||
|
||||
本仓库未在 `assets/skills/ccxt/references/` 内维护 CCXT Manual 的镜像文件;请使用官方文档:
|
||||
|
||||
- Docs(推荐):https://docs.ccxt.com/
|
||||
- GitHub Wiki Manual:https://github.com/ccxt/ccxt/wiki/Manual
|
||||
|
||||
|
|
@ -4,16 +4,16 @@ Welcome to the Capabilities section of the Claude Cookbooks! This directory cont
|
|||
|
||||
## Guides
|
||||
|
||||
- **[Classification with Claude](./classification/guide.ipynb)**: Discover how Claude can revolutionize classification tasks, especially in scenarios with complex business rules and limited training data. This guide walks you through data preparation, prompt engineering with retrieval-augmented generation (RAG), testing, and evaluation.
|
||||
- **[Classification with Claude](https://github.com/anthropics/claude-cookbooks/tree/main/capabilities/classification)**: Discover how Claude can revolutionize classification tasks, especially in scenarios with complex business rules and limited training data. This guide walks you through data preparation, prompt engineering with retrieval-augmented generation (RAG), testing, and evaluation.
|
||||
|
||||
- **[Retrieval Augmented Generation with Claude](./retrieval_augmented_generation/guide.ipynb)**: Learn how to enhance Claude's capabilities with domain-specific knowledge using RAG. This guide demonstrates how to build a RAG system from scratch, optimize its performance, and create an evaluation suite. You'll learn how techniques like summary indexing and re-ranking can significantly improve precision, recall, and overall accuracy in question-answering tasks.
|
||||
- **[Retrieval Augmented Generation with Claude](https://github.com/anthropics/claude-cookbooks/tree/main/capabilities/retrieval_augmented_generation)**: Learn how to enhance Claude's capabilities with domain-specific knowledge using RAG. This guide demonstrates how to build a RAG system from scratch, optimize its performance, and create an evaluation suite. You'll learn how techniques like summary indexing and re-ranking can significantly improve precision, recall, and overall accuracy in question-answering tasks.
|
||||
|
||||
- **[Retrieval Augmented Generation with Contextual Embeddings](./contextual-embeddings/guide.ipynb)**: Learn how to use a new technique to improve the performance of your RAG system. In traditional RAG, documents are typically split into smaller chunks for efficient retrieval. While this approach works well for many applications, it can lead to problems when individual chunks lack sufficient context. Contextual Embeddings solve this problem by adding relevant context to each chunk before embedding. You'll learn how to use contextual embeddings with semantic search, BM25 search, and reranking to improve performance.
|
||||
- **[Retrieval Augmented Generation with Contextual Embeddings](https://github.com/anthropics/claude-cookbooks/tree/main/capabilities/contextual-embeddings)**: Learn how to use a new technique to improve the performance of your RAG system. In traditional RAG, documents are typically split into smaller chunks for efficient retrieval. While this approach works well for many applications, it can lead to problems when individual chunks lack sufficient context. Contextual Embeddings solve this problem by adding relevant context to each chunk before embedding. You'll learn how to use contextual embeddings with semantic search, BM25 search, and reranking to improve performance.
|
||||
|
||||
- **[Summarization with Claude](./summarization/guide.ipynb)**: Explore Claude's ability to summarize and synthesize information from multiple sources. This guide covers a variety of summarization techniques, including multi-shot, domain-based, and chunking methods, as well as strategies for handling long-form content and multiple documents. We also explore evaluating summaries, which can be a balance of art, subjectivity, and the right approach!
|
||||
- **[Summarization with Claude](https://github.com/anthropics/claude-cookbooks/tree/main/capabilities/summarization)**: Explore Claude's ability to summarize and synthesize information from multiple sources. This guide covers a variety of summarization techniques, including multi-shot, domain-based, and chunking methods, as well as strategies for handling long-form content and multiple documents. We also explore evaluating summaries, which can be a balance of art, subjectivity, and the right approach!
|
||||
|
||||
- **[Text-to-SQL with Claude](./text_to_sql/guide.ipynb)**: This guide covers how to generate complex SQL queries from natural language using prompting techniques, self-improvement, and RAG. We'll also explore how to evaluate and improve the accuracy of generated SQL queries, with evals that test for syntax, data correctness, row count, and more.
|
||||
- **[Text-to-SQL with Claude](https://github.com/anthropics/claude-cookbooks/tree/main/capabilities/text_to_sql)**: This guide covers how to generate complex SQL queries from natural language using prompting techniques, self-improvement, and RAG. We'll also explore how to evaluate and improve the accuracy of generated SQL queries, with evals that test for syntax, data correctness, row count, and more.
|
||||
|
||||
## Getting Started
|
||||
|
||||
To get started with these guides, simply navigate to the desired guide's directory and follow the instructions provided in the `guide.ipynb` file. Each guide is self-contained and includes all the necessary code, data, and evaluation scripts to reproduce the examples and experiments.
|
||||
To get started with these guides, simply navigate to the desired guide's directory and follow the instructions provided in the `guide.ipynb` file. Each guide is self-contained and includes all the necessary code, data, and evaluation scripts to reproduce the examples and experiments.
|
||||
|
|
|
|||
|
|
@ -15,6 +15,6 @@ This repository contains example minimal implementations of common agent workflo
|
|||
## Getting Started
|
||||
See the Jupyter notebooks for detailed examples:
|
||||
|
||||
- [Basic Workflows](basic_workflows.ipynb)
|
||||
- [Evaluator-Optimizer Workflow](evaluator_optimizer.ipynb)
|
||||
- [Orchestrator-Workers Workflow](orchestrator_workers.ipynb)
|
||||
- [Basic Workflows](https://github.com/anthropics/claude-cookbooks/blob/main/patterns/agents/basic_workflows.ipynb)
|
||||
- [Evaluator-Optimizer Workflow](https://github.com/anthropics/claude-cookbooks/blob/main/patterns/agents/evaluator_optimizer.ipynb)
|
||||
- [Orchestrator-Workers Workflow](https://github.com/anthropics/claude-cookbooks/blob/main/patterns/agents/orchestrator_workers.ipynb)
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ Authentication method for CoinGecko Public API (Demo plan users)
|
|||
|
||||
* Demo API Key is only available for CoinGecko Public Demo API Plan, the root URL for CoinGecko Public Demo API must be `https://api.coingecko.com/api/v3/`.
|
||||
* ⚠️ You are recommended to store the API key securely in your own backend and use a proxy to insert the key into the request URL.
|
||||
* The authentication method below is for CoinGecko Public Demo API only. For **paid plan users with Pro-API key**, please refer to [this page](/reference/authentication) instead.
|
||||
* The authentication method below is for CoinGecko Public Demo API only. For **paid plan users with Pro-API key**, please refer to [this page](https://docs.coingecko.com/reference/authentication) instead.
|
||||
* User Guide: [How to sign up for CoinGecko Demo API and generate an API key?](https://support.coingecko.com/hc/en-us/articles/21880397454233)
|
||||
* It's highly recommended to use the **Headers method** when making API requests for better security. Using query string parameters can risk exposing your API key.
|
||||
</Note>
|
||||
|
|
@ -33,7 +33,7 @@ If this is your first time using the Demo API key, you can supply API Key to the
|
|||
1. Header (Recommended): `x-cg-demo-api-key`
|
||||
2. Query String Parameter: `x_cg_demo_api_key`
|
||||
|
||||
| Authentication Method | Example using [Ping](/v3.0.1/reference/ping-server) Endpoint |
|
||||
| Authentication Method | Example using [Ping](https://docs.coingecko.com/v3.0.1/reference/ping-server) Endpoint |
|
||||
| ---------------------- | ------------------------------------------------------------------------------------------ |
|
||||
| Header (cURL) | `curl -X GET "https://api.coingecko.com/api/v3/ping" -H "x-cg-demo-api-key: YOUR_API_KEY"` |
|
||||
| Query String Parameter | `https://api.coingecko.com/api/v3/ping?x_cg_demo_api_key=YOUR_API_KEY` |
|
||||
|
|
@ -42,7 +42,7 @@ If this is your first time using the Demo API key, you can supply API Key to the
|
|||
|
||||
* Each request made to any endpoint counts as a single call (1 call = 1 credit).
|
||||
* Your monthly credit & rate limit are determined by the paid plan to which you subscribe. For more details, please refer to this [page](https://www.coingecko.com/en/api/pricing).
|
||||
* To check the API usage, please go to the [developer dashboard](https://www.coingecko.com/en/developers/dashboard) or follow the guide [here](/v3.0.1/reference/setting-up-your-api-key#4-api-usage-report).
|
||||
* To check the API usage, please go to the [developer dashboard](https://www.coingecko.com/en/developers/dashboard) or follow the guide [here](https://docs.coingecko.com/v3.0.1/reference/setting-up-your-api-key#4-api-usage-report).
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ If this is your first time using the Pro API key, you can supply API Key to the
|
|||
1. Header (Recommended): `x-cg-pro-api-key`
|
||||
2. Query String Parameter: `x_cg_pro_api_key`
|
||||
|
||||
| Authentication Method | Example using [Ping](/reference/ping-server) Endpoint |
|
||||
| Authentication Method | Example using [Ping](https://docs.coingecko.com/reference/ping-server) Endpoint |
|
||||
| ---------------------- | --------------------------------------------------------------------------------------------- |
|
||||
| Header (cURL) | `curl -X GET "https://pro-api.coingecko.com/api/v3/ping" -H "x-cg-pro-api-key: YOUR_API_KEY"` |
|
||||
| Query String Parameter | `https://pro-api.coingecko.com/api/v3/ping?x_cg_pro_api_key=YOUR_API_KEY` |
|
||||
|
|
@ -90,7 +90,7 @@ You can now use the Pro-API key (exclusive to any paid plan subscriber) to call
|
|||
* When using the CG Pro API to access onchain DEX data, include the `/onchain` endpoint path in the request.
|
||||
</Note>
|
||||
|
||||
| Authentication Method | Example using [Simple Token Price](/reference/onchain-simple-price) Endpoint |
|
||||
| Authentication Method | Example using [Simple Token Price](https://docs.coingecko.com/reference/onchain-simple-price) Endpoint |
|
||||
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Header (cURL) | `curl -X GET "<https://pro-api.coingecko.com/api/v3/onchain/simple/networks/eth/token_price/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2>" -H "x-cg-pro-api-key: YOUR_API_KEY"` |
|
||||
| Query String Parameter | `https://pro-api.coingecko.com/api/v3/onchain/simple/networks/eth/token_price/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2?x_cg_pro_api_key=YOUR_API_KEY` |
|
||||
|
|
@ -102,7 +102,7 @@ You can now use the Pro-API key (exclusive to any paid plan subscriber) to call
|
|||
* Unsuccessful Requests (Status 4xx, 5xx, etc) will not count towards credit deduction.
|
||||
* Regardless of the HTTP status code returned (including 4xx and 5xx errors), all API requests will count towards your **minute rate limit**.
|
||||
* Your monthly credit & rate limit are determined by the paid plan to which you subscribe. For more details, please refer to this [page](https://www.coingecko.com/en/api/pricing).
|
||||
* To check the API usage, please go to the [developer dashboard](https://www.coingecko.com/en/developers/dashboard) or follow the guide [here](/reference/setting-up-your-api-key#4-api-usage-report)
|
||||
* To check the API usage, please go to the [developer dashboard](https://www.coingecko.com/en/developers/dashboard) or follow the guide [here](https://docs.coingecko.com/reference/setting-up-your-api-key#4-api-usage-report)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -140,8 +140,8 @@ Source: https://docs.coingecko.com/docs/setting-up-your-api-key
|
|||
## 2. Making API Request
|
||||
|
||||
* **Root URLs:**
|
||||
* Pro API: `https://pro-api.coingecko.com/api/v3/`, refer to [Pro API Authentication](/reference/authentication).
|
||||
* Demo API: `https://api.coingecko.com/api/v3/`, refer to [Demo API Authentication](/v3.0.1/reference/authentication).
|
||||
* Pro API: `https://pro-api.coingecko.com/api/v3/`, refer to [Pro API Authentication](https://docs.coingecko.com/reference/authentication).
|
||||
* Demo API: `https://api.coingecko.com/api/v3/`, refer to [Demo API Authentication](https://docs.coingecko.com/v3.0.1/reference/authentication).
|
||||
* **Example using the `/ping` endpoint:**
|
||||
|
||||
* Pro API: `https://pro-api.coingecko.com/api/v3/ping?x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ v3.0.1/reference/api-reference/coingecko-demo.json get /coins/markets
|
|||
This endpoint allows you to **query all the supported coins with price, market cap, volume and market related data**
|
||||
|
||||
* You can retrieve specific coins using their unique `ids`, `names`, or `symbols` instead of returning the whole list.
|
||||
* To filter results based on the coin's category, use the `category` param (refer to [`/coins/categories/list`](/v3.0.1/reference/coins-categories-list) for available categories).
|
||||
* To filter results based on the coin's category, use the `category` param (refer to [`/coins/categories/list`](https://docs.coingecko.com/v3.0.1/reference/coins-categories-list) for available categories).
|
||||
* Use the `per_page` and `page` params to manage the number of results you receive and navigate through the data.
|
||||
</Tip>
|
||||
|
||||
|
|
@ -79,7 +79,7 @@ This endpoint allows you to **get the historical chart data within certain time
|
|||
|
||||
* You may obtain the asset platform and contract address via several ways:
|
||||
* refers to respective coin page and find 'contract address'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint (`include platform = true`).
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint (`include platform = true`).
|
||||
</Tip>
|
||||
|
||||
* You may leave the interval params as empty for automatic granularity:
|
||||
|
|
@ -107,8 +107,8 @@ Source: https://docs.coingecko.com/reference/categories-list
|
|||
reference/api-reference/onchain-pro.json get /categories
|
||||
This endpoint allows you to **query all the supported categories on GeckoTerminal**
|
||||
|
||||
* You can retrieve pools or tokens of a specific category with this endpoint: [Pools by Category ID](/reference/pools-category).
|
||||
* GeckoTerminal categories are different from [CoinGecko categories](/reference/coins-categories-list).
|
||||
* You can retrieve pools or tokens of a specific category with this endpoint: [Pools by Category ID](https://docs.coingecko.com/reference/pools-category).
|
||||
* GeckoTerminal categories are different from [CoinGecko categories](https://docs.coingecko.com/reference/coins-categories-list).
|
||||
</Tip>
|
||||
|
||||
* This endpoint returns 50 categories per page.
|
||||
|
|
@ -471,7 +471,7 @@ This endpoint allows you to **query the historical data (price, market cap, 24hr
|
|||
|
||||
* You may obtain the coin ID (API ID) via several ways:
|
||||
* refers to respective coin page and find 'API ID'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to Google Sheets [here](https://docs.google.com/spreadsheets/d/1wTTuxXt8n9q7C4NDXqQpI3wpKu1_5bGVmP9Xz0XGSyU/edit?usp=sharing).
|
||||
</Tip>
|
||||
|
||||
|
|
@ -493,7 +493,7 @@ This endpoint allows you to **get the historical chart data including time in UN
|
|||
|
||||
* You may obtain the asset platform and contract address via several ways:
|
||||
* refers to respective coin page and find 'contract address'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint (`include platform = true`).
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint (`include platform = true`).
|
||||
</Tip>
|
||||
|
||||
* You may leave the interval as empty for automatic granularity:
|
||||
|
|
@ -536,7 +536,7 @@ v3.0.1/reference/api-reference/onchain-demo.json get /networks/{network}/tokens/
|
|||
This endpoint allows you to **query specific token data based on the provided token contract address on a network**
|
||||
|
||||
* You may add values such as `top_pools` in the include param to include top pools along with the pools information.
|
||||
* If you would like to query token information such as socials, websites, description and etc. You can go to this endpoint [`/networks/{network}/tokens/{address}/info`](/v3.0.1/reference/token-info-contract-address) instead.
|
||||
* If you would like to query token information such as socials, websites, description and etc. You can go to this endpoint [`/networks/{network}/tokens/{address}/info`](https://docs.coingecko.com/v3.0.1/reference/token-info-contract-address) instead.
|
||||
</Tip>
|
||||
|
||||
* If the token's market cap is not verified by the team, the API response will return `null` for its market cap value, even though it has a displayed value on GeckoTerminal, which might not be accurate as it often matches the Fully Diluted Valuation (FDV).
|
||||
|
|
@ -572,12 +572,12 @@ Source: https://docs.coingecko.com/v3.0.1/reference/pool-token-info-contract-add
|
|||
v3.0.1/reference/api-reference/onchain-demo.json get /networks/{network}/pools/{pool_address}/info
|
||||
This endpoint allows you to **query pool metadata (base and quote token details, image, socials, websites, description, contract address, etc.) based on a provided pool contract address on a network**
|
||||
|
||||
* If you would like to query pool data such as price, transactions, volume and etc. You can go to this endpoint [`/networks/{network}/pools/{address}`](/v3.0.1/reference/pool-address) instead.
|
||||
* If you would like to query pool data such as price, transactions, volume and etc. You can go to this endpoint [`/networks/{network}/pools/{address}`](https://docs.coingecko.com/v3.0.1/reference/pool-address) instead.
|
||||
* Cache/Update frequency: every 60 seconds.
|
||||
* Learn more about GT score [here](https://support.coingecko.com/hc/en-us/articles/38381394237593-What-is-GT-Score-How-is-GT-Score-calculated).
|
||||
* Metadata (image, websites, description, socials) may be sourced on-chain and is not vetted by the CoinGecko team. If you wish to get metadata reviewed by CoinGecko team, you may use the following endpoints:
|
||||
* [Coin Data by ID](/v3.0.1/reference/coins-id)
|
||||
* [Coin Data by Token Address](/v3.0.1/reference/coins-contract-address)
|
||||
* [Coin Data by ID](https://docs.coingecko.com/v3.0.1/reference/coins-id)
|
||||
* [Coin Data by Token Address](https://docs.coingecko.com/v3.0.1/reference/coins-contract-address)
|
||||
</Tip>
|
||||
|
||||
* `holders` data is currently in Beta, with ongoing improvements to data quality, coverage, and update frequency.
|
||||
|
|
@ -634,7 +634,7 @@ This endpoint allows you to **get the historical chart data of a coin including
|
|||
|
||||
* You may obtain the coin ID (API ID) via several ways:
|
||||
* refers to respective coin page and find 'API ID'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to google sheets [here](https://docs.google.com/spreadsheets/d/1wTTuxXt8n9q7C4NDXqQpI3wpKu1_5bGVmP9Xz0XGSyU/edit?usp=sharing).
|
||||
* You may use tools like [epoch converter ](https://www.epochconverter.com) to convert human readable date to UNIX timestamp.
|
||||
</Tip>
|
||||
|
|
@ -662,7 +662,7 @@ This endpoint allows you to **query the prices of one or more coins by using the
|
|||
|
||||
* You may obtain the coin ID (API ID) via several ways:
|
||||
* refers to respective coin page and find 'API ID'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to Google Sheets [here](https://docs.google.com/spreadsheets/d/1wTTuxXt8n9q7C4NDXqQpI3wpKu1_5bGVmP9Xz0XGSyU/edit?usp=sharing).
|
||||
* You can retrieve specific coins using their unique `ids`, `names`, or `symbols`.
|
||||
* You may flag to include more data such as market cap, 24hr volume, 24hr change, last updated time etc.
|
||||
|
|
@ -713,12 +713,12 @@ This endpoint allows you to **query all the metadata (image, websites, socials,
|
|||
<Warning>
|
||||
### Notice
|
||||
|
||||
* Please note that the `twitter_followers` data field will no longer be supported by our API starting on May 15, 2025. Please refer to [changelog](/changelog#upcoming-change-notice%3A-removal-of-twitter-followers-data) for more details.
|
||||
* Please note that the `twitter_followers` data field will no longer be supported by our API starting on May 15, 2025. Please refer to [changelog](https://docs.coingecko.com/changelog#upcoming-change-notice%3A-removal-of-twitter-followers-data) for more details.
|
||||
</Warning>
|
||||
|
||||
* You may obtain the asset platform and contract address via several ways:
|
||||
* refers to respective coin page and find 'contract address'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint (`include platform = true`).
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint (`include platform = true`).
|
||||
</Tip>
|
||||
|
||||
* Coin descriptions may include newline characters represented as `\r\n` (escape sequences), which may require processing for proper formatting.
|
||||
|
|
@ -738,13 +738,13 @@ This endpoint allows you to **query all the metadata (image, websites, socials,
|
|||
|
||||
* You may obtain the coin `id` (API ID) via several ways:
|
||||
* refers to respective coin page and find "API ID".
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to Google Sheets [here](https://docs.google.com/spreadsheets/d/1wTTuxXt8n9q7C4NDXqQpI3wpKu1_5bGVmP9Xz0XGSyU/edit?usp=sharing).
|
||||
* You may also flag to include more data such as tickers, market data, community data, developer data and sparkline.
|
||||
* You may refer to `last_updated` in the endpoint response to check whether the price is stale.
|
||||
</Tip>
|
||||
|
||||
* Tickers are limited to 100 items, to get more tickers, please go to [/coins/{id}/tickers](/v3.0.1/reference/coins-id-tickers).
|
||||
* Tickers are limited to 100 items, to get more tickers, please go to [/coins/{id}/tickers](https://docs.coingecko.com/v3.0.1/reference/coins-id-tickers).
|
||||
* Coin descriptions may include newline characters represented as `\r\n` (escape sequences), which may require processing for proper formatting.
|
||||
* When `dex_pair_format=symbol`, the DEX pair `base` and `target` are displayed in symbol format (e.g. `WETH`, `USDC`) instead of as contract addresses.
|
||||
* Cache/Update Frequency:
|
||||
|
|
@ -769,7 +769,7 @@ Source: https://docs.coingecko.com/docs/1-get-data-by-id-or-address
|
|||
|
||||
## Methods to query price & market data of coins
|
||||
|
||||
Using [/simple/price](/reference/simple-price) endpoint as example:
|
||||
Using [/simple/price](https://docs.coingecko.com/reference/simple-price) endpoint as example:
|
||||
|
||||
* `https://pro-api.coingecko.com/api/v3/simple/price?ids=bitcoin&vs_currencies=usd&x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
|
|
@ -777,7 +777,7 @@ Using [/simple/price](/reference/simple-price) endpoint as example:
|
|||
|
||||
**How to obtain Coin ID aka API ID?** There are 3 options:
|
||||
|
||||
* Use [/coins/list](/reference/coins-list) endpoint, example of responses:
|
||||
* Use [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint, example of responses:
|
||||
|
||||
<CodeGroup>
|
||||
|
||||
|
|
@ -793,7 +793,7 @@ Using [/simple/price](/reference/simple-price) endpoint as example:
|
|||
|
||||
### b. Contract Address
|
||||
|
||||
Other than using Coin ID, you may also query price & market data of a coin using contract address, using [/simple/token\_price/\{id](/reference/simple-token-price)} endpoint as example:
|
||||
Other than using Coin ID, you may also query price & market data of a coin using contract address, using [/simple/token\_price/\{id](https://docs.coingecko.com/reference/simple-token-price)} endpoint as example:
|
||||
|
||||
* `https://pro-api.coingecko.com/api/v3/simple/token_price/ethereum?contract_addresses=0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48&vs_currencies=usd&x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
|
|
@ -805,7 +805,7 @@ There are 3 parameters values required to apply for this endpoint:
|
|||
|
||||
**How to obtain Coins/Tokens Contract Address**
|
||||
|
||||
* Use [/coins/list](/reference/coins-list) endpoint (`include_platform=true`), example of responses:
|
||||
* Use [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint (`include_platform=true`), example of responses:
|
||||
<CodeGroup>
|
||||
|
||||
</CodeGroup>
|
||||
|
|
@ -840,11 +840,11 @@ CoinGecko API data supports all major fiat currencies and some famous crypto cur
|
|||
| Cryptocurrency | Ether | `eth` |
|
||||
| Cryptocurrency | Binance Coin | `bnb` |
|
||||
|
||||
For full list of supported currencies, please go to [/simple/supported\_vs\_currencies](/reference/simple-supported-currencies) endpoint
|
||||
For full list of supported currencies, please go to [/simple/supported\_vs\_currencies](https://docs.coingecko.com/reference/simple-supported-currencies) endpoint
|
||||
|
||||
## Other way to obtain coin prices & market data
|
||||
|
||||
Using [/coins/market ](/reference/coins-markets) endpoint as example to query prices and market data of coins in bulk
|
||||
Using [/coins/market ](https://docs.coingecko.com/reference/coins-markets) endpoint as example to query prices and market data of coins in bulk
|
||||
|
||||
* `https://pro-api.coingecko.com/api/v3/coins/markets?vs_currency=usd&order=market_cap_desc&per_page=100&page=1&x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
|
|
@ -871,7 +871,7 @@ Example 1 (unknown):
|
|||
|
||||
### b. Contract Address
|
||||
|
||||
Other than using Coin ID, you may also query price & market data of a coin using contract address, using [/simple/token\_price/\{id](/reference/simple-token-price)} endpoint as example:
|
||||
Other than using Coin ID, you may also query price & market data of a coin using contract address, using [/simple/token\_price/\{id](https://docs.coingecko.com/reference/simple-token-price)} endpoint as example:
|
||||
|
||||
* `https://pro-api.coingecko.com/api/v3/simple/token_price/ethereum?contract_addresses=0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48&vs_currencies=usd&x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
|
|
@ -883,7 +883,7 @@ There are 3 parameters values required to apply for this endpoint:
|
|||
|
||||
**How to obtain Coins/Tokens Contract Address**
|
||||
|
||||
* Use [/coins/list](/reference/coins-list) endpoint (`include_platform=true`), example of responses:
|
||||
* Use [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint (`include_platform=true`), example of responses:
|
||||
<CodeGroup>
|
||||
```
|
||||
|
||||
|
|
@ -937,9 +937,9 @@ You can get Exchange and NFT data just like how you get the coins data:
|
|||
|
||||
| Type | Coins | NFTs | Exchanges | Derivatives |
|
||||
| ---------------------- | -------------------------------------------------------------- | ------------------------------------------------------------ | ---------------------------------------------------------------------- | ---------------------------------------------------------------------- |
|
||||
| Get Full List with IDs | [/coins/list](/reference/coins-list) | [/nfts/list](/reference/nfts-list) | [/exchanges/list](/reference/exchanges-list) | [/derivatives/exchanges/list](/reference/derivatives-exchanges-list) |
|
||||
| Get latest market data | [/coins/\{id}](/reference/coins-id) | [/nfts/\{id}](/reference/nfts-id) | [/exchanges/\{id}](/reference/exchanges-id) | [/derivatives/exchanges/\{id}](/reference/derivatives-exchanges-id) |
|
||||
| Get Historical Data | [/coins/\{id}/market\_chart](/reference/coins-id-market-chart) | [/nfts/\{id}/market\_chart](/reference/nfts-id-market-chart) | [/exchanges/\{id}/volume\_chart](/reference/exchanges-id-volume-chart) | [/exchanges/\{id}/volume\_chart](/reference/exchanges-id-volume-chart) |
|
||||
| Get Full List with IDs | [/coins/list](https://docs.coingecko.com/reference/coins-list) | [/nfts/list](https://docs.coingecko.com/reference/nfts-list) | [/exchanges/list](https://docs.coingecko.com/reference/exchanges-list) | [/derivatives/exchanges/list](https://docs.coingecko.com/reference/derivatives-exchanges-list) |
|
||||
| Get latest market data | [/coins/\{id}](https://docs.coingecko.com/reference/coins-id) | [/nfts/\{id}](https://docs.coingecko.com/reference/nfts-id) | [/exchanges/\{id}](https://docs.coingecko.com/reference/exchanges-id) | [/derivatives/exchanges/\{id}](https://docs.coingecko.com/reference/derivatives-exchanges-id) |
|
||||
| Get Historical Data | [/coins/\{id}/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart) | [/nfts/\{id}/market\_chart](https://docs.coingecko.com/reference/nfts-id-market-chart) | [/exchanges/\{id}/volume\_chart](https://docs.coingecko.com/reference/exchanges-id-volume-chart) | [/exchanges/\{id}/volume\_chart](https://docs.coingecko.com/reference/exchanges-id-volume-chart) |
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -954,7 +954,7 @@ This endpoint allows you to **query one or more token prices using their token c
|
|||
|
||||
* You may obtain the asset platform and contract address via several ways:
|
||||
* refers to respective coin page and find 'contract address'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint (`include platform = true`).
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint (`include platform = true`).
|
||||
* You may flag to include more data such as market cap, 24hr volume, 24hr change, last updated time etc.
|
||||
</Tip>
|
||||
|
||||
|
|
@ -1004,9 +1004,9 @@ Source: https://docs.coingecko.com/reference/pools-category
|
|||
reference/api-reference/onchain-pro.json get /categories/{category_id}/pools
|
||||
This endpoint allows you to **query all the pools based on the provided category ID**
|
||||
|
||||
* You can retrieve full list of categories id via this endpoint: [Categories List](/reference/categories-list).
|
||||
* You can retrieve full list of categories id via this endpoint: [Categories List](https://docs.coingecko.com/reference/categories-list).
|
||||
* You can retrieve tokens of a specific category, by flagging `include=base_token`.
|
||||
* GeckoTerminal categories are different from [CoinGecko categories](/reference/coins-categories-list).
|
||||
* GeckoTerminal categories are different from [CoinGecko categories](https://docs.coingecko.com/reference/coins-categories-list).
|
||||
</Tip>
|
||||
|
||||
* Trending rankings are determined by a combination of factors:
|
||||
|
|
@ -1100,10 +1100,10 @@ We will gradually improve the Websocket and expand the feature limits. Please sh
|
|||
|
||||
| Websocket Channel | Channel Code | Details |
|
||||
| ------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------- |
|
||||
| [OnchainSimpleTokenPrice](/websocket/onchainsimpletokenprice) | G1 | Subscribe to receive real-time price updates for tokens, as seen on GeckoTerminal.com |
|
||||
| [CGSimplePrice](/websocket/cgsimpleprice) | C1 | Subscribe to receive real-time price updates for tokens, as seen on CoinGecko.com |
|
||||
| [OnchainTrade](/websocket/wss-onchain-trade) | G2 | Subscribe to receive real-time transaction updates for pools, as seen on GeckoTerminal.com |
|
||||
| [OnchainOHLCV](/websocket/wssonchainohlcv/) | G3 | Subscribe to receive real-time OHLCV (Open, High, Low, Close, Volume) for pools, as seen on GeckoTerminal.com |
|
||||
| [OnchainSimpleTokenPrice](https://docs.coingecko.com/websocket/onchainsimpletokenprice) | G1 | Subscribe to receive real-time price updates for tokens, as seen on GeckoTerminal.com |
|
||||
| [CGSimplePrice](https://docs.coingecko.com/websocket/cgsimpleprice) | C1 | Subscribe to receive real-time price updates for tokens, as seen on CoinGecko.com |
|
||||
| [OnchainTrade](https://docs.coingecko.com/websocket/wss-onchain-trade) | G2 | Subscribe to receive real-time transaction updates for pools, as seen on GeckoTerminal.com |
|
||||
| [OnchainOHLCV](https://docs.coingecko.com/websocket/wssonchainohlcv/) | G3 | Subscribe to receive real-time OHLCV (Open, High, Low, Close, Volume) for pools, as seen on GeckoTerminal.com |
|
||||
| (More coming soon!) | | |
|
||||
|
||||
<Note>
|
||||
|
|
@ -1168,7 +1168,7 @@ This Websocket channel allows you to subscribe to real-time updates of token tra
|
|||
|
||||
**Update Frequency**: as fast as 0.1s, for actively traded pools.
|
||||
|
||||
**Tips**: use this Rest API endpoint [Top Pools by Token Address](/reference/top-pools-contract-address) to obtain contract address of the most liquid pool.
|
||||
**Tips**: use this Rest API endpoint [Top Pools by Token Address](https://docs.coingecko.com/reference/top-pools-contract-address) to obtain contract address of the most liquid pool.
|
||||
|
||||
| | Field | Type | Description | Example |
|
||||
| ---- | ------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------- | -------------------------- |
|
||||
|
|
@ -1315,9 +1315,9 @@ This endpoint allows you to **get the OHLC chart (Open, High, Low, Close) of a c
|
|||
|
||||
* You may obtain the coin ID (API ID) via several ways:
|
||||
* refers to respective coin page and find 'API ID'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to google sheets [here](https://docs.google.com/spreadsheets/d/1wTTuxXt8n9q7C4NDXqQpI3wpKu1_5bGVmP9Xz0XGSyU/edit?usp=sharing).
|
||||
* For historical chart data with better granularity, you may consider using [/coins/\{id}/market\_chart](/v3.0.1/reference/coins-id-market-chart) endpoint.
|
||||
* For historical chart data with better granularity, you may consider using [/coins/\{id}/market\_chart](https://docs.coingecko.com/v3.0.1/reference/coins-id-market-chart) endpoint.
|
||||
</Tip>
|
||||
|
||||
* The timestamp displayed in the payload (response) indicates the end (or close) time of the OHLC data.
|
||||
|
|
@ -1519,40 +1519,40 @@ Discover the common use cases of CoinGecko API by our users
|
|||
|
||||
## 1. Get Coins Logo Images
|
||||
|
||||
* Use [/coins/id](/reference/coins-id) endpoint.
|
||||
* Use [/coins/id](https://docs.coingecko.com/reference/coins-id) endpoint.
|
||||
|
||||
* This endpoint can be used to query other coin's metadata like: links, categories, contract address, community, description in different languages and many more.
|
||||
* Coin descriptions may include newline characters represented as `\r\n` (escape sequences), which may require processing for proper formatting.
|
||||
|
||||
* Use [Token Info by Token Address](/reference/token-info-contract-address) endpoint to get metadata of tokens listed on GeckoTerminal.com.
|
||||
* Use [Token Info by Token Address](https://docs.coingecko.com/reference/token-info-contract-address) endpoint to get metadata of tokens listed on GeckoTerminal.com.
|
||||
|
||||
## 2. Best Endpoint for Latest Crypto Price
|
||||
|
||||
* Use [/simple/price](/reference/simple-price) endpoint.
|
||||
* Use [/simple/price](https://docs.coingecko.com/reference/simple-price) endpoint.
|
||||
* This endpoint can be used to query other market data like market cap, 24-hour trading volume and 24-hour price change percentage.
|
||||
|
||||
## 3. Get All Trading Pairs (Tickers) of a Coin
|
||||
|
||||
* Use [/coins/id/tickers](/reference/coins-id-tickers) endpoint.
|
||||
* Use [/coins/id/tickers](https://docs.coingecko.com/reference/coins-id-tickers) endpoint.
|
||||
|
||||
## 4. Get Trading Pairs of Specific Coins from a Specific Exchange
|
||||
|
||||
* Use[ /coins/id/tickers](/reference/coins-id-tickers) endpoint by supplying specific exchange ID.
|
||||
* Use[ /coins/id/tickers](https://docs.coingecko.com/reference/coins-id-tickers) endpoint by supplying specific exchange ID.
|
||||
|
||||
## 5. Building Telegram Bot for Latest Coin Listings
|
||||
|
||||
* Use [/coins/list/new](/reference/coins-list-new) endpoint.
|
||||
* Use [/coins/list/new](https://docs.coingecko.com/reference/coins-list-new) endpoint.
|
||||
|
||||
## 6. Get List of Coins Under Specific Category
|
||||
|
||||
* For CoinGecko [categories](https://www.coingecko.com/en/categories), use [/coins/markets](/reference/coins-markets) endpoint by supplying specific category.
|
||||
* For GeckoTerminal [categories](https://www.geckoterminal.com/category), use [Pools by Category ID](/reference/pools-category) endpoint by supplying specific category.
|
||||
* For CoinGecko [categories](https://www.coingecko.com/en/categories), use [/coins/markets](https://docs.coingecko.com/reference/coins-markets) endpoint by supplying specific category.
|
||||
* For GeckoTerminal [categories](https://www.geckoterminal.com/category), use [Pools by Category ID](https://docs.coingecko.com/reference/pools-category) endpoint by supplying specific category.
|
||||
|
||||
## 7. Identify DEX Decentralized Exchanges
|
||||
|
||||
* Use [/exchanges/list](/reference/exchanges-list) endpoint to get full list of exchanges with ID on CoinGecko.
|
||||
* Use [/exchanges/list](https://docs.coingecko.com/reference/exchanges-list) endpoint to get full list of exchanges with ID on CoinGecko.
|
||||
|
||||
* Use [/exchanges/id](/reference/exchanges-id) to find out whether the exchange is centralized or decentralized.
|
||||
* Use [/exchanges/id](https://docs.coingecko.com/reference/exchanges-id) to find out whether the exchange is centralized or decentralized.
|
||||
|
||||
* Example of responses (using Uniswap V3 as example) :
|
||||
|
||||
|
|
@ -1564,7 +1564,7 @@ Since Uniswap is a DEX, therefore it shows `"centralized": false`
|
|||
|
||||
## 8. Get Bitcoin Dominance Data (BTC.D)
|
||||
|
||||
* Use [/global ](/reference/crypto-global)endpoint.
|
||||
* Use [/global ](https://docs.coingecko.com/reference/crypto-global)endpoint.
|
||||
|
||||
* Example of responses:
|
||||
|
||||
|
|
@ -1574,37 +1574,37 @@ Since Uniswap is a DEX, therefore it shows `"centralized": false`
|
|||
|
||||
## 9. Get Market Cap or Dominance of a Specific Ecosystem
|
||||
|
||||
* Use [/coins/categories](/reference/coins-categories).
|
||||
* Use [/coins/categories](https://docs.coingecko.com/reference/coins-categories).
|
||||
* The endpoint also returns the 24-hour percentage change, offering insights into the traction of different categories or ecosystems.
|
||||
|
||||
## 10. Get Token Lists of a Specific Blockchain Network
|
||||
|
||||
* Use [/token\_lists/asset\_platforms\_id/all.json](/reference/token-lists) endpoint.
|
||||
* Use [/token\_lists/asset\_platforms\_id/all.json](https://docs.coingecko.com/reference/token-lists) endpoint.
|
||||
* Supply asset platform id to the endpoint.
|
||||
|
||||
## 11. Get 7-Day Sparkline Price Data of a Coin
|
||||
|
||||
* Use [/coins/id](/reference/coins-id) or [/coins/markets](/reference/coins-markets) endpoints by flagging `sparkline = true`.
|
||||
* Use [/coins/id](https://docs.coingecko.com/reference/coins-id) or [/coins/markets](https://docs.coingecko.com/reference/coins-markets) endpoints by flagging `sparkline = true`.
|
||||
|
||||
## 12. Get Link to Individual CoinGecko Coin Page
|
||||
|
||||
* Use [/coins/list](/reference/coins-list) endpoint to get the coin **`{ID}`**.
|
||||
* Use [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint to get the coin **`{ID}`**.
|
||||
* Supply API ID in this URL path format: `www.coingecko.com/en/coins/{ID}`
|
||||
* If you wish to the obtain the URL slug of a specific CoinGecko Coin Page, e.g. `www.coingecko.com/en/coins/{web_slug}` you may use [/coin/id](/reference/coins-id) endpoint and obtain the **`{web_slug}`** value.
|
||||
* If you wish to the obtain the URL slug of a specific CoinGecko Coin Page, e.g. `www.coingecko.com/en/coins/{web_slug}` you may use [/coin/id](https://docs.coingecko.com/reference/coins-id) endpoint and obtain the **`{web_slug}`** value.
|
||||
|
||||
## 13. Check Coin Status and Stale Price Updates
|
||||
|
||||
* Active: use [/coins/list](/reference/coins-list) endpoint, only active coins will be shown by default. You may also flag **`status=inactive`** to get a list of inactive coins.
|
||||
* Price Stale: use [/simple/price](/reference/simple-price) endpoint, flag `include_last_updated_at=true` to check latest update time.
|
||||
* Active: use [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint, only active coins will be shown by default. You may also flag **`status=inactive`** to get a list of inactive coins.
|
||||
* Price Stale: use [/simple/price](https://docs.coingecko.com/reference/simple-price) endpoint, flag `include_last_updated_at=true` to check latest update time.
|
||||
|
||||
## 14. Get Real-Time and Historical Exchange of BTC in USD
|
||||
|
||||
* Current exchange rate: use [/exchange\_rates](/reference/exchange-rates) endpoint.
|
||||
* Historical exchange rate: use [/coins/id/history](/reference/coins-id-history) or [/coins/id/market\_chart](/reference/coins-id-market-chart) endpoints.
|
||||
* Current exchange rate: use [/exchange\_rates](https://docs.coingecko.com/reference/exchange-rates) endpoint.
|
||||
* Historical exchange rate: use [/coins/id/history](https://docs.coingecko.com/reference/coins-id-history) or [/coins/id/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart) endpoints.
|
||||
|
||||
## 15. Get Watchlist Portfolio Data of a Coin
|
||||
|
||||
* Use [/coins/id](/reference/coins-id) endpoint by supplying coin ID.
|
||||
* Use [/coins/id](https://docs.coingecko.com/reference/coins-id) endpoint by supplying coin ID.
|
||||
|
||||
* Example of responses:
|
||||
|
||||
|
|
@ -1616,21 +1616,21 @@ Since Uniswap is a DEX, therefore it shows `"centralized": false`
|
|||
|
||||
**Note**: This is available for paid plan subscribers only.
|
||||
|
||||
* Use [/coins/list](/reference/coins-list) endpoint, specifying the status param as `inactive`.
|
||||
* Use [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint, specifying the status param as `inactive`.
|
||||
|
||||
* Example of endpoint request: `https://pro-api.coingecko.com/api/v3/coins/list?include_platform=false&status=inactive&x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
* Retrieve the coin's ID from the endpoint mentioned above and use it to access historical data via the following endpoints:
|
||||
|
||||
* [/coins/id/history](/reference/coins-id-history)
|
||||
* [/coins/id/market\_chart](/reference/coins-id-market-chart)
|
||||
* [/coins/id/market\_chart/range](/reference/coins-id-market-chart-range)
|
||||
* [/coins/id/contract/contract\_address/market\_chart](/reference/contract-address-market-chart)
|
||||
* [/coins/id/contract/contract\_address/market\_chart/range](/reference/contract-address-market-chart-range)
|
||||
* [/coins/id/history](https://docs.coingecko.com/reference/coins-id-history)
|
||||
* [/coins/id/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart)
|
||||
* [/coins/id/market\_chart/range](https://docs.coingecko.com/reference/coins-id-market-chart-range)
|
||||
* [/coins/id/contract/contract\_address/market\_chart](https://docs.coingecko.com/reference/contract-address-market-chart)
|
||||
* [/coins/id/contract/contract\_address/market\_chart/range](https://docs.coingecko.com/reference/contract-address-market-chart-range)
|
||||
|
||||
## 17. Get TVL (Total Value Locked) data of a Coin
|
||||
|
||||
* Use [/coins/id](/reference/coins-id) endpoint by supplying coin ID.
|
||||
* Use [/coins/id](https://docs.coingecko.com/reference/coins-id) endpoint by supplying coin ID.
|
||||
|
||||
* Example of responses:
|
||||
|
||||
|
|
@ -1642,29 +1642,29 @@ Since Uniswap is a DEX, therefore it shows `"centralized": false`
|
|||
|
||||
We have 2 Search endpoints:
|
||||
|
||||
* [/search](/reference/search-data) endpoint allows you to search for coins, categories, exchanges (markets), and NFTs listed on CoinGecko.com. You may query by name or symbol.
|
||||
* [/search-pools](/reference/search-pools) endpoint allows you to search for pools listed on GeckoTerminal.com. You may query by pool contract address, token contract address, or token symbol.
|
||||
* [/search](https://docs.coingecko.com/reference/search-data) endpoint allows you to search for coins, categories, exchanges (markets), and NFTs listed on CoinGecko.com. You may query by name or symbol.
|
||||
* [/search-pools](https://docs.coingecko.com/reference/search-pools) endpoint allows you to search for pools listed on GeckoTerminal.com. You may query by pool contract address, token contract address, or token symbol.
|
||||
|
||||
## 19. Get List of Blockchain Networks supported on CoinGecko and GeckoTerminal.
|
||||
|
||||
CoinGecko and GeckoTerminal support different sets of blockchain networks. You can use the following endpoints to find the list of supported networks and their respective IDs:
|
||||
|
||||
* CoinGecko: [/asset-platforms-list](/reference/asset-platforms-list)
|
||||
* GeckoTerminal ([onchain endpoints](/reference/endpoint-overview#-onchain-dex-endpoints-geckoterminal)): [/networks-list](/reference/networks-list)
|
||||
* CoinGecko: [/asset-platforms-list](https://docs.coingecko.com/reference/asset-platforms-list)
|
||||
* GeckoTerminal ([onchain endpoints](https://docs.coingecko.com/reference/endpoint-overview#-onchain-dex-endpoints-geckoterminal)): [/networks-list](https://docs.coingecko.com/reference/networks-list)
|
||||
|
||||
## 20. Get Native Coin of a Blockchain Network (Asset Platform)
|
||||
|
||||
You may use the [/asset-platforms-list](/reference/asset-platforms-list) endpoint to obtain the native coin ID of all networks (asset platforms) listed on [www.coingecko.com](http://www.coingecko.com.).
|
||||
You may use the [/asset-platforms-list](https://docs.coingecko.com/reference/asset-platforms-list) endpoint to obtain the native coin ID of all networks (asset platforms) listed on [www.coingecko.com](http://www.coingecko.com.).
|
||||
|
||||
## 21. Get Liquidity data of a Liquidity Pool or Token
|
||||
|
||||
There are multiple onchain endpoints that provide the liquidity data (`reserve_in_usd`) of a pool, for example: [Specific Pool Data by Pool Address](/reference/pool-address). You may also get liquidity data (`total_reserve_in_usd`) of a token, using endpoints like: [Token Data by Token Address](/reference/token-data-contract-address).
|
||||
There are multiple onchain endpoints that provide the liquidity data (`reserve_in_usd`) of a pool, for example: [Specific Pool Data by Pool Address](https://docs.coingecko.com/reference/pool-address). You may also get liquidity data (`total_reserve_in_usd`) of a token, using endpoints like: [Token Data by Token Address](https://docs.coingecko.com/reference/token-data-contract-address).
|
||||
|
||||
Note: `reserve_in_usd` (pool) represents the total liquidity of all tokens within a specific pool, whereas `total_reserve_in_usd` (token) refers to the total liquidity portion attributable to a specific token across all available pools.
|
||||
|
||||
## 22. Get list of onchain DEX pools based on specific criteria
|
||||
|
||||
* Use [/pools/megafilter](/reference/pools-megafilter) to retrieve data for onchain DEX pools that match a given set of filters.
|
||||
* Use [/pools/megafilter](https://docs.coingecko.com/reference/pools-megafilter) to retrieve data for onchain DEX pools that match a given set of filters.
|
||||
|
||||
* Example of use cases:
|
||||
|
||||
|
|
@ -1673,24 +1673,24 @@ Note: `reserve_in_usd` (pool) represents the total liquidity of all tokens withi
|
|||
|
||||
* For more details on examples and available filters, refer to:
|
||||
|
||||
* [Changelog — New Megafilter Endpoint](/changelog#february-2025)
|
||||
* [Changelog — New Megafilter Endpoint](https://docs.coingecko.com/changelog#february-2025)
|
||||
* [Live Filtering on GeckoTerminal](https://www.geckoterminal.com/)
|
||||
|
||||
## 23. Get List of Trending Coins
|
||||
|
||||
* Use the following endpoints to get trending coins and pools:
|
||||
|
||||
* [Trending Search List](/reference/trending-search/) — Trending Coins, NFTs, Categories on CoinGecko.com, based on user searches.
|
||||
* [Trending Search Pools](/reference/trending-search-pools/) — Trending Pools and Tokens on GeckoTerminal.com, based on user searches.
|
||||
* [Trending Search List](https://docs.coingecko.com/reference/trending-search/) — Trending Coins, NFTs, Categories on CoinGecko.com, based on user searches.
|
||||
* [Trending Search Pools](https://docs.coingecko.com/reference/trending-search-pools/) — Trending Pools and Tokens on GeckoTerminal.com, based on user searches.
|
||||
|
||||
* Other useful endpoints:
|
||||
|
||||
* [Top Gainers & Losers](/reference/coins-top-gainers-losers) on CoinGecko.com, by specific time duration.
|
||||
* [Trending Pools List](/reference/trending-pools-list) and [Trending Pools by Network](/reference/trending-pools-network) on GeckoTerminal.com, by specific time duration.
|
||||
* [Top Gainers & Losers](https://docs.coingecko.com/reference/coins-top-gainers-losers) on CoinGecko.com, by specific time duration.
|
||||
* [Trending Pools List](https://docs.coingecko.com/reference/trending-pools-list) and [Trending Pools by Network](https://docs.coingecko.com/reference/trending-pools-network) on GeckoTerminal.com, by specific time duration.
|
||||
|
||||
## 24. Get Security Info of Tokens
|
||||
|
||||
* By using [Token Info by Token Address](/reference/token-info-contract-address) endpoint, you can obtain the following security related data:
|
||||
* By using [Token Info by Token Address](https://docs.coingecko.com/reference/token-info-contract-address) endpoint, you can obtain the following security related data:
|
||||
|
||||
* GeckoTerminal Score (Pool, Transaction, Creation, Info, Holders)
|
||||
* Holders count and distribution percentage
|
||||
|
|
@ -1698,7 +1698,7 @@ Note: `reserve_in_usd` (pool) represents the total liquidity of all tokens withi
|
|||
|
||||
## 25. Get Latest Token/Pool Data from Launchpad
|
||||
|
||||
* Use [megafilter](/reference/pools-megafilter) endpoint to retrieve latest launchpad data, by flagging `sort=pool_created_at_desc`. Learn more on [changelog](/changelog#now-supported%3A-launchpad-data-pump-fun-%26-more-%2C-granular-ohlcv%2C-and-honeypot-info).
|
||||
* Use [megafilter](https://docs.coingecko.com/reference/pools-megafilter) endpoint to retrieve latest launchpad data, by flagging `sort=pool_created_at_desc`. Learn more on [changelog](https://docs.coingecko.com/changelog#now-supported%3A-launchpad-data-pump-fun-%26-more-%2C-granular-ohlcv%2C-and-honeypot-info).
|
||||
* **Request example (Get latest pools on Pump.fun)**:
|
||||
|
||||
<CodeGroup>
|
||||
|
|
@ -1724,7 +1724,7 @@ Example 1 (unknown):
|
|||
|
||||
## 8. Get Bitcoin Dominance Data (BTC.D)
|
||||
|
||||
* Use [/global ](/reference/crypto-global)endpoint.
|
||||
* Use [/global ](https://docs.coingecko.com/reference/crypto-global)endpoint.
|
||||
|
||||
* Example of responses:
|
||||
|
||||
|
|
@ -1737,37 +1737,37 @@ Example 2 (unknown):
|
|||
|
||||
## 9. Get Market Cap or Dominance of a Specific Ecosystem
|
||||
|
||||
* Use [/coins/categories](/reference/coins-categories).
|
||||
* Use [/coins/categories](https://docs.coingecko.com/reference/coins-categories).
|
||||
* The endpoint also returns the 24-hour percentage change, offering insights into the traction of different categories or ecosystems.
|
||||
|
||||
## 10. Get Token Lists of a Specific Blockchain Network
|
||||
|
||||
* Use [/token\_lists/asset\_platforms\_id/all.json](/reference/token-lists) endpoint.
|
||||
* Use [/token\_lists/asset\_platforms\_id/all.json](https://docs.coingecko.com/reference/token-lists) endpoint.
|
||||
* Supply asset platform id to the endpoint.
|
||||
|
||||
## 11. Get 7-Day Sparkline Price Data of a Coin
|
||||
|
||||
* Use [/coins/id](/reference/coins-id) or [/coins/markets](/reference/coins-markets) endpoints by flagging `sparkline = true`.
|
||||
* Use [/coins/id](https://docs.coingecko.com/reference/coins-id) or [/coins/markets](https://docs.coingecko.com/reference/coins-markets) endpoints by flagging `sparkline = true`.
|
||||
|
||||
## 12. Get Link to Individual CoinGecko Coin Page
|
||||
|
||||
* Use [/coins/list](/reference/coins-list) endpoint to get the coin **`{ID}`**.
|
||||
* Use [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint to get the coin **`{ID}`**.
|
||||
* Supply API ID in this URL path format: `www.coingecko.com/en/coins/{ID}`
|
||||
* If you wish to the obtain the URL slug of a specific CoinGecko Coin Page, e.g. `www.coingecko.com/en/coins/{web_slug}` you may use [/coin/id](/reference/coins-id) endpoint and obtain the **`{web_slug}`** value.
|
||||
* If you wish to the obtain the URL slug of a specific CoinGecko Coin Page, e.g. `www.coingecko.com/en/coins/{web_slug}` you may use [/coin/id](https://docs.coingecko.com/reference/coins-id) endpoint and obtain the **`{web_slug}`** value.
|
||||
|
||||
## 13. Check Coin Status and Stale Price Updates
|
||||
|
||||
* Active: use [/coins/list](/reference/coins-list) endpoint, only active coins will be shown by default. You may also flag **`status=inactive`** to get a list of inactive coins.
|
||||
* Price Stale: use [/simple/price](/reference/simple-price) endpoint, flag `include_last_updated_at=true` to check latest update time.
|
||||
* Active: use [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint, only active coins will be shown by default. You may also flag **`status=inactive`** to get a list of inactive coins.
|
||||
* Price Stale: use [/simple/price](https://docs.coingecko.com/reference/simple-price) endpoint, flag `include_last_updated_at=true` to check latest update time.
|
||||
|
||||
## 14. Get Real-Time and Historical Exchange of BTC in USD
|
||||
|
||||
* Current exchange rate: use [/exchange\_rates](/reference/exchange-rates) endpoint.
|
||||
* Historical exchange rate: use [/coins/id/history](/reference/coins-id-history) or [/coins/id/market\_chart](/reference/coins-id-market-chart) endpoints.
|
||||
* Current exchange rate: use [/exchange\_rates](https://docs.coingecko.com/reference/exchange-rates) endpoint.
|
||||
* Historical exchange rate: use [/coins/id/history](https://docs.coingecko.com/reference/coins-id-history) or [/coins/id/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart) endpoints.
|
||||
|
||||
## 15. Get Watchlist Portfolio Data of a Coin
|
||||
|
||||
* Use [/coins/id](/reference/coins-id) endpoint by supplying coin ID.
|
||||
* Use [/coins/id](https://docs.coingecko.com/reference/coins-id) endpoint by supplying coin ID.
|
||||
|
||||
* Example of responses:
|
||||
|
||||
|
|
@ -1782,21 +1782,21 @@ Example 3 (unknown):
|
|||
|
||||
**Note**: This is available for paid plan subscribers only.
|
||||
|
||||
* Use [/coins/list](/reference/coins-list) endpoint, specifying the status param as `inactive`.
|
||||
* Use [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint, specifying the status param as `inactive`.
|
||||
|
||||
* Example of endpoint request: `https://pro-api.coingecko.com/api/v3/coins/list?include_platform=false&status=inactive&x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
* Retrieve the coin's ID from the endpoint mentioned above and use it to access historical data via the following endpoints:
|
||||
|
||||
* [/coins/id/history](/reference/coins-id-history)
|
||||
* [/coins/id/market\_chart](/reference/coins-id-market-chart)
|
||||
* [/coins/id/market\_chart/range](/reference/coins-id-market-chart-range)
|
||||
* [/coins/id/contract/contract\_address/market\_chart](/reference/contract-address-market-chart)
|
||||
* [/coins/id/contract/contract\_address/market\_chart/range](/reference/contract-address-market-chart-range)
|
||||
* [/coins/id/history](https://docs.coingecko.com/reference/coins-id-history)
|
||||
* [/coins/id/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart)
|
||||
* [/coins/id/market\_chart/range](https://docs.coingecko.com/reference/coins-id-market-chart-range)
|
||||
* [/coins/id/contract/contract\_address/market\_chart](https://docs.coingecko.com/reference/contract-address-market-chart)
|
||||
* [/coins/id/contract/contract\_address/market\_chart/range](https://docs.coingecko.com/reference/contract-address-market-chart-range)
|
||||
|
||||
## 17. Get TVL (Total Value Locked) data of a Coin
|
||||
|
||||
* Use [/coins/id](/reference/coins-id) endpoint by supplying coin ID.
|
||||
* Use [/coins/id](https://docs.coingecko.com/reference/coins-id) endpoint by supplying coin ID.
|
||||
|
||||
* Example of responses:
|
||||
|
||||
|
|
@ -1811,29 +1811,29 @@ Example 4 (unknown):
|
|||
|
||||
We have 2 Search endpoints:
|
||||
|
||||
* [/search](/reference/search-data) endpoint allows you to search for coins, categories, exchanges (markets), and NFTs listed on CoinGecko.com. You may query by name or symbol.
|
||||
* [/search-pools](/reference/search-pools) endpoint allows you to search for pools listed on GeckoTerminal.com. You may query by pool contract address, token contract address, or token symbol.
|
||||
* [/search](https://docs.coingecko.com/reference/search-data) endpoint allows you to search for coins, categories, exchanges (markets), and NFTs listed on CoinGecko.com. You may query by name or symbol.
|
||||
* [/search-pools](https://docs.coingecko.com/reference/search-pools) endpoint allows you to search for pools listed on GeckoTerminal.com. You may query by pool contract address, token contract address, or token symbol.
|
||||
|
||||
## 19. Get List of Blockchain Networks supported on CoinGecko and GeckoTerminal.
|
||||
|
||||
CoinGecko and GeckoTerminal support different sets of blockchain networks. You can use the following endpoints to find the list of supported networks and their respective IDs:
|
||||
|
||||
* CoinGecko: [/asset-platforms-list](/reference/asset-platforms-list)
|
||||
* GeckoTerminal ([onchain endpoints](/reference/endpoint-overview#-onchain-dex-endpoints-geckoterminal)): [/networks-list](/reference/networks-list)
|
||||
* CoinGecko: [/asset-platforms-list](https://docs.coingecko.com/reference/asset-platforms-list)
|
||||
* GeckoTerminal ([onchain endpoints](https://docs.coingecko.com/reference/endpoint-overview#-onchain-dex-endpoints-geckoterminal)): [/networks-list](https://docs.coingecko.com/reference/networks-list)
|
||||
|
||||
## 20. Get Native Coin of a Blockchain Network (Asset Platform)
|
||||
|
||||
You may use the [/asset-platforms-list](/reference/asset-platforms-list) endpoint to obtain the native coin ID of all networks (asset platforms) listed on [www.coingecko.com](http://www.coingecko.com.).
|
||||
You may use the [/asset-platforms-list](https://docs.coingecko.com/reference/asset-platforms-list) endpoint to obtain the native coin ID of all networks (asset platforms) listed on [www.coingecko.com](http://www.coingecko.com.).
|
||||
|
||||
## 21. Get Liquidity data of a Liquidity Pool or Token
|
||||
|
||||
There are multiple onchain endpoints that provide the liquidity data (`reserve_in_usd`) of a pool, for example: [Specific Pool Data by Pool Address](/reference/pool-address). You may also get liquidity data (`total_reserve_in_usd`) of a token, using endpoints like: [Token Data by Token Address](/reference/token-data-contract-address).
|
||||
There are multiple onchain endpoints that provide the liquidity data (`reserve_in_usd`) of a pool, for example: [Specific Pool Data by Pool Address](https://docs.coingecko.com/reference/pool-address). You may also get liquidity data (`total_reserve_in_usd`) of a token, using endpoints like: [Token Data by Token Address](https://docs.coingecko.com/reference/token-data-contract-address).
|
||||
|
||||
Note: `reserve_in_usd` (pool) represents the total liquidity of all tokens within a specific pool, whereas `total_reserve_in_usd` (token) refers to the total liquidity portion attributable to a specific token across all available pools.
|
||||
|
||||
## 22. Get list of onchain DEX pools based on specific criteria
|
||||
|
||||
* Use [/pools/megafilter](/reference/pools-megafilter) to retrieve data for onchain DEX pools that match a given set of filters.
|
||||
* Use [/pools/megafilter](https://docs.coingecko.com/reference/pools-megafilter) to retrieve data for onchain DEX pools that match a given set of filters.
|
||||
|
||||
* Example of use cases:
|
||||
|
||||
|
|
@ -1842,24 +1842,24 @@ Note: `reserve_in_usd` (pool) represents the total liquidity of all tokens withi
|
|||
|
||||
* For more details on examples and available filters, refer to:
|
||||
|
||||
* [Changelog — New Megafilter Endpoint](/changelog#february-2025)
|
||||
* [Changelog — New Megafilter Endpoint](https://docs.coingecko.com/changelog#february-2025)
|
||||
* [Live Filtering on GeckoTerminal](https://www.geckoterminal.com/)
|
||||
|
||||
## 23. Get List of Trending Coins
|
||||
|
||||
* Use the following endpoints to get trending coins and pools:
|
||||
|
||||
* [Trending Search List](/reference/trending-search/) — Trending Coins, NFTs, Categories on CoinGecko.com, based on user searches.
|
||||
* [Trending Search Pools](/reference/trending-search-pools/) — Trending Pools and Tokens on GeckoTerminal.com, based on user searches.
|
||||
* [Trending Search List](https://docs.coingecko.com/reference/trending-search/) — Trending Coins, NFTs, Categories on CoinGecko.com, based on user searches.
|
||||
* [Trending Search Pools](https://docs.coingecko.com/reference/trending-search-pools/) — Trending Pools and Tokens on GeckoTerminal.com, based on user searches.
|
||||
|
||||
* Other useful endpoints:
|
||||
|
||||
* [Top Gainers & Losers](/reference/coins-top-gainers-losers) on CoinGecko.com, by specific time duration.
|
||||
* [Trending Pools List](/reference/trending-pools-list) and [Trending Pools by Network](/reference/trending-pools-network) on GeckoTerminal.com, by specific time duration.
|
||||
* [Top Gainers & Losers](https://docs.coingecko.com/reference/coins-top-gainers-losers) on CoinGecko.com, by specific time duration.
|
||||
* [Trending Pools List](https://docs.coingecko.com/reference/trending-pools-list) and [Trending Pools by Network](https://docs.coingecko.com/reference/trending-pools-network) on GeckoTerminal.com, by specific time duration.
|
||||
|
||||
## 24. Get Security Info of Tokens
|
||||
|
||||
* By using [Token Info by Token Address](/reference/token-info-contract-address) endpoint, you can obtain the following security related data:
|
||||
* By using [Token Info by Token Address](https://docs.coingecko.com/reference/token-info-contract-address) endpoint, you can obtain the following security related data:
|
||||
|
||||
* GeckoTerminal Score (Pool, Transaction, Creation, Info, Holders)
|
||||
* Holders count and distribution percentage
|
||||
|
|
@ -1867,7 +1867,7 @@ Note: `reserve_in_usd` (pool) represents the total liquidity of all tokens withi
|
|||
|
||||
## 25. Get Latest Token/Pool Data from Launchpad
|
||||
|
||||
* Use [megafilter](/reference/pools-megafilter) endpoint to retrieve latest launchpad data, by flagging `sort=pool_created_at_desc`. Learn more on [changelog](/changelog#now-supported%3A-launchpad-data-pump-fun-%26-more-%2C-granular-ohlcv%2C-and-honeypot-info).
|
||||
* Use [megafilter](https://docs.coingecko.com/reference/pools-megafilter) endpoint to retrieve latest launchpad data, by flagging `sort=pool_created_at_desc`. Learn more on [changelog](https://docs.coingecko.com/changelog#now-supported%3A-launchpad-data-pump-fun-%26-more-%2C-granular-ohlcv%2C-and-honeypot-info).
|
||||
* **Request example (Get latest pools on Pump.fun)**:
|
||||
|
||||
<CodeGroup>
|
||||
|
|
@ -1910,7 +1910,7 @@ This endpoint allows you to **query the coin tickers on both centralized exchang
|
|||
|
||||
* You may obtain the coin ID (API ID) via several ways:
|
||||
* refers to respective coin page and find 'API ID'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to google sheets [here](https://docs.google.com/spreadsheets/d/1wTTuxXt8n9q7C4NDXqQpI3wpKu1_5bGVmP9Xz0XGSyU/edit?usp=sharing).
|
||||
* You may specify the `exchange_ids` if you want to retrieve tickers for specific exchange only.
|
||||
* You may include values such as `page` to specify which page of responses you would like to show.
|
||||
|
|
@ -1972,7 +1972,7 @@ This endpoint allows you to **get token price based on the provided token contra
|
|||
* The returned price currency is in USD.
|
||||
* Addresses not found in GeckoTerminal will be ignored.
|
||||
* This endpoint allows querying **up to 30 contract addresses** per request.
|
||||
* When using this endpoint, GeckoTerminal's routing decides the best pool for token price. The price source may change based on liquidity and pool activity. For full control over the price, you may use [`/networks/{network}/pools/{address}`](/v3.0.1/reference/pool-address) endpoint by providing a specific pool address.
|
||||
* When using this endpoint, GeckoTerminal's routing decides the best pool for token price. The price source may change based on liquidity and pool activity. For full control over the price, you may use [`/networks/{network}/pools/{address}`](https://docs.coingecko.com/v3.0.1/reference/pool-address) endpoint by providing a specific pool address.
|
||||
* Cache/Update Frequency: every 60 seconds.
|
||||
</Note>
|
||||
|
||||
|
|
@ -1988,7 +1988,7 @@ v3.0.1/reference/api-reference/onchain-demo.json get /networks/{network}/tokens/
|
|||
This endpoint allows you to **query multiple tokens data based on the provided token contract addresses on a network**
|
||||
|
||||
* You may add values such as `top_pools` in the include param to include top pools along with the pools information.
|
||||
* If you would like to query token information such as socials, websites, description and etc. You can go to this endpoint [`/networks/{network}/tokens/{address}/info`](/v3.0.1/reference/token-info-contract-address) instead.
|
||||
* If you would like to query token information such as socials, websites, description and etc. You can go to this endpoint [`/networks/{network}/tokens/{address}/info`](https://docs.coingecko.com/v3.0.1/reference/token-info-contract-address) instead.
|
||||
</Tip>
|
||||
|
||||
* Addresses not found in GeckoTerminal.com will be ignored.
|
||||
|
|
@ -2098,9 +2098,9 @@ This endpoint allows you to **get the OHLC chart (Open, High, Low, Close) of a c
|
|||
|
||||
* You may obtain the coin ID (API ID) via several ways:
|
||||
* refers to respective coin page and find 'API ID'.
|
||||
* refers to [`/coins/list`](/reference/coins-list) endpoint.
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/reference/coins-list) endpoint.
|
||||
* refers to google sheets [here](https://docs.google.com/spreadsheets/d/1wTTuxXt8n9q7C4NDXqQpI3wpKu1_5bGVmP9Xz0XGSyU/edit?usp=sharing).
|
||||
* For historical chart data with better granularity, you may consider using [/coins/{`id`}/market\_chart](/reference/coins-id-market-chart) endpoint.
|
||||
* For historical chart data with better granularity, you may consider using [/coins/{`id`}/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart) endpoint.
|
||||
* Supports ISO date strings (`YYYY-MM-DD` or\
|
||||
`YYYY-MM-DDTHH:MM`, recommended for best compatibility) or UNIX timestamps.
|
||||
</Tip>
|
||||
|
|
@ -2129,12 +2129,12 @@ Source: https://docs.coingecko.com/v3.0.1/reference/token-info-contract-address
|
|||
v3.0.1/reference/api-reference/onchain-demo.json get /networks/{network}/tokens/{address}/info
|
||||
This endpoint allows you to **query token metadata (name, symbol, CoinGecko ID, image, socials, websites, description, etc.) based on a provided token contract address on a network**
|
||||
|
||||
* If you would like to query token data such as decimals, total supply, price and etc. You can go to this endpoint [`/networks/{network}/tokens/{address}`](/v3.0.1/reference/token-data-contract-address) instead.
|
||||
* If you would like to query token data such as decimals, total supply, price and etc. You can go to this endpoint [`/networks/{network}/tokens/{address}`](https://docs.coingecko.com/v3.0.1/reference/token-data-contract-address) instead.
|
||||
* Cache/Update frequency: every 60 seconds.
|
||||
* Learn more about GT score [here](https://support.coingecko.com/hc/en-us/articles/38381394237593-What-is-GT-Score-How-is-GT-Score-calculated).
|
||||
* Metadata (image, websites, description, socials) may be sourced on-chain and is not vetted by the CoinGecko team. If you wish to get metadata reviewed by CoinGecko team, you may use the following endpoints:
|
||||
* [Coin Data by ID](/v3.0.1/reference/coins-id)
|
||||
* [Coin Data by Token Address](/v3.0.1/reference/coins-contract-address)
|
||||
* [Coin Data by ID](https://docs.coingecko.com/v3.0.1/reference/coins-id)
|
||||
* [Coin Data by Token Address](https://docs.coingecko.com/v3.0.1/reference/coins-contract-address)
|
||||
</Tip>
|
||||
|
||||
* `holders` data is currently in Beta, with ongoing improvements to data quality, coverage, and update frequency.
|
||||
|
|
@ -2364,7 +2364,7 @@ Here are some of the important parameters to take note while using Onchain DEX A
|
|||
|
||||
**How to obtain Network ID?**
|
||||
|
||||
* Use [/onchain/networks](/reference/networks-list) endpoint, example of response:
|
||||
* Use [/onchain/networks](https://docs.coingecko.com/reference/networks-list) endpoint, example of response:
|
||||
|
||||
<CodeGroup>
|
||||
|
||||
|
|
@ -2380,7 +2380,7 @@ Here are some of the important parameters to take note while using Onchain DEX A
|
|||
|
||||
Some of the pools endpoints require you to provide DEX ID along with Network ID to query the pools on a particular DEX (Decentralized Exchange).
|
||||
|
||||
Using [/onchain/networks/\{network}/dexes/\{dex}/pools](/reference/top-pools-dex) as example:
|
||||
Using [/onchain/networks/\{network}/dexes/\{dex}/pools](https://docs.coingecko.com/reference/top-pools-dex) as example:
|
||||
|
||||
* `https://pro-api.coingecko.com/api/v3/onchain/networks/eth/dexes/uniswap_v3/pools?x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
|
|
@ -2391,7 +2391,7 @@ There are 2 parameter values required to apply for this endpoint:
|
|||
|
||||
**How to obtain DEX ID?**
|
||||
|
||||
* Use [/onchain/networks/\{network}/dexes](/reference/dexes-list) endpoint, example of response:
|
||||
* Use [/onchain/networks/\{network}/dexes](https://docs.coingecko.com/reference/dexes-list) endpoint, example of response:
|
||||
|
||||
<CodeGroup>
|
||||
|
||||
|
|
@ -2413,7 +2413,7 @@ There are 2 parameter values required to apply for this endpoint:
|
|||
|
||||
Most of the time, you will need a pool contract address along with Network ID to query the onchain data, especially when using the Pools Endpoints.
|
||||
|
||||
Using [/onchain/networks/\{network}/pools/\{address}](/reference/pool-address) as example:
|
||||
Using [/onchain/networks/\{network}/pools/\{address}](https://docs.coingecko.com/reference/pool-address) as example:
|
||||
|
||||
* `https://pro-api.coingecko.com/api/v3/onchain/networks/eth/pools/0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc?x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
|
|
@ -2435,7 +2435,7 @@ There are 2 parameter values required to apply for this endpoint:
|
|||
|
||||
### b. Token Contract Address
|
||||
|
||||
Apart from the pool contract address, you also have the option to query onchain data by using the token contract address, using [/onchain/networks/\{network}/tokens/\{token\_address}/pools](/reference/top-pools-contract-address) as example:
|
||||
Apart from the pool contract address, you also have the option to query onchain data by using the token contract address, using [/onchain/networks/\{network}/tokens/\{token\_address}/pools](https://docs.coingecko.com/reference/top-pools-contract-address) as example:
|
||||
|
||||
* `https://pro-api.coingecko.com/api/v3/onchain/networks/eth/tokens/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48/pools?x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
|
|
@ -2474,7 +2474,7 @@ Example 1 (unknown):
|
|||
|
||||
Some of the pools endpoints require you to provide DEX ID along with Network ID to query the pools on a particular DEX (Decentralized Exchange).
|
||||
|
||||
Using [/onchain/networks/\{network}/dexes/\{dex}/pools](/reference/top-pools-dex) as example:
|
||||
Using [/onchain/networks/\{network}/dexes/\{dex}/pools](https://docs.coingecko.com/reference/top-pools-dex) as example:
|
||||
|
||||
* `https://pro-api.coingecko.com/api/v3/onchain/networks/eth/dexes/uniswap_v3/pools?x_cg_pro_api_key=YOUR_API_KEY`
|
||||
|
||||
|
|
@ -2485,7 +2485,7 @@ There are 2 parameter values required to apply for this endpoint:
|
|||
|
||||
**How to obtain DEX ID?**
|
||||
|
||||
* Use [/onchain/networks/\{network}/dexes](/reference/dexes-list) endpoint, example of response:
|
||||
* Use [/onchain/networks/\{network}/dexes](https://docs.coingecko.com/reference/dexes-list) endpoint, example of response:
|
||||
|
||||
<CodeGroup>
|
||||
```
|
||||
|
|
@ -2525,7 +2525,7 @@ This endpoint allows you to **get the historical chart data of a coin within cer
|
|||
|
||||
* You may obtain the coin ID (API ID) via several ways:
|
||||
* refers to respective coin page and find 'API ID'.
|
||||
* refers to [`/coins/list`](/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to [`/coins/list`](https://docs.coingecko.com/v3.0.1/reference/coins-list) endpoint.
|
||||
* refers to google sheets [here](https://docs.google.com/spreadsheets/d/1wTTuxXt8n9q7C4NDXqQpI3wpKu1_5bGVmP9Xz0XGSyU/edit?usp=sharing).
|
||||
</Tip>
|
||||
|
||||
|
|
|
|||
|
|
@ -13,10 +13,10 @@ Source: https://docs.coingecko.com/v3.0.1/reference/nfts-contract-address
|
|||
v3.0.1/reference/api-reference/coingecko-demo.json get /nfts/{asset_platform_id}/contract/{contract_address}
|
||||
This endpoint allows you to **query all the NFT data (name, floor price, 24hr volume ...) based on the NFT collection contract address and respective asset platform**
|
||||
|
||||
* You may also obtain the asset platform id and contract address through [/nfts/list](/v3.0.1/reference/nfts-list) endpoint.
|
||||
* You may also obtain the asset platform id and contract address through [/nfts/list](https://docs.coingecko.com/v3.0.1/reference/nfts-list) endpoint.
|
||||
</Tip>
|
||||
|
||||
* Solana NFT & Art Blocks are not supported for this endpoint, please use [/nfts/\{id}](/v3.0.1/reference/nfts-id) endpoint instead.
|
||||
* Solana NFT & Art Blocks are not supported for this endpoint, please use [/nfts/\{id}](https://docs.coingecko.com/v3.0.1/reference/nfts-id) endpoint instead.
|
||||
* Cache / Update Frequency: every 60 seconds for all the API plans.
|
||||
</Note>
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ v3.0.1/reference/api-reference/coingecko-demo.json get /exchanges/{id}/volume_ch
|
|||
This endpoint allows you to **query the historical volume chart data with time in UNIX and trading volume data in BTC based on exchange's ID**
|
||||
|
||||
* You can use this endpoint to query the historical volume chart data of **derivatives exchanges** as well.
|
||||
* The exchange volume in the response is provided in BTC. To convert it to other currencies, please use [/exchange\_rates](/v3.0.1/reference/exchange-rates) endpoint.
|
||||
* The exchange volume in the response is provided in BTC. To convert it to other currencies, please use [/exchange\_rates](https://docs.coingecko.com/v3.0.1/reference/exchange-rates) endpoint.
|
||||
* Data granularity is automatic (cannot be adjusted):
|
||||
* 1 day = 10-minutely
|
||||
* 7, 14 days = hourly
|
||||
|
|
@ -229,12 +229,12 @@ This endpoint allows you to **query exchange's data (name, year established, cou
|
|||
<Warning>
|
||||
### Notice
|
||||
|
||||
* Please note that the `trade_volume_24h_btc_normalized` data field will no longer be supported by our API starting on June 15, 2025. Please refer to [changelog](/changelog#may-2025) for more details.
|
||||
* Please note that the `trade_volume_24h_btc_normalized` data field will no longer be supported by our API starting on June 15, 2025. Please refer to [changelog](https://docs.coingecko.com/changelog#may-2025) for more details.
|
||||
</Warning>
|
||||
|
||||
* The exchange volume in the response is provided in BTC. To convert it to other currencies, please use [/exchange\_rates](/v3.0.1/reference/exchange-rates) endpoint.
|
||||
* For derivatives (e.g. bitmex, binance\_futures), to get derivatives exchanges data, please go to [/derivatives/exchange/\{id}](/v3.0.1/reference/derivatives-exchanges-id) endpoint.
|
||||
* Tickers are limited to 100 items, to get more tickers, please go to [/exchanges/\{id}/tickers](/v3.0.1/reference/exchanges-id-tickers) endpoint.
|
||||
* The exchange volume in the response is provided in BTC. To convert it to other currencies, please use [/exchange\_rates](https://docs.coingecko.com/v3.0.1/reference/exchange-rates) endpoint.
|
||||
* For derivatives (e.g. bitmex, binance\_futures), to get derivatives exchanges data, please go to [/derivatives/exchange/\{id}](https://docs.coingecko.com/v3.0.1/reference/derivatives-exchanges-id) endpoint.
|
||||
* Tickers are limited to 100 items, to get more tickers, please go to [/exchanges/\{id}/tickers](https://docs.coingecko.com/v3.0.1/reference/exchanges-id-tickers) endpoint.
|
||||
* When `dex_pair_format=symbol`, the DEX pair `base` and `target` are displayed in symbol format (e.g. `WETH`, `USDC`) instead of as contract addresses.
|
||||
* Cache / Update Frequency: every 60 seconds for all the API plans.
|
||||
</Note>
|
||||
|
|
|
|||
|
|
@ -207,97 +207,97 @@ Source: https://docs.coingecko.com/v3.0.1/reference/endpoint-overview
|
|||
|
||||
Any exclusive endpoints for Pro-API users (any paid plan subscribers) will not be included here.
|
||||
|
||||
For a full list of endpoints, please visit [Pro API Documentation](/reference/endpoint-overview) instead.
|
||||
For a full list of endpoints, please visit [Pro API Documentation](https://docs.coingecko.com/reference/endpoint-overview) instead.
|
||||
</Note>
|
||||
|
||||
## CoinGecko Endpoints: Coins
|
||||
|
||||
| Endpoint | Description |
|
||||
| -------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [/ping](/v3.0.1/reference/ping-server) | Check the API server status |
|
||||
| [/simple/price](/v3.0.1/reference/simple-price) | Query the prices of one or more coins by using their unique Coin API IDs |
|
||||
| [/simple/token\_price/\{id}](/v3.0.1/reference/simple-token-price) | Query the prices of one or more coins by using their unique Coin API IDs |
|
||||
| [/simple/supported\_vs\_currencies](/v3.0.1/reference/simple-supported-currencies) | Query all the supported currencies on CoinGecko |
|
||||
| [/coins/list](/v3.0.1/reference/coins-list) | Query all the supported coins on CoinGecko with coins ID, name and symbol |
|
||||
| [/coins/markets](/v3.0.1/reference/coins-markets) | Query all the supported coins with price, market cap, volume and market related data |
|
||||
| [/coins/\{id}](/v3.0.1/reference/coins-id) | Query all the metadata (image, websites, socials, description, contract address, etc.) from the CoinGecko coin page based on a particular coin ID |
|
||||
| [/coins/\{id}/tickers](/v3.0.1/reference/coins-id-tickers) | Query the coin tickers on both centralized exchange (CEX) and decentralized exchange (DEX) based on a particular coin ID |
|
||||
| [/coins/\{id}/history](/v3.0.1/reference/coins-id-history) | Query the historical data (price, market cap, 24hr volume, ...) at a given date for a coin based on a particular coin ID |
|
||||
| [/coins/\{id}/market\_chart](/v3.0.1/reference/coins-id-market-chart) | Get the historical chart data of a coin including time in UNIX, price, market cap and 24hr volume based on particular coin ID |
|
||||
| [/coins/\{id}/market\_chart/range](/v3.0.1/reference/coins-id-market-chart-range) | Get the historical chart data of a coin within certain time range in UNIX along with price, market cap and 24hr volume based on particular coin ID |
|
||||
| [/coins-id-ohlc](/v3.0.1/reference/coins-id-ohlc) | Get the OHLC chart (Open, High, Low, Close) of a coin based on particular coin ID |
|
||||
| [/coins/../contract/..](/v3.0.1/reference/coins-contract-address) | Query all the metadata (image, websites, socials, description, contract address, etc.) from the CoinGecko coin page based on an asset platform and a particular token contract address |
|
||||
| [/coins/../contract/../market\_chart](/v3.0.1/reference/contract-address-market-chart) | Get the historical chart data including time in UNIX, price, market cap and 24hr volume based on asset platform and particular token contract address |
|
||||
| [/coins/../contract/../market\_chart/range](/v3.0.1/reference/contract-address-market-chart-range) | Get the historical chart data within certain time range in UNIX along with price, market cap and 24hr volume based on asset platform and particular token contract address |
|
||||
| [/coins/categories/list](/v3.0.1/reference/coins-categories-list) | Query all the coins categories on CoinGecko |
|
||||
| [/coins/categories](/v3.0.1/reference/coins-categories) | Query all the coins categories with market data (market cap, volume, ...) on CoinGecko |
|
||||
| [/ping](https://docs.coingecko.com/v3.0.1/reference/ping-server) | Check the API server status |
|
||||
| [/simple/price](https://docs.coingecko.com/v3.0.1/reference/simple-price) | Query the prices of one or more coins by using their unique Coin API IDs |
|
||||
| [/simple/token\_price/\{id}](https://docs.coingecko.com/v3.0.1/reference/simple-token-price) | Query the prices of one or more coins by using their unique Coin API IDs |
|
||||
| [/simple/supported\_vs\_currencies](https://docs.coingecko.com/v3.0.1/reference/simple-supported-currencies) | Query all the supported currencies on CoinGecko |
|
||||
| [/coins/list](https://docs.coingecko.com/v3.0.1/reference/coins-list) | Query all the supported coins on CoinGecko with coins ID, name and symbol |
|
||||
| [/coins/markets](https://docs.coingecko.com/v3.0.1/reference/coins-markets) | Query all the supported coins with price, market cap, volume and market related data |
|
||||
| [/coins/\{id}](https://docs.coingecko.com/v3.0.1/reference/coins-id) | Query all the metadata (image, websites, socials, description, contract address, etc.) from the CoinGecko coin page based on a particular coin ID |
|
||||
| [/coins/\{id}/tickers](https://docs.coingecko.com/v3.0.1/reference/coins-id-tickers) | Query the coin tickers on both centralized exchange (CEX) and decentralized exchange (DEX) based on a particular coin ID |
|
||||
| [/coins/\{id}/history](https://docs.coingecko.com/v3.0.1/reference/coins-id-history) | Query the historical data (price, market cap, 24hr volume, ...) at a given date for a coin based on a particular coin ID |
|
||||
| [/coins/\{id}/market\_chart](https://docs.coingecko.com/v3.0.1/reference/coins-id-market-chart) | Get the historical chart data of a coin including time in UNIX, price, market cap and 24hr volume based on particular coin ID |
|
||||
| [/coins/\{id}/market\_chart/range](https://docs.coingecko.com/v3.0.1/reference/coins-id-market-chart-range) | Get the historical chart data of a coin within certain time range in UNIX along with price, market cap and 24hr volume based on particular coin ID |
|
||||
| [/coins-id-ohlc](https://docs.coingecko.com/v3.0.1/reference/coins-id-ohlc) | Get the OHLC chart (Open, High, Low, Close) of a coin based on particular coin ID |
|
||||
| [/coins/../contract/..](https://docs.coingecko.com/v3.0.1/reference/coins-contract-address) | Query all the metadata (image, websites, socials, description, contract address, etc.) from the CoinGecko coin page based on an asset platform and a particular token contract address |
|
||||
| [/coins/../contract/../market\_chart](https://docs.coingecko.com/v3.0.1/reference/contract-address-market-chart) | Get the historical chart data including time in UNIX, price, market cap and 24hr volume based on asset platform and particular token contract address |
|
||||
| [/coins/../contract/../market\_chart/range](https://docs.coingecko.com/v3.0.1/reference/contract-address-market-chart-range) | Get the historical chart data within certain time range in UNIX along with price, market cap and 24hr volume based on asset platform and particular token contract address |
|
||||
| [/coins/categories/list](https://docs.coingecko.com/v3.0.1/reference/coins-categories-list) | Query all the coins categories on CoinGecko |
|
||||
| [/coins/categories](https://docs.coingecko.com/v3.0.1/reference/coins-categories) | Query all the coins categories with market data (market cap, volume, ...) on CoinGecko |
|
||||
|
||||
## CoinGecko Endpoints: NFT
|
||||
|
||||
| Endpoint | Description |
|
||||
| --------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [/nfts/list](/v3.0.1/reference/nfts-list) | Query all supported NFTs with ID, contract address, name, asset platform ID and symbol on CoinGecko |
|
||||
| [/nfts/..](/v3.0.1/reference/nfts-id) | Query all the NFT data (name, floor price, 24hr volume, ...) based on the NFT collection ID |
|
||||
| [/nfts/../contract/..](/v3.0.1/reference/nfts-contract-address) | Query all the NFT data (name, floor price, 24hr volume, ...) based on the NFT collection contract address and respective asset platform |
|
||||
| [/nfts/list](https://docs.coingecko.com/v3.0.1/reference/nfts-list) | Query all supported NFTs with ID, contract address, name, asset platform ID and symbol on CoinGecko |
|
||||
| [/nfts/..](https://docs.coingecko.com/v3.0.1/reference/nfts-id) | Query all the NFT data (name, floor price, 24hr volume, ...) based on the NFT collection ID |
|
||||
| [/nfts/../contract/..](https://docs.coingecko.com/v3.0.1/reference/nfts-contract-address) | Query all the NFT data (name, floor price, 24hr volume, ...) based on the NFT collection contract address and respective asset platform |
|
||||
|
||||
## CoinGecko Endpoints: Exchanges & Derivatives
|
||||
|
||||
| Endpoint | Description |
|
||||
| ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [/exchanges](/v3.0.1/reference/exchanges) | Query all the supported exchanges with exchanges' data (ID, name, country, ...) that have active trading volumes on CoinGecko |
|
||||
| [/exchanges/list](/v3.0.1/reference/exchanges-list) | Query all the exchanges with ID and name |
|
||||
| [/exchanges/\{id}](/v3.0.1/reference/exchanges-id) | Query exchange's data (name, year established, country, ...), exchange volume in BTC and tickers based on exchange's ID |
|
||||
| [/exchanges/\{id}/tickers](/v3.0.1/reference/exchanges-id-tickers) | Query exchange's tickers based on exchange's ID |
|
||||
| [/exchanges/\{id}/volume\_chart](/v3.0.1/reference/exchanges-id-volume-chart) | Query the historical volume chart data with time in UNIX and trading volume data in BTC based on exchange's ID |
|
||||
| [/derivatives](/v3.0.1/reference/derivatives-tickers) | Query all the tickers from derivatives exchanges on CoinGecko |
|
||||
| [/derivatives/exchanges](/v3.0.1/reference/derivatives-exchanges) | Query all the derivatives exchanges with related data (ID, name, open interest, ...) on CoinGecko |
|
||||
| [/derivatives/exchanges/\{id}](/v3.0.1/reference/derivatives-exchanges-id) | Query the derivatives exchange's related data (ID, name, open interest, ...) based on the exchanges' ID |
|
||||
| [/derivatives/exchanges/list](/v3.0.1/reference/derivatives-exchanges-list) | Query all the derivatives exchanges with ID and name on CoinGecko |
|
||||
| [/exchanges](https://docs.coingecko.com/v3.0.1/reference/exchanges) | Query all the supported exchanges with exchanges' data (ID, name, country, ...) that have active trading volumes on CoinGecko |
|
||||
| [/exchanges/list](https://docs.coingecko.com/v3.0.1/reference/exchanges-list) | Query all the exchanges with ID and name |
|
||||
| [/exchanges/\{id}](https://docs.coingecko.com/v3.0.1/reference/exchanges-id) | Query exchange's data (name, year established, country, ...), exchange volume in BTC and tickers based on exchange's ID |
|
||||
| [/exchanges/\{id}/tickers](https://docs.coingecko.com/v3.0.1/reference/exchanges-id-tickers) | Query exchange's tickers based on exchange's ID |
|
||||
| [/exchanges/\{id}/volume\_chart](https://docs.coingecko.com/v3.0.1/reference/exchanges-id-volume-chart) | Query the historical volume chart data with time in UNIX and trading volume data in BTC based on exchange's ID |
|
||||
| [/derivatives](https://docs.coingecko.com/v3.0.1/reference/derivatives-tickers) | Query all the tickers from derivatives exchanges on CoinGecko |
|
||||
| [/derivatives/exchanges](https://docs.coingecko.com/v3.0.1/reference/derivatives-exchanges) | Query all the derivatives exchanges with related data (ID, name, open interest, ...) on CoinGecko |
|
||||
| [/derivatives/exchanges/\{id}](https://docs.coingecko.com/v3.0.1/reference/derivatives-exchanges-id) | Query the derivatives exchange's related data (ID, name, open interest, ...) based on the exchanges' ID |
|
||||
| [/derivatives/exchanges/list](https://docs.coingecko.com/v3.0.1/reference/derivatives-exchanges-list) | Query all the derivatives exchanges with ID and name on CoinGecko |
|
||||
|
||||
## CoinGecko Endpoints: Public Treasuries
|
||||
|
||||
| Endpoint | Description |
|
||||
| ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
|
||||
| [/\{entity}/public\_treasury/\{coin\_id}](/reference/companies-public-treasury) | Query public companies & governments' cryptocurrency holdings by coin ID |
|
||||
| [/public\_treasury/\{entity\_id}](/reference/public-treasury-entity) | Query public companies & governments' cryptocurrency holdings by entity ID |
|
||||
| [/entities/list](/reference/entities-list) | Query all the supported entities on CoinGecko with entities ID, name, symbol, and country |
|
||||
| [/\{entity}/public\_treasury/\{coin\_id}](https://docs.coingecko.com/reference/companies-public-treasury) | Query public companies & governments' cryptocurrency holdings by coin ID |
|
||||
| [/public\_treasury/\{entity\_id}](https://docs.coingecko.com/reference/public-treasury-entity) | Query public companies & governments' cryptocurrency holdings by entity ID |
|
||||
| [/entities/list](https://docs.coingecko.com/reference/entities-list) | Query all the supported entities on CoinGecko with entities ID, name, symbol, and country |
|
||||
|
||||
## CoinGecko Endpoints: General
|
||||
|
||||
| Endpoint | Description |
|
||||
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
|
||||
| [/exchange\_rates](/v3.0.1/reference/exchange-rates) | Query BTC exchange rates with other currencies |
|
||||
| [/asset\_platforms](/v3.0.1/reference/asset-platforms-list) | Query all the asset platforms (blockchain networks) on CoinGecko |
|
||||
| [/token\_lists/\{asset\_platform\_id}/all.json](/v3.0.1/reference/token-lists) | Get full list of tokens of a blockchain network (asset platform) that is supported by Ethereum token list standard |
|
||||
| [/search](/v3.0.1/reference/search-data) | Search for coins, categories and markets listed on CoinGecko |
|
||||
| [/search/trending](/v3.0.1/reference/trending-search) | Query trending search coins, NFTs and categories on CoinGecko in the last 24 hours |
|
||||
| [/global](/v3.0.1/reference/crypto-global) | Query cryptocurrency global data including active cryptocurrencies, markets, total crypto market cap and etc. |
|
||||
| [/global/decentralized\_finance\_defi](/v3.0.1/reference/global-defi) | Query cryptocurrency global decentralized finance (DeFi) data including DeFi market cap, trading volume |
|
||||
| [/exchange\_rates](https://docs.coingecko.com/v3.0.1/reference/exchange-rates) | Query BTC exchange rates with other currencies |
|
||||
| [/asset\_platforms](https://docs.coingecko.com/v3.0.1/reference/asset-platforms-list) | Query all the asset platforms (blockchain networks) on CoinGecko |
|
||||
| [/token\_lists/\{asset\_platform\_id}/all.json](https://docs.coingecko.com/v3.0.1/reference/token-lists) | Get full list of tokens of a blockchain network (asset platform) that is supported by Ethereum token list standard |
|
||||
| [/search](https://docs.coingecko.com/v3.0.1/reference/search-data) | Search for coins, categories and markets listed on CoinGecko |
|
||||
| [/search/trending](https://docs.coingecko.com/v3.0.1/reference/trending-search) | Query trending search coins, NFTs and categories on CoinGecko in the last 24 hours |
|
||||
| [/global](https://docs.coingecko.com/v3.0.1/reference/crypto-global) | Query cryptocurrency global data including active cryptocurrencies, markets, total crypto market cap and etc. |
|
||||
| [/global/decentralized\_finance\_defi](https://docs.coingecko.com/v3.0.1/reference/global-defi) | Query cryptocurrency global decentralized finance (DeFi) data including DeFi market cap, trading volume |
|
||||
|
||||
## Onchain DEX Endpoints (GeckoTerminal)
|
||||
|
||||
| Endpoint | Description |
|
||||
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| [/onchain/simple/networks/../token\_price/..](/v3.0.1/reference/onchain-simple-price) | Get token price based on the provided token contract address on a network |
|
||||
| [/onchain/networks](/v3.0.1/reference/networks-list) | Query all the supported networks on GeckoTerminal |
|
||||
| [/onchain/networks/../dexes](/v3.0.1/reference/dexes-list) | Query all the supported decentralized exchanges (DEXs) based on the provided network on GeckoTerminal |
|
||||
| [/onchain/networks/trending\_pools](/v3.0.1/reference/trending-pools-list) | Query all the trending pools across all networks on GeckoTerminal |
|
||||
| [/onchain/networks/../trending\_pools](/v3.0.1/reference/trending-pools-network) | Query the trending pools based on the provided network |
|
||||
| [/onchain/networks/../pools/..](/v3.0.1/reference/pool-address) | Query the specific pool based on the provided network and pool address |
|
||||
| [/onchain/networks/../pools/multi/..](/v3.0.1/reference/pools-addresses) | Query multiple pools based on the provided network and pool address |
|
||||
| [/onchain/networks/../pools](/v3.0.1/reference/top-pools-network) | Query all the top pools based on the provided network |
|
||||
| [/onchain/networks/../dexes/../pools](/v3.0.1/reference/top-pools-dex) | Query all the top pools based on the provided network and decentralized exchange (DEX) |
|
||||
| [/onchain/networks/../new\_pools](/v3.0.1/reference/latest-pools-network) | Query all the latest pools based on provided network |
|
||||
| [/onchain/networks/new\_pools](/v3.0.1/reference/latest-pools-list) | Query all the latest pools across all networks on GeckoTerminal |
|
||||
| [/onchain/search/pools](/v3.0.1/reference/search-pools) | Search for pools on a network |
|
||||
| [/onchain/networks/../tokens/../pools](/v3.0.1/reference/top-pools-contract-address) | Query top pools based on the provided token contract address on a network |
|
||||
| [/onchain/networks/../tokens/..](/v3.0.1/reference/token-data-contract-address) | Query specific token data based on the provided token contract address on a network |
|
||||
| [/onchain/networks/../tokens/multi/..](/v3.0.1/reference/tokens-data-contract-addresses) | Query multiple tokens data based on the provided token contract addresses on a network |
|
||||
| [/onchain/networks/../tokens/../info](/v3.0.1/reference/token-info-contract-address) | Query token metadata (name, symbol, CoinGecko ID, image, socials, websites, description, etc.) based on a provided token contract address on a network |
|
||||
| [/onchain/networks/../pools/../info](/v3.0.1/reference/pool-token-info-contract-address) | Query pool metadata (base and quote token details, image, socials, websites, description, contract address, etc.) based on a provided pool contract address on a network |
|
||||
| [/onchain/tokens/info\_recently\_updated](/v3.0.1/reference/tokens-info-recent-updated) | Query 100 most recently updated tokens info across all networks on GeckoTerminal |
|
||||
| [/onchain/networks/../pools/../ohlcv/..](/v3.0.1/reference/pool-ohlcv-contract-address) | Get the OHLCV chart (Open, High, Low, Close, Volume) of a pool based on the provided pool address on a network |
|
||||
| [/onchain/networks/../pools/../trades](/v3.0.1/reference/pool-trades-contract-address) | Query the last 300 trades in the past 24 hours based on the provided pool address |
|
||||
| [/onchain/simple/networks/../token\_price/..](https://docs.coingecko.com/v3.0.1/reference/onchain-simple-price) | Get token price based on the provided token contract address on a network |
|
||||
| [/onchain/networks](https://docs.coingecko.com/v3.0.1/reference/networks-list) | Query all the supported networks on GeckoTerminal |
|
||||
| [/onchain/networks/../dexes](https://docs.coingecko.com/v3.0.1/reference/dexes-list) | Query all the supported decentralized exchanges (DEXs) based on the provided network on GeckoTerminal |
|
||||
| [/onchain/networks/trending\_pools](https://docs.coingecko.com/v3.0.1/reference/trending-pools-list) | Query all the trending pools across all networks on GeckoTerminal |
|
||||
| [/onchain/networks/../trending\_pools](https://docs.coingecko.com/v3.0.1/reference/trending-pools-network) | Query the trending pools based on the provided network |
|
||||
| [/onchain/networks/../pools/..](https://docs.coingecko.com/v3.0.1/reference/pool-address) | Query the specific pool based on the provided network and pool address |
|
||||
| [/onchain/networks/../pools/multi/..](https://docs.coingecko.com/v3.0.1/reference/pools-addresses) | Query multiple pools based on the provided network and pool address |
|
||||
| [/onchain/networks/../pools](https://docs.coingecko.com/v3.0.1/reference/top-pools-network) | Query all the top pools based on the provided network |
|
||||
| [/onchain/networks/../dexes/../pools](https://docs.coingecko.com/v3.0.1/reference/top-pools-dex) | Query all the top pools based on the provided network and decentralized exchange (DEX) |
|
||||
| [/onchain/networks/../new\_pools](https://docs.coingecko.com/v3.0.1/reference/latest-pools-network) | Query all the latest pools based on provided network |
|
||||
| [/onchain/networks/new\_pools](https://docs.coingecko.com/v3.0.1/reference/latest-pools-list) | Query all the latest pools across all networks on GeckoTerminal |
|
||||
| [/onchain/search/pools](https://docs.coingecko.com/v3.0.1/reference/search-pools) | Search for pools on a network |
|
||||
| [/onchain/networks/../tokens/../pools](https://docs.coingecko.com/v3.0.1/reference/top-pools-contract-address) | Query top pools based on the provided token contract address on a network |
|
||||
| [/onchain/networks/../tokens/..](https://docs.coingecko.com/v3.0.1/reference/token-data-contract-address) | Query specific token data based on the provided token contract address on a network |
|
||||
| [/onchain/networks/../tokens/multi/..](https://docs.coingecko.com/v3.0.1/reference/tokens-data-contract-addresses) | Query multiple tokens data based on the provided token contract addresses on a network |
|
||||
| [/onchain/networks/../tokens/../info](https://docs.coingecko.com/v3.0.1/reference/token-info-contract-address) | Query token metadata (name, symbol, CoinGecko ID, image, socials, websites, description, etc.) based on a provided token contract address on a network |
|
||||
| [/onchain/networks/../pools/../info](https://docs.coingecko.com/v3.0.1/reference/pool-token-info-contract-address) | Query pool metadata (base and quote token details, image, socials, websites, description, contract address, etc.) based on a provided pool contract address on a network |
|
||||
| [/onchain/tokens/info\_recently\_updated](https://docs.coingecko.com/v3.0.1/reference/tokens-info-recent-updated) | Query 100 most recently updated tokens info across all networks on GeckoTerminal |
|
||||
| [/onchain/networks/../pools/../ohlcv/..](https://docs.coingecko.com/v3.0.1/reference/pool-ohlcv-contract-address) | Get the OHLCV chart (Open, High, Low, Close, Volume) of a pool based on the provided pool address on a network |
|
||||
| [/onchain/networks/../pools/../trades](https://docs.coingecko.com/v3.0.1/reference/pool-trades-contract-address) | Query the last 300 trades in the past 24 hours based on the provided pool address |
|
||||
|
||||
⚡️ Need Real-time Data Streams? Try [WebSocket API](https://docs.coingecko.com/websocket)
|
||||
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -32,7 +32,7 @@ Source: https://docs.coingecko.com/reference/nfts-contract-address-market-chart
|
|||
reference/api-reference/coingecko-pro.json get /nfts/{asset_platform_id}/contract/{contract_address}/market_chart
|
||||
This endpoint allows you **query historical market data of a NFT collection, including floor price, market cap, and 24hr volume, by number of days away from now based on the provided contract address**
|
||||
|
||||
* This endpoint doesn't support Solana NFT and Art Blocks, please use [/nfts/\{id}/market\_chart](/reference/nfts-id-market-chart) endpoint instead.
|
||||
* This endpoint doesn't support Solana NFT and Art Blocks, please use [/nfts/\{id}/market\_chart](https://docs.coingecko.com/reference/nfts-id-market-chart) endpoint instead.
|
||||
* Data Granularity (auto):
|
||||
* 1-14 days from now = **5-minutely** data
|
||||
* 15 days & above from now = **daily** data (00:00 UTC)
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ Here are the official API SDKs maintained by us.
|
|||
|
||||
Want us to support your favorite programming language? Let us know [here](https://forms.gle/JJLH3SXiL2eJaGzBA)!
|
||||
|
||||
**Not a developer?** Fred not, check our no-code tutorial for beginners here: [Tutorials (Beginner-friendly)](/docs/tutorials-beginner-friendly)
|
||||
**Not a developer?** Fred not, check our no-code tutorial for beginners here: [Tutorials (Beginner-friendly)](https://docs.coingecko.com/docs/tutorials-beginner-friendly)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -338,16 +338,16 @@ Wonder how to use different endpoints together? This is the perfect place for yo
|
|||
|
||||
### "Discovery/Navigational Endpoints"
|
||||
|
||||
* [/coins/list](/reference/coins-list) — can be used to query all the supported coins on CoinGecko with names, symbols and coin IDs that can be used in other endpoints.
|
||||
* [/search/trending](/reference/trending-search) — can be used to query trending search coins, categories and NFTs on CoinGecko.
|
||||
* [/coins/list](https://docs.coingecko.com/reference/coins-list) — can be used to query all the supported coins on CoinGecko with names, symbols and coin IDs that can be used in other endpoints.
|
||||
* [/search/trending](https://docs.coingecko.com/reference/trending-search) — can be used to query trending search coins, categories and NFTs on CoinGecko.
|
||||
|
||||
### "Supporting Endpoints"
|
||||
|
||||
* [/simple/supported\_vs\_currencies](/reference/simple-supported-currencies) — can be used to query the list of currencies for other endpoints that include parameters like `vs_currencies`, allowing to obtain the corresponding data for those currencies.
|
||||
* [/asset\_platforms](/reference/asset-platforms-list) — can be used to query the list of asset platforms for other endpoints that contain parameters like `id` or `ids` (asset platforms), allowing the retrieval of corresponding data for these asset platforms.
|
||||
* [/simple/supported\_vs\_currencies](https://docs.coingecko.com/reference/simple-supported-currencies) — can be used to query the list of currencies for other endpoints that include parameters like `vs_currencies`, allowing to obtain the corresponding data for those currencies.
|
||||
* [/asset\_platforms](https://docs.coingecko.com/reference/asset-platforms-list) — can be used to query the list of asset platforms for other endpoints that contain parameters like `id` or `ids` (asset platforms), allowing the retrieval of corresponding data for these asset platforms.
|
||||
|
||||
* [/simple/price](/reference/simple-price) — can be used to query the prices of coins using the unique coin IDs that can be obtained from the "Discovery/Navigational Endpoints" mentioned above.
|
||||
* [/coins/\{id}](/reference/coins-id) — can be used to query the coin data using the unique coin IDs that can be obtained from the "Discovery/Navigational Endpoints" mentioned above.
|
||||
* [/simple/price](https://docs.coingecko.com/reference/simple-price) — can be used to query the prices of coins using the unique coin IDs that can be obtained from the "Discovery/Navigational Endpoints" mentioned above.
|
||||
* [/coins/\{id}](https://docs.coingecko.com/reference/coins-id) — can be used to query the coin data using the unique coin IDs that can be obtained from the "Discovery/Navigational Endpoints" mentioned above.
|
||||
|
||||
## User Journey for Onchain DEX API Endpoints (GeckoTerminal data)
|
||||
|
||||
|
|
@ -355,16 +355,16 @@ Wonder how to use different endpoints together? This is the perfect place for yo
|
|||
|
||||
### "Discovery/Navigational Endpoints"
|
||||
|
||||
* [/onchain/trending\_pools](/reference/trending-pools-list) - can be used to query trending pools across all networks on GeckoTerminal.
|
||||
* [/onchain/search/pools](/reference/search-pools) - can be used to search for any pools on GeckoTerminal.
|
||||
* [/onchain/trending\_pools](https://docs.coingecko.com/reference/trending-pools-list) - can be used to query trending pools across all networks on GeckoTerminal.
|
||||
* [/onchain/search/pools](https://docs.coingecko.com/reference/search-pools) - can be used to search for any pools on GeckoTerminal.
|
||||
|
||||
### "Supporting Endpoints"
|
||||
|
||||
* [/onchain/networks-list](/reference/networks-list) - can be used to query all the supported networks on GeckoTerminal.
|
||||
* [/onchain/networks/\{network}/dexes](/reference/dexes-list) - can be used to query all the supported decentralized exchanges (DEXs/`dexes`) on GeckoTerminal based on network id that can be obtained from the endpoint mentioned above.
|
||||
* [/onchain/networks-list](https://docs.coingecko.com/reference/networks-list) - can be used to query all the supported networks on GeckoTerminal.
|
||||
* [/onchain/networks/\{network}/dexes](https://docs.coingecko.com/reference/dexes-list) - can be used to query all the supported decentralized exchanges (DEXs/`dexes`) on GeckoTerminal based on network id that can be obtained from the endpoint mentioned above.
|
||||
|
||||
* [/onchain/simple/networks/\{network}/token\_price/\{addresses}](/reference/onchain-simple-price) - can be used to query any token price using the token address and network id that can be obtained from the "Discovery/Navigational Endpoints" and "Supporting Endpoints" mentioned above.
|
||||
* [/onchain/networks/\{network}/pools/\{address}](/reference/pool-address) - can be used to query the data of a specific pool based on the pool address and network id that can be obtained from the "Discovery/Navigational Endpoints" and "Supporting Endpoints" mentioned above.
|
||||
* [/onchain/simple/networks/\{network}/token\_price/\{addresses}](https://docs.coingecko.com/reference/onchain-simple-price) - can be used to query any token price using the token address and network id that can be obtained from the "Discovery/Navigational Endpoints" and "Supporting Endpoints" mentioned above.
|
||||
* [/onchain/networks/\{network}/pools/\{address}](https://docs.coingecko.com/reference/pool-address) - can be used to query the data of a specific pool based on the pool address and network id that can be obtained from the "Discovery/Navigational Endpoints" and "Supporting Endpoints" mentioned above.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -386,7 +386,7 @@ Choosing between a Demo and Pro key for your MCP server impacts your access to d
|
|||
| **Rate Limit** | 30 calls/min | Starts at 500 calls/min |
|
||||
| **Monthly Credits** | 10,000 | Starts at 500,000 |
|
||||
| **Historical Data** | Past 1 year | From 2013 until now |
|
||||
| **MCP Tools** | Limited access | Full access, including exclusive tools:<br />- [Top Gainers & Losers](/reference/coins-top-gainers-losers)<br />- [NFTs Collection Historical Chart](/reference/nfts-id-market-chart)<br />- [🔥 Megafilter for Pools](/reference/pools-megafilter)<br />- [Pools by Category ID](/reference/pools-category) |
|
||||
| **MCP Tools** | Limited access | Full access, including exclusive tools:<br />- [Top Gainers & Losers](https://docs.coingecko.com/reference/coins-top-gainers-losers)<br />- [NFTs Collection Historical Chart](https://docs.coingecko.com/reference/nfts-id-market-chart)<br />- [🔥 Megafilter for Pools](https://docs.coingecko.com/reference/pools-megafilter)<br />- [Pools by Category ID](https://docs.coingecko.com/reference/pools-category) |
|
||||
|
||||
🔥 Ready to upgrade? Explore [our API plans](https://www.coingecko.com/en/api/pricing).
|
||||
|
||||
|
|
@ -399,7 +399,7 @@ When running our CoinGecko MCP server, you can choose how the LLM client discove
|
|||
|
||||
For a deeper dive, read the [official documentation](https://www.stainless.com/changelog/mcp-dynamic-tools) from Stainless.
|
||||
|
||||
To help AI models interact with CoinGecko data effectively, we provide an `llms.txt` file at [/llms-full.txt](/llms-full.txt). This file gives models context on how to best query our API, ensuring more accurate and efficient data retrieval. We recommend utilizing this in your integrations.
|
||||
To help AI models interact with CoinGecko data effectively, we provide an `llms.txt` file at [/llms-full.txt](https://docs.coingecko.com/llms-full.txt). This file gives models context on how to best query our API, ensuring more accurate and efficient data retrieval. We recommend utilizing this in your integrations.
|
||||
|
||||
CoinGecko MCP Server is powered by [Stainless](https://www.stainless.com/) ✱
|
||||
|
||||
|
|
@ -489,7 +489,7 @@ Some of the useful links to help you navigate while using the CoinGecko API
|
|||
|
||||
#### Using `llms.txt` for AI use cases
|
||||
|
||||
* [/llms-full.txt](/llms-full.txt)
|
||||
* [/llms-full.txt](https://docs.coingecko.com/llms-full.txt)
|
||||
|
||||
#### Attributing CoinGecko Brand
|
||||
|
||||
|
|
@ -542,14 +542,14 @@ Due to recent updates to MagicEden's API, we are updating our integration. Durin
|
|||
|
||||
We've added support for bonding curve (e.g. launchpad graduation from PumpFun) data across multiple token endpoints:
|
||||
|
||||
* [Token Data by Token Address](/reference/token-data-contract-address) — `/onchain/networks/{network}/tokens/{address}`
|
||||
* [Tokens Data by Token Addresses](/reference/tokens-data-contract-addresses) — `/onchain/networks/{network}/tokens/multi/{addresses}`
|
||||
* [Token Info by Token Address](/reference/token-info-contract-address) — `/onchain/networks/{network}/tokens/{address}/info`
|
||||
* [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) — `/onchain/networks/{network}/pools/{pool_address}/info`
|
||||
* [Token Data by Token Address](https://docs.coingecko.com/reference/token-data-contract-address) — `/onchain/networks/{network}/tokens/{address}`
|
||||
* [Tokens Data by Token Addresses](https://docs.coingecko.com/reference/tokens-data-contract-addresses) — `/onchain/networks/{network}/tokens/multi/{addresses}`
|
||||
* [Token Info by Token Address](https://docs.coingecko.com/reference/token-info-contract-address) — `/onchain/networks/{network}/tokens/{address}/info`
|
||||
* [Pool Tokens Info by Pool Address](https://docs.coingecko.com/reference/pool-token-info-contract-address) — `/onchain/networks/{network}/pools/{pool_address}/info`
|
||||
|
||||
### Megafilter: Ascending Sort Order for Price Change %
|
||||
|
||||
The [Megafilter for Pools](/reference/pools-megafilter) endpoint now supports ascending sorting for price change percentage:
|
||||
The [Megafilter for Pools](https://docs.coingecko.com/reference/pools-megafilter) endpoint now supports ascending sorting for price change percentage:
|
||||
|
||||
* `m5_price_change_percentage_asc`
|
||||
* `h1_price_change_percentage_asc`
|
||||
|
|
@ -558,7 +558,7 @@ The [Megafilter for Pools](/reference/pools-megafilter) endpoint now supports as
|
|||
|
||||
### Token OHLCV Endpoint Fix to respect Specified Token Address
|
||||
|
||||
We've fixed an issue where the [Token OHLCV chart by Token Address](/reference/token-ohlcv-token-address) endpoint returned data for the base token of the top pool instead of the requested token. It will now always return data for the specified token address.
|
||||
We've fixed an issue where the [Token OHLCV chart by Token Address](https://docs.coingecko.com/reference/token-ohlcv-token-address) endpoint returned data for the base token of the top pool instead of the requested token. It will now always return data for the specified token address.
|
||||
</Update>
|
||||
|
||||
<Update label="September 2025">
|
||||
|
|
@ -582,17 +582,17 @@ We're broadening our SDK coverage to make treasury-level insights more powerful
|
|||
We're also surfacing new tools through the MCP to give developers a richer, faster way to query exchanges, NFTs, and onchain activity.
|
||||
|
||||
* New tools:
|
||||
* Exchange coverage with [/exchanges/list](reference/exchanges-list), [/exchanges/](reference/exchanges-id), [/exchanges//tickers](reference/exchanges-id-tickers), and [/exchanges//volume\_chart/range](reference/exchanges-id-volume-chart-range)
|
||||
* NFT markets with [/nfts/markets](reference/nfts-markets)
|
||||
* Multi-address queries with [/onchain/networks//pools/multi/](reference/pools-addresses) and [/onchain/networks//tokens/multi/](reference/tokens-data-contract-addresses)
|
||||
* Exchange coverage with [/exchanges/list](https://docs.coingecko.com/reference/exchanges-list), [/exchanges/](https://docs.coingecko.com/reference/exchanges-id), [/exchanges//tickers](https://docs.coingecko.com/reference/exchanges-id-tickers), and [/exchanges//volume\_chart/range](https://docs.coingecko.com/reference/exchanges-id-volume-chart-range)
|
||||
* NFT markets with [/nfts/markets](https://docs.coingecko.com/reference/nfts-markets)
|
||||
* Multi-address queries with [/onchain/networks//pools/multi/](https://docs.coingecko.com/reference/pools-addresses) and [/onchain/networks//tokens/multi/](https://docs.coingecko.com/reference/tokens-data-contract-addresses)
|
||||
* Retired tools:
|
||||
* We've removed endpoints such as [/coins/list](reference/coins-list), [/onchain/networks/trending\_pools](reference/trending-pools-network), and single-address pool/token queries in favor of more scalable multi-address endpoints
|
||||
* We've removed endpoints such as [/coins/list](https://docs.coingecko.com/reference/coins-list), [/onchain/networks/trending\_pools](https://docs.coingecko.com/reference/trending-pools-network), and single-address pool/token queries in favor of more scalable multi-address endpoints
|
||||
|
||||
### Friendlier Time-related MCP Queries with ISO Support
|
||||
|
||||
Time-based queries just got easier. MCP tools now accept **ISO date strings** (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`) alongside UNIX timestamps.
|
||||
|
||||
For example, when using the [Coin Historical Chart Data within Time Range](reference/coins-id-market-chart-range) tool, you can now pass ISO date strings directly instead of converting them into UNIX timestamps for your LLM tools.
|
||||
For example, when using the [Coin Historical Chart Data within Time Range](https://docs.coingecko.com/reference/coins-id-market-chart-range) tool, you can now pass ISO date strings directly instead of converting them into UNIX timestamps for your LLM tools.
|
||||
|
||||
**CoinGecko API Team**
|
||||
|
||||
|
|
@ -1644,13 +1644,13 @@ Historical data for new non-native or bridged assets will only be available from
|
|||
|
||||
For a finalised list of token contracts and API IDs that have been separated from its native asset page and listed individually, please refer to this [Google Sheets](https://docs.google.com/spreadsheets/d/15FyY1gvUi20LdnlJRly-pXvm5ATNbFbSy06VoI1vVs4/edit?usp=sharing)
|
||||
|
||||
You may also identify the list of bridged coins via API: you may also use [/categories/list endpoint](/reference/coins-categories-list) to look for bridged categories such as:
|
||||
You may also identify the list of bridged coins via API: you may also use [/categories/list endpoint](https://docs.coingecko.com/reference/coins-categories-list) to look for bridged categories such as:
|
||||
|
||||
1. bridged-usdc
|
||||
2. bridged-wbtc
|
||||
3. bridged-weth
|
||||
|
||||
Then you may use [/coins/market endpoint](/reference/coins-markets) to retrieve the list of coins
|
||||
Then you may use [/coins/market endpoint](https://docs.coingecko.com/reference/coins-markets) to retrieve the list of coins
|
||||
|
||||
## Enhancing Your Access to Even Fresher Data!
|
||||
|
||||
|
|
@ -1735,21 +1735,21 @@ You can now query coin prices in the 13 new currencies for the following 3 endpo
|
|||
|
||||
### Onchain: Simple Price - Increased Token Address Limit from 30 to 100
|
||||
|
||||
[Token Price by Token Addresses](/reference/onchain-simple-price) now allows to input up to 100 contract addresses, instead of 30.
|
||||
[Token Price by Token Addresses](https://docs.coingecko.com/reference/onchain-simple-price) now allows to input up to 100 contract addresses, instead of 30.
|
||||
|
||||
* You may now retrieve data of up to 100 token prices of a specific network, in one single request.
|
||||
* Available exclusively to Pro API paid plan subscribers.
|
||||
|
||||
### Onchain: Recently Updated Info - Added Filter by Network
|
||||
|
||||
[Most Recently Updated Token List](/reference/tokens-info-recent-updated) now allows to filter by blockchain network, by flagging the `network` parameter. e.g. `network=eth`.
|
||||
[Most Recently Updated Token List](https://docs.coingecko.com/reference/tokens-info-recent-updated) now allows to filter by blockchain network, by flagging the `network` parameter. e.g. `network=eth`.
|
||||
|
||||
* You can use the `network` parameter to retrieve the 100 most recently updated token info of a specific network.
|
||||
* View list of supported network via [Supported Networks List](https://docs.coingecko.com/reference/networks-list) endpoint.
|
||||
|
||||
### NFT Collection Data - Included Banner Image
|
||||
|
||||
[NFTs Collection Data by ID](/reference/nfts-id) now provides banner image of a NFT collection.
|
||||
[NFTs Collection Data by ID](https://docs.coingecko.com/reference/nfts-id) now provides banner image of a NFT collection.
|
||||
|
||||
View banner image [example](https://coin-images.coingecko.com/nft_contracts/images/38/pudgy-penguins-banner.png?1708416126) on: [https://www.coingecko.com/en/nft/pudgy-penguins](https://www.coingecko.com/en/nft/pudgy-penguins)
|
||||
|
||||
|
|
@ -1766,11 +1766,11 @@ The last completed UTC day (00:00) is available 5 minutes after midnight on the
|
|||
|
||||
### Asset Platforms - Included Images of Blockchain Network Logos
|
||||
|
||||
[Asset Platforms List (ID Map)](/reference/asset-platforms-list) now provides the logos of blockchain networks.
|
||||
[Asset Platforms List (ID Map)](https://docs.coingecko.com/reference/asset-platforms-list) now provides the logos of blockchain networks.
|
||||
|
||||
### Coins Categories - Included Ids of Top 3 Coins
|
||||
|
||||
[Coins Categories List with Market Data](/reference/coins-categories) now provides coins id of the top 3 coins of a category.
|
||||
[Coins Categories List with Market Data](https://docs.coingecko.com/reference/coins-categories) now provides coins id of the top 3 coins of a category.
|
||||
|
||||
### Circulating Supply Chart and Total Supply Chart - Fixed '0' data issue
|
||||
|
||||
|
|
@ -1787,8 +1787,8 @@ For the following **Enterprise-plan** exclusive endpoints below, there was a bug
|
|||
|
||||
The cache & update frequency of the following endpoints have been improved from every 30 minutes to every 15 minutes:
|
||||
|
||||
* [/coins//ohlc](/reference/coins-id-ohlc)
|
||||
* [/coins//ohlc/range](/reference/coins-id-ohlc-range)
|
||||
* [/coins//ohlc](https://docs.coingecko.com/reference/coins-id-ohlc)
|
||||
* [/coins//ohlc/range](https://docs.coingecko.com/reference/coins-id-ohlc-range)
|
||||
</Update>
|
||||
|
||||
<Update label="August 2024">
|
||||
|
|
@ -1798,15 +1798,15 @@ The cache & update frequency of the following endpoints have been improved from
|
|||
|
||||
We've added 'user\_favorites\_count', and 'ath' (all-time-high) related data to the following NFT endpoints:
|
||||
|
||||
* [/nfts/](/reference/nfts-id)
|
||||
* [/nfts//contract/](/reference/nfts-contract-address)
|
||||
* [/nfts/](https://docs.coingecko.com/reference/nfts-id)
|
||||
* [/nfts//contract/](https://docs.coingecko.com/reference/nfts-contract-address)
|
||||
|
||||
**Example of responses:**
|
||||
|
||||
<Update label="May 2024">
|
||||
## Introduced /coins/id/ohlc/range endpoint
|
||||
|
||||
We've introduced a new endpoint [/coins//ohlc/range](/reference/coins-id-ohlc-range).
|
||||
We've introduced a new endpoint [/coins//ohlc/range](https://docs.coingecko.com/reference/coins-id-ohlc-range).
|
||||
|
||||
This endpoint allows you to get the OHLC chart (Open, High, Low, Close) of a coin within a range of timestamp based on particular coin id.
|
||||
|
||||
|
|
@ -1814,7 +1814,7 @@ Please note that this endpoint is available exclusively for **paid plan subscrib
|
|||
|
||||
## Added interval hourly params to /coins/id/ohlc
|
||||
|
||||
We've expanded functionality to include support for the `interval=hourly` parameter within the [/coins//ohlc](/reference/coins-id-ohlc) endpoint.
|
||||
We've expanded functionality to include support for the `interval=hourly` parameter within the [/coins//ohlc](https://docs.coingecko.com/reference/coins-id-ohlc) endpoint.
|
||||
|
||||
Users can use this parameter to retrieve OHLC (Open/High/Low/Close) data on a hourly interval for up to 90 days of the date range.
|
||||
|
||||
|
|
@ -1828,7 +1828,7 @@ Example of endpoint request:
|
|||
|
||||
🗓️ **April 30, 2024**
|
||||
|
||||
We've now enhanced the [/coins/list](/reference/coins-list) endpoint to include inactive coins
|
||||
We've now enhanced the [/coins/list](https://docs.coingecko.com/reference/coins-list) endpoint to include inactive coins
|
||||
|
||||
* You may access the inactive coins by specifying `status=inactive` in your query
|
||||
* Example of endpoint request:\
|
||||
|
|
@ -1836,11 +1836,11 @@ We've now enhanced the [/coins/list](/reference/coins-list) endpoint to include
|
|||
|
||||
Additionally, historical data for inactive coins can be queried using their IDs in the following endpoints:
|
||||
|
||||
* [/coins//history](/reference/coins-id-history)
|
||||
* [/coins//market\_chart](/reference/coins-id-market-chart)
|
||||
* [/coins//market\_chart/range](/reference/coins-id-market-chart-range)
|
||||
* [/coins//contract//market\_chart](/reference/contract-address-market-chart)
|
||||
* [/coins//contract//market\_chart/range](/reference/contract-address-market-chart-range)
|
||||
* [/coins//history](https://docs.coingecko.com/reference/coins-id-history)
|
||||
* [/coins//market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart)
|
||||
* [/coins//market\_chart/range](https://docs.coingecko.com/reference/coins-id-market-chart-range)
|
||||
* [/coins//contract//market\_chart](https://docs.coingecko.com/reference/contract-address-market-chart)
|
||||
* [/coins//contract//market\_chart/range](https://docs.coingecko.com/reference/contract-address-market-chart-range)
|
||||
|
||||
Please note that these features are available exclusively for **paid plan subscribers only**
|
||||
</Update>
|
||||
|
|
@ -1850,7 +1850,7 @@ Please note that these features are available exclusively for **paid plan subscr
|
|||
|
||||
🗓️ **March 27, 2024**
|
||||
|
||||
We've introduced a new endpoint [/key](/reference/api-usage) for conveniently monitoring your account's API usage, including rate limits and remaining credits.
|
||||
We've introduced a new endpoint [/key](https://docs.coingecko.com/reference/api-usage) for conveniently monitoring your account's API usage, including rate limits and remaining credits.
|
||||
|
||||
**Example of responses**:
|
||||
|
||||
|
|
@ -1864,17 +1864,17 @@ We've introduced a new endpoint [/key](/reference/api-usage) for conveniently mo
|
|||
Example of responses:
|
||||
|
||||
* We've added sorting parameters such as order= `h24_volume_usd_desc` and order=` h24_tx_count_desc` for /pools endpoints
|
||||
* The 'token' parameter within the [/ohlcv ](/reference/pool-ohlcv-contract-address) endpoint can now accept a token address, provided it exists in the queried pool, to return OHLCV data\
|
||||
* The 'token' parameter within the [/ohlcv ](https://docs.coingecko.com/reference/pool-ohlcv-contract-address) endpoint can now accept a token address, provided it exists in the queried pool, to return OHLCV data\
|
||||
Example of endpoint request (**token=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2**):\
|
||||
`https://pro-api.coingecko.com/api/v3/onchain/networks/eth/pools/0x06da0fd433c1a5d7a4faa01111c044910a184553/ohlcv/day?token=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&x_cg_pro_api_key=YOUR_API_KEY`
|
||||
* [/ohlcv ](/reference/pool-ohlcv-contract-address) endpoint now includes the base and target token metadata in the response\
|
||||
* [/ohlcv ](https://docs.coingecko.com/reference/pool-ohlcv-contract-address) endpoint now includes the base and target token metadata in the response\
|
||||
Example of responses:
|
||||
|
||||
## Introduced /networks/network/trending\_pools endpoint (Onchain/GT)
|
||||
|
||||
🗓️ **February 19, 2024**
|
||||
|
||||
Trending Pools endpoint, [/networks//trending\_pools](/reference/trending-pools-network) is now available to fetch a list of pools that are trending as seen on GeckoTerminal based on web visits and on-chain activities.
|
||||
Trending Pools endpoint, [/networks//trending\_pools](https://docs.coingecko.com/reference/trending-pools-network) is now available to fetch a list of pools that are trending as seen on GeckoTerminal based on web visits and on-chain activities.
|
||||
|
||||
## Introduced /search/pools endpoint (Onchain/GT)
|
||||
|
||||
|
|
@ -1888,7 +1888,7 @@ Added new endpoint to search for pools /search/pools based on keywords passed in
|
|||
|
||||
🗓️ **January 18, 2024**
|
||||
|
||||
We've included a new field "whitepaper" under "links" section for [/coins/](/reference/coins-id) endpoint
|
||||
We've included a new field "whitepaper" under "links" section for [/coins/](https://docs.coingecko.com/reference/coins-id) endpoint
|
||||
|
||||
**Example of responses:**
|
||||
|
||||
|
|
@ -1897,7 +1897,7 @@ We've included a new field "whitepaper" under "links" section for [/coins/](/ref
|
|||
|
||||
🗓️ **December 13, 2023**
|
||||
|
||||
The following data is now deprecated for [/coins/](/reference/coins-id) endpoint:
|
||||
The following data is now deprecated for [/coins/](https://docs.coingecko.com/reference/coins-id) endpoint:
|
||||
|
||||
* coingecko\_rank
|
||||
* coingecko\_score
|
||||
|
|
@ -1915,14 +1915,14 @@ The following data is now deprecated for [/coins/](/reference/coins-id) endpoint
|
|||
|
||||
We've introduced Historical Total Supply data to Enterprise plan subscribers via these 2 exclusive endpoints:
|
||||
|
||||
* [/coins//total\_supply\_chart](/reference/coins-id-total-supply-chart) : get historical total supply of a coin, by number of days away from now.
|
||||
* [/coins//total\_supply\_chart/range](/reference/coins-id-total-supply-chart-range) : get historical total supply of a coin, within a range of timestamp.
|
||||
* [/coins//total\_supply\_chart](https://docs.coingecko.com/reference/coins-id-total-supply-chart) : get historical total supply of a coin, by number of days away from now.
|
||||
* [/coins//total\_supply\_chart/range](https://docs.coingecko.com/reference/coins-id-total-supply-chart-range) : get historical total supply of a coin, within a range of timestamp.
|
||||
|
||||
## Included more trending coins
|
||||
|
||||
🗓️ **December 07, 2023**
|
||||
|
||||
We've expanded the capabilities of the [/search/trending](/reference/trending-search) endpoint.
|
||||
We've expanded the capabilities of the [/search/trending](https://docs.coingecko.com/reference/trending-search) endpoint.
|
||||
|
||||
It now supports up to 15 trending coins, a significant increase from the previous limit of 7.
|
||||
|
||||
|
|
@ -1940,14 +1940,14 @@ Pool data now returns transaction stats for the last 1 hour. Unique buyers and s
|
|||
|
||||
The web\_slug data is now available in the following endpoints.
|
||||
|
||||
* [/coins/](/reference/coins-id)
|
||||
* [/coins//contract/](/reference/coins-contract-address)
|
||||
* [/coins/](https://docs.coingecko.com/reference/coins-id)
|
||||
* [/coins//contract/](https://docs.coingecko.com/reference/coins-contract-address)
|
||||
|
||||
This addition allows users to accurately link to a CoinGecko coin page using [www.coingecko.com/en/](http://www.coingecko.com/en/\{web_slug}).
|
||||
|
||||
**Example of responses:**
|
||||
|
||||
For the [/asset\_platforms](/reference/asset-platforms-list) endpoint, we've introduced the native\_coin\_id data. This enables users to obtain the coin ID of different blockchain networks or asset platforms that may not have a contract address to look up
|
||||
For the [/asset\_platforms](https://docs.coingecko.com/reference/asset-platforms-list) endpoint, we've introduced the native\_coin\_id data. This enables users to obtain the coin ID of different blockchain networks or asset platforms that may not have a contract address to look up
|
||||
|
||||
**Example of responses:**
|
||||
|
||||
|
|
@ -1955,13 +1955,13 @@ For the [/asset\_platforms](/reference/asset-platforms-list) endpoint, we've int
|
|||
|
||||
🗓️ **November 10, 2023**
|
||||
|
||||
Inspired by CoinGecko API most popular endpoint, we have launched the [/simple/networks//token\_price/](/reference/onchain-simple-price), simple endpoint. Simply pass in addresses of any tokens on supported blockchain and get price data for it
|
||||
Inspired by CoinGecko API most popular endpoint, we have launched the [/simple/networks//token\_price/](https://docs.coingecko.com/reference/onchain-simple-price), simple endpoint. Simply pass in addresses of any tokens on supported blockchain and get price data for it
|
||||
|
||||
## Introduced /networks/network/pools/pool\_address/trades endpoint (Onchain/GT)
|
||||
|
||||
🗓️ **November 08, 2023**
|
||||
|
||||
You can now get the latest 300 trades in the past 24 hours of a given pool from this endpoint [/networks//pools//trades](/reference/pool-trades-contract-address). You may optionally filter by trade size as well. You can now build your own telegram bot alert!
|
||||
You can now get the latest 300 trades in the past 24 hours of a given pool from this endpoint [/networks//pools//trades](https://docs.coingecko.com/reference/pool-trades-contract-address). You may optionally filter by trade size as well. You can now build your own telegram bot alert!
|
||||
</Update>
|
||||
|
||||
<Update label="October 2023">
|
||||
|
|
@ -1971,9 +1971,9 @@ You can now get the latest 300 trades in the past 24 hours of a given pool from
|
|||
|
||||
You can now fetch token information such as name, image, social links, and description via these endpoints:
|
||||
|
||||
* To fetch information of tokens inside a pool, use [/networks//pools//info](/reference/pool-token-info-contract-address)
|
||||
* To fetch information of a specific token use [/networks//tokens//info](/reference/token-info-contract-address)
|
||||
* If you like to get token information of the most recently updated tokens, use [/tokens/info\_recently\_updated](/reference/tokens-info-recent-updated)
|
||||
* To fetch information of tokens inside a pool, use [/networks//pools//info](https://docs.coingecko.com/reference/pool-token-info-contract-address)
|
||||
* To fetch information of a specific token use [/networks//tokens//info](https://docs.coingecko.com/reference/token-info-contract-address)
|
||||
* If you like to get token information of the most recently updated tokens, use [/tokens/info\_recently\_updated](https://docs.coingecko.com/reference/tokens-info-recent-updated)
|
||||
</Update>
|
||||
|
||||
<Update label="September 2023">
|
||||
|
|
@ -1998,34 +1998,34 @@ Added new endpoints to allow querying multiple pools and tokens in a single API
|
|||
|
||||
## Introduced precision params for other endpoints
|
||||
|
||||
The uses of 'precision' parameter allows to specify price data in full or 0-18 decimals, and previously was only made available for [/simple/price](/reference/simple-price) and [/simple/token\_price/](/reference/simple-token-price) endpoints.
|
||||
The uses of 'precision' parameter allows to specify price data in full or 0-18 decimals, and previously was only made available for [/simple/price](https://docs.coingecko.com/reference/simple-price) and [/simple/token\_price/](https://docs.coingecko.com/reference/simple-token-price) endpoints.
|
||||
|
||||
This parameter is now supported for more endpoints as listed below:
|
||||
|
||||
* [/coins/markets](/reference/coins-markets)
|
||||
* [/coins/market\_chart](/reference/coins-id-market-chart)
|
||||
* [/coins/market\_chart/range](/reference/coins-id-market-chart)
|
||||
* [/coins//contract//market\_chart](/reference/contract-address-market-chart)
|
||||
* [/coins//contract//market\_chart/range](/reference/contract-address-market-chart-range)
|
||||
* [/coins//ohlc](/reference/coins-id-ohlc)
|
||||
* [/coins/markets](https://docs.coingecko.com/reference/coins-markets)
|
||||
* [/coins/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart)
|
||||
* [/coins/market\_chart/range](https://docs.coingecko.com/reference/coins-id-market-chart)
|
||||
* [/coins//contract//market\_chart](https://docs.coingecko.com/reference/contract-address-market-chart)
|
||||
* [/coins//contract//market\_chart/range](https://docs.coingecko.com/reference/contract-address-market-chart-range)
|
||||
* [/coins//ohlc](https://docs.coingecko.com/reference/coins-id-ohlc)
|
||||
|
||||
## Multiple Improvements
|
||||
|
||||
We've made enhancements to the /search/trending and /coins/asset\_platform\_id/contract/contract\_address endpoints:
|
||||
|
||||
* Top 5 trending NFT data (based on high trading volume in the last 24 hours) is now included in the [/search/trending](/reference/trending-search) endpoint
|
||||
* Near Protocol contract address (e.g. wrap.near) is now supported for [/coins//contract/ ](/reference/coins-contract-address) endpoint
|
||||
* Top 5 trending NFT data (based on high trading volume in the last 24 hours) is now included in the [/search/trending](https://docs.coingecko.com/reference/trending-search) endpoint
|
||||
* Near Protocol contract address (e.g. wrap.near) is now supported for [/coins//contract/ ](https://docs.coingecko.com/reference/coins-contract-address) endpoint
|
||||
</Update>
|
||||
|
||||
<Update label="May 2023">
|
||||
## Multiple Improvements (Onchain/GT)
|
||||
|
||||
* Token metadata such as name, symbol, and CoinGecko ID are now returned in the responses for pools endpoints. Users will need to pass in this attribute include=base\_token, quote\_token
|
||||
* CoinGecko asset platform ID added to the response for [/networks](/reference/networks-list) endpoint
|
||||
* CoinGecko asset platform ID added to the response for [/networks](https://docs.coingecko.com/reference/networks-list) endpoint
|
||||
|
||||
## Added interval daily params to /coins/id/ohlc
|
||||
|
||||
The [/coins//ohlc](/reference/coins-id-ohlc) endpoint now supports the "interval=daily" parameter for Paid Plan Subscribers
|
||||
The [/coins//ohlc](https://docs.coingecko.com/reference/coins-id-ohlc) endpoint now supports the "interval=daily" parameter for Paid Plan Subscribers
|
||||
|
||||
Users can use this parameter to retrieve OHLC (Open/High/Low/Close) data on a daily interval for up to 180 days of date range.
|
||||
</Update>
|
||||
|
|
@ -2035,7 +2035,7 @@ Users can use this parameter to retrieve OHLC (Open/High/Low/Close) data on a da
|
|||
|
||||
🗓️ **April 26, 2023**
|
||||
|
||||
We've added 'watchlist\_portfolio\_users' field to [/coins/](/reference/coins-id) endpoint responses.
|
||||
We've added 'watchlist\_portfolio\_users' field to [/coins/](https://docs.coingecko.com/reference/coins-id) endpoint responses.
|
||||
|
||||
This refers to number of users who added the coin into a watchlist or portfolio.
|
||||
|
||||
|
|
@ -2055,10 +2055,10 @@ We've increased the rate limit of Public Plan from 10 calls per minute to 30 cal
|
|||
* reserve\_in\_usd added to the pools endpoint response. This returns the total liquidity/reserve of the pool in USD
|
||||
* pool\_created\_at added to the pools endpoint response
|
||||
|
||||
Example of responses for [/networks//pools/](/reference/pool-address) :
|
||||
Example of responses for [/networks//pools/](https://docs.coingecko.com/reference/pool-address) :
|
||||
|
||||
* [/networks//new\_pools](/reference/latest-pools-network) endpoint added to query new pools discovered for a network
|
||||
* [/networks/new\_pools](/reference/latest-pools-list) endpoint added to query new pools discovered across all networks
|
||||
* [/networks//new\_pools](https://docs.coingecko.com/reference/latest-pools-network) endpoint added to query new pools discovered for a network
|
||||
* [/networks/new\_pools](https://docs.coingecko.com/reference/latest-pools-list) endpoint added to query new pools discovered across all networks
|
||||
|
||||
## Included new fields
|
||||
|
||||
|
|
@ -2066,9 +2066,9 @@ Example of responses for [/networks//pools/](/reference/pool-address) :
|
|||
|
||||
We've added "symbol" field to these NFT endpoints responses:
|
||||
|
||||
* [/nfts/markets](/reference/nfts-markets)
|
||||
* [/nfts/ ](/reference/nfts-id)
|
||||
* [/nfts//contract/](/reference/nfts-contract-address)
|
||||
* [/nfts/markets](https://docs.coingecko.com/reference/nfts-markets)
|
||||
* [/nfts/ ](https://docs.coingecko.com/reference/nfts-id)
|
||||
* [/nfts//contract/](https://docs.coingecko.com/reference/nfts-contract-address)
|
||||
|
||||
**Example of responses:**
|
||||
|
||||
|
|
@ -2079,8 +2079,8 @@ We've added "symbol" field to these NFT endpoints responses:
|
|||
|
||||
We've added "links" field (e.g. homepage, twitter, discord) to these NFT endpoints responses:
|
||||
|
||||
* [/nfts/](/reference/nfts-id)
|
||||
* [/nfts//contract/](/reference/nfts-contract-address)
|
||||
* [/nfts/](https://docs.coingecko.com/reference/nfts-id)
|
||||
* [/nfts//contract/](https://docs.coingecko.com/reference/nfts-contract-address)
|
||||
|
||||
**Example of responses:**
|
||||
|
||||
|
|
@ -2088,7 +2088,7 @@ We've added "links" field (e.g. homepage, twitter, discord) to these NFT endpoin
|
|||
|
||||
🗓️ **March 23, 2023**
|
||||
|
||||
We've added [/coins/top\_gainers\_losers](/reference/coins-top-gainers-losers) endpoint exclusively for Paid Plan Subscribers.
|
||||
We've added [/coins/top\_gainers\_losers](https://docs.coingecko.com/reference/coins-top-gainers-losers) endpoint exclusively for Paid Plan Subscribers.
|
||||
|
||||
Users can now get the top 30 coins with largest price gain and loss by a specific time duration with this endpoint.
|
||||
|
||||
|
|
@ -2096,7 +2096,7 @@ Users can now get the top 30 coins with largest price gain and loss by a specifi
|
|||
|
||||
🗓️ **March 23, 2023**
|
||||
|
||||
[/networks//pools//ohlcv/](/reference/pool-ohlcv-contract-address) now returns more granularity `day,` `hour`, `minute` and multiple aggregates
|
||||
[/networks//pools//ohlcv/](https://docs.coingecko.com/reference/pool-ohlcv-contract-address) now returns more granularity `day,` `hour`, `minute` and multiple aggregates
|
||||
</Update>
|
||||
|
||||
<Update label="February 2023">
|
||||
|
|
@ -2106,14 +2106,14 @@ Users can now get the top 30 coins with largest price gain and loss by a specifi
|
|||
|
||||
We've made some updates to the /coins/categories and /simple/token\_price/id endpoints:
|
||||
|
||||
* Market cap and volume data for 'ecosystem' categories in the [/coins/categories](/reference/coins-categories) endpoint will now return 'null' until further notice. The CoinGecko team is actively working on improvements to provide more accurate data. If you have any feedback or suggestions, please reach out via [api@coingecko.com](mailto:api@coingecko.com).
|
||||
* Previously, the [/simple/token\_price/](/reference/simple-token-price) endpoint was unable to return data for some Solana coins. This issue has been resolved, and users can now expect accurate data for Solana coins from this endpoint.
|
||||
* Market cap and volume data for 'ecosystem' categories in the [/coins/categories](https://docs.coingecko.com/reference/coins-categories) endpoint will now return 'null' until further notice. The CoinGecko team is actively working on improvements to provide more accurate data. If you have any feedback or suggestions, please reach out via [api@coingecko.com](mailto:api@coingecko.com).
|
||||
* Previously, the [/simple/token\_price/](https://docs.coingecko.com/reference/simple-token-price) endpoint was unable to return data for some Solana coins. This issue has been resolved, and users can now expect accurate data for Solana coins from this endpoint.
|
||||
|
||||
## Introduced /exchange/id/volume\_chart/range endpoint
|
||||
|
||||
🗓️ **February 15, 2023**
|
||||
|
||||
We've introduced the [/exchange//volume\_chart/range](/reference/exchanges-id-volume-chart-range) endpoint for Paid Plan Subscribers.
|
||||
We've introduced the [/exchange//volume\_chart/range](https://docs.coingecko.com/reference/exchanges-id-volume-chart-range) endpoint for Paid Plan Subscribers.
|
||||
|
||||
This exclusive feature allows users to query full historical volume data of an exchange.
|
||||
</Update>
|
||||
|
|
@ -2123,7 +2123,7 @@ This exclusive feature allows users to query full historical volume data of an e
|
|||
|
||||
🗓️ **January 09, 2023**
|
||||
|
||||
We've introduced the [/coins/list/new](/reference/coins-list-new) endpoint for Paid Plan Subscribers.
|
||||
We've introduced the [/coins/list/new](https://docs.coingecko.com/reference/coins-list-new) endpoint for Paid Plan Subscribers.
|
||||
|
||||
This exclusive feature allows users to query the latest 200 coins on CoinGecko.
|
||||
</Update>
|
||||
|
|
@ -2134,7 +2134,7 @@ Example 1 (unknown):
|
|||
```unknown
|
||||
### Megafilter: Ascending Sort Order for Price Change %
|
||||
|
||||
The [Megafilter for Pools](/reference/pools-megafilter) endpoint now supports ascending sorting for price change percentage:
|
||||
The [Megafilter for Pools](https://docs.coingecko.com/reference/pools-megafilter) endpoint now supports ascending sorting for price change percentage:
|
||||
|
||||
* `m5_price_change_percentage_asc`
|
||||
* `h1_price_change_percentage_asc`
|
||||
|
|
@ -2143,7 +2143,7 @@ Example 1 (unknown):
|
|||
|
||||
### Token OHLCV Endpoint Fix to respect Specified Token Address
|
||||
|
||||
We've fixed an issue where the [Token OHLCV chart by Token Address](/reference/token-ohlcv-token-address) endpoint returned data for the base token of the top pool instead of the requested token. It will now always return data for the specified token address.
|
||||
We've fixed an issue where the [Token OHLCV chart by Token Address](https://docs.coingecko.com/reference/token-ohlcv-token-address) endpoint returned data for the base token of the top pool instead of the requested token. It will now always return data for the specified token address.
|
||||
</Update>
|
||||
|
||||
<Update label="September 2025">
|
||||
|
|
@ -2167,17 +2167,17 @@ Example 1 (unknown):
|
|||
We're also surfacing new tools through the MCP to give developers a richer, faster way to query exchanges, NFTs, and onchain activity.
|
||||
|
||||
* New tools:
|
||||
* Exchange coverage with [/exchanges/list](reference/exchanges-list), [/exchanges/](reference/exchanges-id), [/exchanges//tickers](reference/exchanges-id-tickers), and [/exchanges//volume\_chart/range](reference/exchanges-id-volume-chart-range)
|
||||
* NFT markets with [/nfts/markets](reference/nfts-markets)
|
||||
* Multi-address queries with [/onchain/networks//pools/multi/](reference/pools-addresses) and [/onchain/networks//tokens/multi/](reference/tokens-data-contract-addresses)
|
||||
* Exchange coverage with [/exchanges/list](https://docs.coingecko.com/reference/exchanges-list), [/exchanges/](https://docs.coingecko.com/reference/exchanges-id), [/exchanges//tickers](https://docs.coingecko.com/reference/exchanges-id-tickers), and [/exchanges//volume\_chart/range](https://docs.coingecko.com/reference/exchanges-id-volume-chart-range)
|
||||
* NFT markets with [/nfts/markets](https://docs.coingecko.com/reference/nfts-markets)
|
||||
* Multi-address queries with [/onchain/networks//pools/multi/](https://docs.coingecko.com/reference/pools-addresses) and [/onchain/networks//tokens/multi/](https://docs.coingecko.com/reference/tokens-data-contract-addresses)
|
||||
* Retired tools:
|
||||
* We've removed endpoints such as [/coins/list](reference/coins-list), [/onchain/networks/trending\_pools](reference/trending-pools-network), and single-address pool/token queries in favor of more scalable multi-address endpoints
|
||||
* We've removed endpoints such as [/coins/list](https://docs.coingecko.com/reference/coins-list), [/onchain/networks/trending\_pools](https://docs.coingecko.com/reference/trending-pools-network), and single-address pool/token queries in favor of more scalable multi-address endpoints
|
||||
|
||||
### Friendlier Time-related MCP Queries with ISO Support
|
||||
|
||||
Time-based queries just got easier. MCP tools now accept **ISO date strings** (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`) alongside UNIX timestamps.
|
||||
|
||||
For example, when using the [Coin Historical Chart Data within Time Range](reference/coins-id-market-chart-range) tool, you can now pass ISO date strings directly instead of converting them into UNIX timestamps for your LLM tools.
|
||||
For example, when using the [Coin Historical Chart Data within Time Range](https://docs.coingecko.com/reference/coins-id-market-chart-range) tool, you can now pass ISO date strings directly instead of converting them into UNIX timestamps for your LLM tools.
|
||||
|
||||
**CoinGecko API Team**
|
||||
|
||||
|
|
@ -2261,11 +2261,11 @@ Quick tips to empower your AI applications with CoinGecko API, and leverage our
|
|||
|
||||
CoinGecko provides a powerful suite of AI-native tools to help you integrate real-time, historical, and onchain market data into your applications. Whether you're building a sophisticated trading bot, a market analysis tool, or a simple portfolio tracker, our AI toolkit is here to accelerate your development.
|
||||
|
||||
To help AI models interact with CoinGecko data effectively, we provide an `llms.txt` file at [/llms-full.txt](/llms-full.txt). This file gives models context on how to best query our API, ensuring more accurate and efficient data retrieval. We recommend utilizing this in your integrations of MCP and AI applications.
|
||||
To help AI models interact with CoinGecko data effectively, we provide an `llms.txt` file at [/llms-full.txt](https://docs.coingecko.com/llms-full.txt). This file gives models context on how to best query our API, ensuring more accurate and efficient data retrieval. We recommend utilizing this in your integrations of MCP and AI applications.
|
||||
|
||||
## CoinGecko MCP Server
|
||||
|
||||
The **MCP (Model-Context-Protocol)** Server is your gateway for connecting AI agents and large language models, like Claude and Gemini, directly to CoinGecko's live data streams. It's ideal for building conversational applications that can perform complex, real-time crypto analysis and answer user queries with up-to-the-minute information. Learn how to connect your AI agent by checking out [CoinGecko MCP Server](/docs/mcp-server)
|
||||
The **MCP (Model-Context-Protocol)** Server is your gateway for connecting AI agents and large language models, like Claude and Gemini, directly to CoinGecko's live data streams. It's ideal for building conversational applications that can perform complex, real-time crypto analysis and answer user queries with up-to-the-minute information. Learn how to connect your AI agent by checking out [CoinGecko MCP Server](https://docs.coingecko.com/docs/mcp-server)
|
||||
|
||||
## Tools for Your Workflow
|
||||
|
||||
|
|
@ -2519,16 +2519,16 @@ There are five different endpoints to get historical data of a coin:
|
|||
|
||||
| Endpoint | Description |
|
||||
| ---------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [/coins/\{id}/history](/reference/coins-id-history) | Get the historical data (price, market cap, 24hrs volume, etc.) at a given date for a coin based on a particular coin ID. |
|
||||
| [/coins/\{id}/market\_chart](/reference/coins-id-market-chart) | Get the historical chart data of a coin including time in UNIX, price, market cap and 24hrs volume based on particular coin ID. |
|
||||
| [/coins/\{id}/market\_chart/range](/reference/coins-id-market-chart-range) | Get the historical chart data of a coin within certain time range in UNIX along with price, market cap and 24hrs volume based on particular coin ID. |
|
||||
| [/coins/\{id}/contract/\{contract\_address}/market\_chart](/reference/contract-address-market-chart) | Get the historical chart data of a coin including time in UNIX, price, market cap and 24hrs volume based on token contract address. |
|
||||
| [/coins/\{id}/contract/\{contract\_address}/market\_chart/range](/reference/contract-address-market-chart-range) | Get the historical chart data of a coin within certain time range in UNIX along with price, market cap and 24hrs volume based on token contract address. |
|
||||
| [/coins/\{id}/history](https://docs.coingecko.com/reference/coins-id-history) | Get the historical data (price, market cap, 24hrs volume, etc.) at a given date for a coin based on a particular coin ID. |
|
||||
| [/coins/\{id}/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart) | Get the historical chart data of a coin including time in UNIX, price, market cap and 24hrs volume based on particular coin ID. |
|
||||
| [/coins/\{id}/market\_chart/range](https://docs.coingecko.com/reference/coins-id-market-chart-range) | Get the historical chart data of a coin within certain time range in UNIX along with price, market cap and 24hrs volume based on particular coin ID. |
|
||||
| [/coins/\{id}/contract/\{contract\_address}/market\_chart](https://docs.coingecko.com/reference/contract-address-market-chart) | Get the historical chart data of a coin including time in UNIX, price, market cap and 24hrs volume based on token contract address. |
|
||||
| [/coins/\{id}/contract/\{contract\_address}/market\_chart/range](https://docs.coingecko.com/reference/contract-address-market-chart-range) | Get the historical chart data of a coin within certain time range in UNIX along with price, market cap and 24hrs volume based on token contract address. |
|
||||
|
||||
<Note>
|
||||
### **Notes**
|
||||
|
||||
The data granularity (interval) for [/market\_chart](/reference/coins-id-market-chart) and [/market\_chart/range](/reference/coins-id-market-chart-range) endpoints is automatic and based on the date range:
|
||||
The data granularity (interval) for [/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart) and [/market\_chart/range](https://docs.coingecko.com/reference/coins-id-market-chart-range) endpoints is automatic and based on the date range:
|
||||
|
||||
* 1 day from current time = 5-minutely data
|
||||
* 1 day from anytime (except from current time) = hourly data
|
||||
|
|
@ -2563,8 +2563,8 @@ Integrating these prompts into your workflow is simple. Copy the entire markdown
|
|||
|
||||
Select the prompt that matches your project's tech stack.
|
||||
|
||||
* 🐍 **[Python](/docs/python-ai-prompts)**: A complete guide for implementing the CoinGecko API using our official [coingecko-sdk](https://pypi.org/project/coingecko-sdk/).
|
||||
* 🟦 **[TypeScript](/docs/typescript-ai-prompts#/)**: The definitive prompt for integrating the CoinGecko API with our official [@coingecko/coingecko-typescript](https://www.npmjs.com/package/@coingecko/coingecko-typescript) package.
|
||||
* 🐍 **[Python](https://docs.coingecko.com/docs/python-ai-prompts)**: A complete guide for implementing the CoinGecko API using our official [coingecko-sdk](https://pypi.org/project/coingecko-sdk/).
|
||||
* 🟦 **[TypeScript](https://docs.coingecko.com/docs/typescript-ai-prompts#/)**: The definitive prompt for integrating the CoinGecko API with our official [@coingecko/coingecko-typescript](https://www.npmjs.com/package/@coingecko/coingecko-typescript) package.
|
||||
|
||||
To get the most out of our AI prompts, keep these tips in mind:
|
||||
|
||||
|
|
@ -2583,14 +2583,14 @@ Source: https://docs.coingecko.com/docs/10-mins-tutorial-guide
|
|||
|
||||
New to CoinGecko API? Fret not. Whether you're a programmer or someone with zero coding experience, we've got you covered!
|
||||
|
||||
If you are not a developer and prefer to learn only specific tutorials on Google Sheet/Excel, feel free to check [👶 Tutorials (Beginner-friendly)](/docs/tutorials-beginner-friendly)
|
||||
If you are not a developer and prefer to learn only specific tutorials on Google Sheet/Excel, feel free to check [👶 Tutorials (Beginner-friendly)](https://docs.coingecko.com/docs/tutorials-beginner-friendly)
|
||||
|
||||
| Tutorial Steps | Description |
|
||||
| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
|
||||
| [1. Get data by ID or Address](/docs/1-get-data-by-id-or-address) | Learn how to use different endpoints by obtaining Coin ID and token's contract address at first. |
|
||||
| [2. Get Historical Data](/docs/2-get-historical-data) | Learn how to get historical data of a coin by using different historical endpoints. |
|
||||
| [3. Get Exchanges & NFT Data](/docs/3-get-exchanges-nft-data) | Learn how to query exchanges and NFT data by accessing different endpoints. |
|
||||
| [4. Get On-chain Data](/docs/4-get-on-chain-data) | Learn how to use `/onchain` GT endpoints to query onchain data. |
|
||||
| [1. Get data by ID or Address](https://docs.coingecko.com/docs/1-get-data-by-id-or-address) | Learn how to use different endpoints by obtaining Coin ID and token's contract address at first. |
|
||||
| [2. Get Historical Data](https://docs.coingecko.com/docs/2-get-historical-data) | Learn how to get historical data of a coin by using different historical endpoints. |
|
||||
| [3. Get Exchanges & NFT Data](https://docs.coingecko.com/docs/3-get-exchanges-nft-data) | Learn how to query exchanges and NFT data by accessing different endpoints. |
|
||||
| [4. Get On-chain Data](https://docs.coingecko.com/docs/4-get-on-chain-data) | Learn how to use `/onchain` GT endpoints to query onchain data. |
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -2618,73 +2618,73 @@ Discover how CoinGecko API is used at CoinGecko.com and GeckoTerminal.com
|
|||
|
||||
<img src="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/5efbe42-image.png?fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=d63633d56cc7a4d3c7d71a931a7112d8" alt="" data-og-width="2200" width="2200" data-og-height="1528" height="1528" data-path="images/docs/5efbe42-image.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/5efbe42-image.png?w=280&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=094bb211db972bea7d8b66716f5eed3a 280w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/5efbe42-image.png?w=560&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=da211f3d8c1aec265d53891dc8f43ed6 560w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/5efbe42-image.png?w=840&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=fc59610f652ef640696568679b90b723 840w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/5efbe42-image.png?w=1100&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=4d8905af936b5a34968b6dad1c59f7c5 1100w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/5efbe42-image.png?w=1650&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=1679ab4c405a2ad10f8037bf0e830a0d 1650w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/5efbe42-image.png?w=2500&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=299d7edb9949e51d03a2c357eb0ce127 2500w" />
|
||||
|
||||
1. [/global](/reference/crypto-global) — Display global crypto data such as number of active cryptocurrencies, exchanges and etc.
|
||||
2. [/search/trending](/reference/trending-search) — Display trending search coins, NFTs and categories.
|
||||
3. [/coins/top\_gainers\_losers](/reference/coins-top-gainers-losers) — Display the largest gainers in 24hr.
|
||||
4. [/coins/categories](/reference/coins-categories) — Display all the categories list.
|
||||
5. [/coins/markets](/reference/coins-markets) — Display all the supported coins with market related data.
|
||||
1. [/global](https://docs.coingecko.com/reference/crypto-global) — Display global crypto data such as number of active cryptocurrencies, exchanges and etc.
|
||||
2. [/search/trending](https://docs.coingecko.com/reference/trending-search) — Display trending search coins, NFTs and categories.
|
||||
3. [/coins/top\_gainers\_losers](https://docs.coingecko.com/reference/coins-top-gainers-losers) — Display the largest gainers in 24hr.
|
||||
4. [/coins/categories](https://docs.coingecko.com/reference/coins-categories) — Display all the categories list.
|
||||
5. [/coins/markets](https://docs.coingecko.com/reference/coins-markets) — Display all the supported coins with market related data.
|
||||
|
||||
### [Coin Page](https://www.coingecko.com/en/coins/bitcoin)
|
||||
|
||||
<img src="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/2f71923-image.png?fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=4f3f1e9c241ac3c7fb3c6fdfec6f516d" alt="" data-og-width="2104" width="2104" data-og-height="1492" height="1492" data-path="images/docs/2f71923-image.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/2f71923-image.png?w=280&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=9a71372f238cd241108306680d5a2a46 280w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/2f71923-image.png?w=560&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=cad968f1b3cf92f47091e006897bd9c8 560w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/2f71923-image.png?w=840&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=0977ba4c9e4fd44e025685bd4527bfbe 840w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/2f71923-image.png?w=1100&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=a7bdbd1e213ad62e8763ad00177567e7 1100w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/2f71923-image.png?w=1650&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=602e29d2123e3681f7f7eca248348f6c 1650w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/2f71923-image.png?w=2500&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=1931234bdbbc82514affdaf503710e38 2500w" />
|
||||
|
||||
1. [/coins/\{id} ](/reference/coins-id)— Display all the coin data including name, price, market related data, website, explorers and etc.
|
||||
2. [/simple/price](/reference/simple-price) — Display data such as latest coin price, market cap and 24hr trading volume.
|
||||
3. * [/coins/\{id}/history](/reference/coins-id-history) — Display the historical price data.
|
||||
* [/coins/\{id}/market\_chart](/reference/coins-id-market-chart) — Display the historical data in line chart.
|
||||
* [/coins/\{id}/ohlc](/reference/coins-id-ohlc) — Display the historical data in candlestick chart.
|
||||
1. [/coins/\{id} ](https://docs.coingecko.com/reference/coins-id)— Display all the coin data including name, price, market related data, website, explorers and etc.
|
||||
2. [/simple/price](https://docs.coingecko.com/reference/simple-price) — Display data such as latest coin price, market cap and 24hr trading volume.
|
||||
3. * [/coins/\{id}/history](https://docs.coingecko.com/reference/coins-id-history) — Display the historical price data.
|
||||
* [/coins/\{id}/market\_chart](https://docs.coingecko.com/reference/coins-id-market-chart) — Display the historical data in line chart.
|
||||
* [/coins/\{id}/ohlc](https://docs.coingecko.com/reference/coins-id-ohlc) — Display the historical data in candlestick chart.
|
||||
|
||||
### [Exchanges Page](https://www.coingecko.com/en/exchanges/hyperliquid-spot)
|
||||
|
||||
<img src="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/9e12298-image.png?fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=8306154da0e21d2b902eadda23cb7dfc" alt="" data-og-width="2128" width="2128" data-og-height="1394" height="1394" data-path="images/docs/9e12298-image.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/9e12298-image.png?w=280&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=cad9ee450cbc127562e5bc65d922339a 280w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/9e12298-image.png?w=560&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=03edf7a33acb4c998656ce6b1007e6ad 560w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/9e12298-image.png?w=840&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=ba853e66f1bed4efcf8a6a1bf0ad5c6f 840w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/9e12298-image.png?w=1100&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=ab46e891e1c84ca00961a549e27e9434 1100w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/9e12298-image.png?w=1650&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=b741c73166b49da858f7a9de5e9dda45 1650w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/9e12298-image.png?w=2500&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=063b3126d0c4236464345bb4cf9c38d0 2500w" />
|
||||
|
||||
1. [/exchanges/\{id}](/reference/exchanges-id) — Display the exchange information such as name, type, market related data such as trading volume and etc.
|
||||
2. [/exchanges/\{id}/volume\_chart](/reference/exchanges-id-volume-chart) — Display the historical volume chart data.
|
||||
3. [/exchanges/\{id}/tickers](/reference/exchanges-id-tickers) — Display the exchange's tickers.
|
||||
1. [/exchanges/\{id}](https://docs.coingecko.com/reference/exchanges-id) — Display the exchange information such as name, type, market related data such as trading volume and etc.
|
||||
2. [/exchanges/\{id}/volume\_chart](https://docs.coingecko.com/reference/exchanges-id-volume-chart) — Display the historical volume chart data.
|
||||
3. [/exchanges/\{id}/tickers](https://docs.coingecko.com/reference/exchanges-id-tickers) — Display the exchange's tickers.
|
||||
|
||||
### [NFTs Page](https://www.coingecko.com/en/nft/pudgy-penguins)
|
||||
|
||||
<img src="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/cda9241-image.png?fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=666f359cbc3e65fef656e351617f2b9f" alt="" data-og-width="1845" width="1845" data-og-height="1867" height="1867" data-path="images/docs/cda9241-image.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/cda9241-image.png?w=280&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=885542d09a7346a1a7000df7cd2a4452 280w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/cda9241-image.png?w=560&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=16419d75014aab231cda6c6d7596a1da 560w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/cda9241-image.png?w=840&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=1df3f1689b943b7a3f53d7e6099b0897 840w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/cda9241-image.png?w=1100&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=5aa83a631e8e6960cbe416b7d4375fbd 1100w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/cda9241-image.png?w=1650&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=e037c284ec52bb4f9c9c666c8501d99d 1650w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/cda9241-image.png?w=2500&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=c27add5b7c705a2034414567ab1693de 2500w" />
|
||||
|
||||
1. [/nfts/\{id}](/reference/nfts-id) — Display NFT data such as name, contract address, website, market related data such as floor price, market cap, volume and etc.
|
||||
2. [/nfts/\{id}/market\_chart](/reference/nfts-id-market-chart) — Display the historical market data in chart.
|
||||
3. [/nfts/\{id}](/reference/nfts-id) — Display the description of the NFT collection.
|
||||
4. [/nfts/\{id}/tickers](/reference/nfts-id-tickers) — Display the tickers of the NFT collection on different NFT marketplace.
|
||||
1. [/nfts/\{id}](https://docs.coingecko.com/reference/nfts-id) — Display NFT data such as name, contract address, website, market related data such as floor price, market cap, volume and etc.
|
||||
2. [/nfts/\{id}/market\_chart](https://docs.coingecko.com/reference/nfts-id-market-chart) — Display the historical market data in chart.
|
||||
3. [/nfts/\{id}](https://docs.coingecko.com/reference/nfts-id) — Display the description of the NFT collection.
|
||||
4. [/nfts/\{id}/tickers](https://docs.coingecko.com/reference/nfts-id-tickers) — Display the tickers of the NFT collection on different NFT marketplace.
|
||||
|
||||
### [Home Page](https://www.geckoterminal.com/)
|
||||
|
||||
<img src="https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/8d5ac53-image.png?fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=006779468e238af7cb515c3b90d478b7" alt="" data-og-width="3023" width="3023" data-og-height="1881" height="1881" data-path="images/docs/8d5ac53-image.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/8d5ac53-image.png?w=280&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=1e64c2a847217aeb6a1524ba665d0bb7 280w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/8d5ac53-image.png?w=560&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=98994fc84ed994e69ef12ea133093092 560w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/8d5ac53-image.png?w=840&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=e1f9614a1227137104e693480cb739cb 840w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/8d5ac53-image.png?w=1100&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=de8a324c611cc5b2557a1d130224346a 1100w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/8d5ac53-image.png?w=1650&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=d94dee12678b5c879f5e6ebafe107d4a 1650w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/8d5ac53-image.png?w=2500&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=96c61ccae7576b9f486e28459ca4e963 2500w" />
|
||||
|
||||
1. [/onchain/search/pools ](/reference/search-pools)— Allow users to search for pools on GeckoTerminal.
|
||||
2. [/onchain/networks](/reference/networks-list) — Display a list of supported networks on GeckoTerminal.
|
||||
3. [/onchain/networks/trending\_pools](/reference/trending-pools-list) — Display a list of trending pools across all networks on GeckoTerminal.
|
||||
4. [/onchain/networks/new\_pools](/reference/latest-pools-list) — Display all the latest pools across all networks on GeckoTerminal.
|
||||
5. [/onchain/categories](/reference/categories-list) — Display all the onchain categories on GeckoTerminal.
|
||||
1. [/onchain/search/pools ](https://docs.coingecko.com/reference/search-pools)— Allow users to search for pools on GeckoTerminal.
|
||||
2. [/onchain/networks](https://docs.coingecko.com/reference/networks-list) — Display a list of supported networks on GeckoTerminal.
|
||||
3. [/onchain/networks/trending\_pools](https://docs.coingecko.com/reference/trending-pools-list) — Display a list of trending pools across all networks on GeckoTerminal.
|
||||
4. [/onchain/networks/new\_pools](https://docs.coingecko.com/reference/latest-pools-list) — Display all the latest pools across all networks on GeckoTerminal.
|
||||
5. [/onchain/categories](https://docs.coingecko.com/reference/categories-list) — Display all the onchain categories on GeckoTerminal.
|
||||
|
||||
### [Chain Page](https://www.geckoterminal.com/eth/pools)
|
||||
|
||||
<img src="https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/7b49f3e-image.png?fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=26f7cdd8a92a237ac6358be830d42c55" alt="" data-og-width="3023" width="3023" data-og-height="1883" height="1883" data-path="images/docs/7b49f3e-image.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/7b49f3e-image.png?w=280&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=46918d142183d419c4d2ddb6852c2b9e 280w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/7b49f3e-image.png?w=560&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=2b60fc1e44832b2df0b0fa39e01cc6dc 560w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/7b49f3e-image.png?w=840&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=9ce014411117fb3907620cca658c4b81 840w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/7b49f3e-image.png?w=1100&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=4e1b0fb9ea89441c506fe7cd66007e91 1100w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/7b49f3e-image.png?w=1650&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=bc062efdc17e4506c6d1fa9c203e524f 1650w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/7b49f3e-image.png?w=2500&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=ee169d02c1f17780b97daf3ee9e34189 2500w" />
|
||||
|
||||
1. [/onchain/networks/\{network}/dexes](/reference/dexes-list) — Display all the supported dex on a network on GeckoTerminal.
|
||||
2. [/onchain/networks/\{network}/trending\_pools](/reference/trending-pools-network) — Display a list of trending pools on a network on GeckoTerminal.
|
||||
3. [/onchain/networks/\{network}/new\_pools](/reference/latest-pools-network) — Display a list of new pools on a network on GeckoTerminal.
|
||||
4. [/onchain/networks/\{network}/pools](/reference/top-pools-network) — Display all the top pools on a network on GeckoTerminal.
|
||||
5. [/onchain/categories/\{category\_id}/pools](/reference/pools-category) — Display all the pools under a specific onchain category on GeckoTerminal.
|
||||
1. [/onchain/networks/\{network}/dexes](https://docs.coingecko.com/reference/dexes-list) — Display all the supported dex on a network on GeckoTerminal.
|
||||
2. [/onchain/networks/\{network}/trending\_pools](https://docs.coingecko.com/reference/trending-pools-network) — Display a list of trending pools on a network on GeckoTerminal.
|
||||
3. [/onchain/networks/\{network}/new\_pools](https://docs.coingecko.com/reference/latest-pools-network) — Display a list of new pools on a network on GeckoTerminal.
|
||||
4. [/onchain/networks/\{network}/pools](https://docs.coingecko.com/reference/top-pools-network) — Display all the top pools on a network on GeckoTerminal.
|
||||
5. [/onchain/categories/\{category\_id}/pools](https://docs.coingecko.com/reference/pools-category) — Display all the pools under a specific onchain category on GeckoTerminal.
|
||||
|
||||
### [Pool Page](https://www.geckoterminal.com/eth/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640)
|
||||
|
||||
<img src="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/43e04c2-image.png?fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=dedf21f04c9bbf11fbf376f83b101969" alt="" data-og-width="3023" width="3023" data-og-height="1887" height="1887" data-path="images/docs/43e04c2-image.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/43e04c2-image.png?w=280&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=6e355b30d2a491ccf540d269d631721c 280w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/43e04c2-image.png?w=560&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=2088b61a6ae8a189a4249db17fd75928 560w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/43e04c2-image.png?w=840&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=ced214f96c8c869eca7627410782dc7a 840w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/43e04c2-image.png?w=1100&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=722d09f605c5a0eabeda3e194f6bd51c 1100w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/43e04c2-image.png?w=1650&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=4d921a31f241b78515f25be7a698a6ff 1650w, https://mintcdn.com/coingecko/M02rMX2XJMwBGpCe/images/docs/43e04c2-image.png?w=2500&fit=max&auto=format&n=M02rMX2XJMwBGpCe&q=85&s=1f522f2b1fbc4e1cf96c5e4bf7cb3f44 2500w" />
|
||||
|
||||
1. * [/onchain/networks/\{network}/pools/\{address}](/reference/pool-address) — Display pool data such as price, transactions, volume and etc.
|
||||
* [/onchain/networks/\{network}/pools/\{pool\_address}/info](/reference/pool-token-info-contract-address) — Display pool information such as name, symbol, image URL, description and etc.
|
||||
2. [/onchain/networks/\{network}/pools/\{pool\_address}/ohlcv/\{timeframe}](/reference/pool-ohlcv-contract-address) — Display the OHLCV chart of the pool.
|
||||
3. [/onchain/networks/\{network}/pools/\{pool\_address}/trades](/reference/pool-trades-contract-address) — Display the trades of the pool in the past 24 hours.
|
||||
1. * [/onchain/networks/\{network}/pools/\{address}](https://docs.coingecko.com/reference/pool-address) — Display pool data such as price, transactions, volume and etc.
|
||||
* [/onchain/networks/\{network}/pools/\{pool\_address}/info](https://docs.coingecko.com/reference/pool-token-info-contract-address) — Display pool information such as name, symbol, image URL, description and etc.
|
||||
2. [/onchain/networks/\{network}/pools/\{pool\_address}/ohlcv/\{timeframe}](https://docs.coingecko.com/reference/pool-ohlcv-contract-address) — Display the OHLCV chart of the pool.
|
||||
3. [/onchain/networks/\{network}/pools/\{pool\_address}/trades](https://docs.coingecko.com/reference/pool-trades-contract-address) — Display the trades of the pool in the past 24 hours.
|
||||
|
||||
### [Categories Page](https://www.geckoterminal.com/category)
|
||||
|
||||
<img src="https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/cd8f5e-image.png?fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=912a6001736c59cf4fcdbf7bdce05814" alt="" data-og-width="3023" width="3023" data-og-height="1887" height="1887" data-path="images/docs/cd8f5e-image.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/cd8f5e-image.png?w=280&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=c97b53b79138f3e1e2f909e8e563c7fe 280w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/cd8f5e-image.png?w=560&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=84aedbbff60dc6f80fa478d0f389c31c 560w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/cd8f5e-image.png?w=840&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=80ff73fe40ba9b98c15894752d42a981 840w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/cd8f5e-image.png?w=1100&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=331705cce03b7b5aea56d00bc22a294d 1100w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/cd8f5e-image.png?w=1650&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=28fe2d9a7552ce2477be4c616b7f4fad 1650w, https://mintcdn.com/coingecko/Jrf60GKLjFfVX1SS/images/docs/cd8f5e-image.png?w=2500&fit=max&auto=format&n=Jrf60GKLjFfVX1SS&q=85&s=b7750c4ae2c4de27b6b6bedb41c8af96 2500w" />
|
||||
|
||||
1. [/onchain/categories](/reference/categories-list) — Display list of onchain categories with market data.
|
||||
2. [/onchain/categories/\{id}/pools](/reference/pools-category) — Display list of pools with market data of a specific onchain category.
|
||||
1. [/onchain/categories](https://docs.coingecko.com/reference/categories-list) — Display list of onchain categories with market data.
|
||||
2. [/onchain/categories/\{id}/pools](https://docs.coingecko.com/reference/pools-category) — Display list of pools with market data of a specific onchain category.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
# Cryptocurrency Exchange Feed Handler
|
||||
[](LICENSE)
|
||||
[](https://github.com/bmoscon/cryptofeed/blob/master/LICENSE)
|
||||

|
||||
[](https://pypi.python.org/pypi/cryptofeed)
|
||||
[](https://www.codacy.com/app/bmoscon/cryptofeed?utm_source=github.com&utm_medium=referral&utm_content=bmoscon/cryptofeed&utm_campaign=Badge_Grade)
|
||||
|
|
@ -82,7 +82,7 @@ For an example of a containerized application using cryptofeed to store data to
|
|||
|
||||
## National Best Bid/Offer (NBBO)
|
||||
|
||||
Cryptofeed also provides a synthetic [NBBO](examples/demo_nbbo.py) (National Best Bid/Offer) feed that aggregates the best bids and asks from the user specified feeds.
|
||||
Cryptofeed also provides a synthetic [NBBO](https://github.com/bmoscon/cryptofeed/blob/master/examples/demo_nbbo.py) (National Best Bid/Offer) feed that aggregates the best bids and asks from the user specified feeds.
|
||||
|
||||
```python
|
||||
from cryptofeed import FeedHandler
|
||||
|
|
@ -171,7 +171,7 @@ See more discussion of package installation in [INSTALL.md](https://github.com/b
|
|||
|
||||
## Rest API
|
||||
|
||||
Cryptofeed supports some REST interfaces for retrieving real-time and historical data, as well as order placement and account management. These are integrated into the exchange classes directly. You can view the supported methods by calling the `info()` method on any exchange. The methods for interacting with the exchange RET endpoints exist in two flavors, the synchronous methods (suffixed with `_sync`) as well as the asynchronous which can be utilized with asyncio. For more information see the [documentation](docs/rest.md).
|
||||
Cryptofeed supports some REST interfaces for retrieving real-time and historical data, as well as order placement and account management. These are integrated into the exchange classes directly. You can view the supported methods by calling the `info()` method on any exchange. The methods for interacting with the exchange RET endpoints exist in two flavors, the synchronous methods (suffixed with `_sync`) as well as the asynchronous which can be utilized with asyncio. For more information see the [documentation](https://github.com/bmoscon/cryptofeed/blob/master/docs/rest.md).
|
||||
|
||||
|
||||
## Future Work
|
||||
|
|
@ -182,7 +182,7 @@ There are a lot of planned features, new exchanges, etc planned! If you'd like t
|
|||
|
||||
Issues and PRs are welcomed!
|
||||
|
||||
Cryptofeed wouldn't be possible without the help of many [contributors](AUTHORS.md)! I owe them and all other contributors my thanks!
|
||||
Cryptofeed wouldn't be possible without the help of many [contributors](https://github.com/bmoscon/cryptofeed/blob/master/AUTHORS.md)! I owe them and all other contributors my thanks!
|
||||
|
||||
## Donations / Support
|
||||
|
||||
|
|
|
|||
|
|
@ -190,9 +190,9 @@ curl "https://gamma-api.polymarket.com/markets?tag_id=100381&closed=false&limit=
|
|||
4. **Always Include `closed=false`:** Unless you specifically need historical data
|
||||
5. **Implement Rate Limiting:** Respect API limits for production applications
|
||||
|
||||
* [Get Markets](/developers/gamma-markets-api/get-markets) - Full markets endpoint documentation
|
||||
* [Get Events](/developers/gamma-markets-api/get-events) - Full events endpoint documentation
|
||||
* [Search Markets](/developers/gamma-markets-api/get-public-search) - Search functionality
|
||||
* [Get Markets](https://docs.polymarket.com/developers/gamma-markets-api/get-markets) - Full markets endpoint documentation
|
||||
* [Get Events](https://docs.polymarket.com/developers/gamma-markets-api/get-events) - Full events endpoint documentation
|
||||
* [Search Markets](https://docs.polymarket.com/developers/gamma-markets-api/get-public-search) - Search functionality
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -193,7 +193,7 @@ Source: https://docs.polymarket.com/quickstart/introduction/definitions
|
|||
| **Token** | A token represents a stake in a specific Yes/No outcome in a Market. The price of a token can fluctuate between $0 - $1 based on the market belief in the outcome. When a market resolves, the token associated with the correct prediction can be redeemed for \$1 USDC. This is also sometimes called an *Asset Id* |
|
||||
| **Market** | A single event outcome. Corresponds to a pair of CLOB token IDs(Yes/No), a market address, a question ID and a condition ID. |
|
||||
| **Event** | A collection of related markets grouped under a common topic or theme. |
|
||||
| **SLUG** | A human readable identification for a market or event. Can be found in the URL of any Polymarket Market or Event. You can use this slug to find more detailed information about a market or event by using it as a parameter in the [Get Events](/developers/gamma-markets-api/get-events) or [Get Markets](/developers/gamma-markets-api/get-markets) endpoints. |
|
||||
| **SLUG** | A human readable identification for a market or event. Can be found in the URL of any Polymarket Market or Event. You can use this slug to find more detailed information about a market or event by using it as a parameter in the [Get Events](https://docs.polymarket.com/developers/gamma-markets-api/get-events) or [Get Markets](https://docs.polymarket.com/developers/gamma-markets-api/get-markets) endpoints. |
|
||||
| **Negative Risk (negrisk)** | A group of Markets(Event) in which only one Market can resolve as yes. For more detail see [Negrisk Details](https://docs.polymarket.com/developers/neg-risk/overview) |
|
||||
| **Central Limit Order Book** | The off-chain order matching system. This is where you place resting orders and market orders are matched with existing orders before being sent on-chain. |
|
||||
| **Polygon Network** | A scalable, multi-chain blockchain platform used by Polymarket to facilitate on-chain activities(contract creation, token transfers, etc) |
|
||||
|
|
@ -247,7 +247,7 @@ Source: https://docs.polymarket.com/polymarket-learn/FAQ/does-polymarket-have-an
|
|||
|
||||
Getting data from Polymarket
|
||||
|
||||
Yes! Developers can find all the information they need for interacting with Polymarket. This includes [documentation on market discovery, resolution, trading etc.](/quickstart/introduction/main)
|
||||
Yes! Developers can find all the information they need for interacting with Polymarket. This includes [documentation on market discovery, resolution, trading etc.](https://docs.polymarket.com/quickstart/introduction/main)
|
||||
|
||||
Whether you are an academic researcher a market maker or an indepedent developer, this documentation should provide you what you need to get started. All the code you find linked here and on our [GitHub](https://github.com/polymarket) is open source and free to use.
|
||||
|
||||
|
|
@ -267,7 +267,7 @@ This section of the documentation will provide all the essential resources to he
|
|||
|
||||
Everything you need to start building with the Polymarket API is right here. Let’s get started.
|
||||
|
||||
[Not sure what to build next? Get inspired by checking out real examples from other developers using the API.](/quickstart/introduction/showcase)
|
||||
[Not sure what to build next? Get inspired by checking out real examples from other developers using the API.](https://docs.polymarket.com/quickstart/introduction/showcase)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -327,13 +327,13 @@ Polymarket is the world’s largest prediction market, allowing you to stay info
|
|||
|
||||
Studies show prediction markets are often more accurate than pundits because they combine news, polls, and expert opinions into a single value that represents the market's view of an event's odds. Our markets reflect *accurate, unbiased, and real-time probabilities* for the events that matter most to you. Markets seek truth.
|
||||
|
||||
* On Polymarket, you can [buy and sell shares](making-your-first-trade) representing future event outcomes (i.e. "Will TikTok be banned in the U.S. this year?")
|
||||
* On Polymarket, you can [buy and sell shares](https://docs.polymarket.com/polymarket-learn/get-started/making-your-first-trade) representing future event outcomes (i.e. "Will TikTok be banned in the U.S. this year?")
|
||||
|
||||
* Shares in event outcomes are [always priced](what-is-polymarket/#understanding-prices) between 0.00 and 1.00 [USDC](../FAQ/why-do-i-need-crypto/#why-usdc), and every pair of event outcomes (i.e. each pair of "YES" + "NO" shares) is fully collateralized by \$1.00 USDC.
|
||||
* Shares in event outcomes are [always priced](https://docs.polymarket.com/polymarket-learn/get-started/what-is-polymarket/#understanding-prices) between 0.00 and 1.00 [USDC](https://docs.polymarket.com/polymarket-learn/FAQ/why-do-i-need-crypto/#why-usdc), and every pair of event outcomes (i.e. each pair of "YES" + "NO" shares) is fully collateralized by \$1.00 USDC.
|
||||
|
||||
* Shares are created when [opposing sides come to an agreement on odds](../trading/limit-orders), such that the sum of what each side is willing to pay is equal to \$1.00.
|
||||
* Shares are created when [opposing sides come to an agreement on odds](https://docs.polymarket.com/polymarket-learn/trading/limit-orders), such that the sum of what each side is willing to pay is equal to \$1.00.
|
||||
|
||||
* The shares representing the *correct, final outcome* are paid out \$1.00 USDC each upon [market resolution](../markets/how-are-markets-resolved).
|
||||
* The shares representing the *correct, final outcome* are paid out \$1.00 USDC each upon [market resolution](https://docs.polymarket.com/polymarket-learn/markets/how-are-markets-resolved).
|
||||
|
||||
* Unlike sportsbooks, you are not betting against "the house" – the counterparty to each trade is another Polymarket user. As such:
|
||||
|
||||
|
|
@ -351,7 +351,7 @@ Prices = Probabilities.
|
|||
|
||||
These odds are determined by what price other Polymarket users are currently willing to buy & sell those shares at. Just how stock exchanges don't "set" the prices of stocks, Polymarket does not set prices / odds - they're a function of supply & demand.
|
||||
|
||||
[Learn more >](/docs/guides/trading/how-are-prices-calculated)
|
||||
[Learn more >](https://docs.polymarket.com/docs/guides/trading/how-are-prices-calculated)
|
||||
|
||||
### Making money on markets
|
||||
|
||||
|
|
|
|||
|
|
@ -52,9 +52,9 @@ Individual markets and events are best fetched using their unique slug identifie
|
|||
|
||||
From any Polymarket URL, the slug is the path segment after `/event/` or `/market/`:
|
||||
|
||||
**For Events:** [GET /events/slug/{slug}](/api-reference/events/list-events)
|
||||
**For Events:** [GET /events/slug/{slug}](https://docs.polymarket.com/api-reference/events/list-events)
|
||||
|
||||
**For Markets:** [GET /markets/slug/{slug}](/api-reference/markets/list-markets)
|
||||
**For Markets:** [GET /markets/slug/{slug}](https://docs.polymarket.com/api-reference/markets/list-markets)
|
||||
|
||||
**Use Case:** When you want to filter markets by category, sport, or topic.
|
||||
|
||||
|
|
@ -62,9 +62,9 @@ Tags provide a powerful way to categorize and filter markets. You can discover a
|
|||
|
||||
### Discover Available Tags
|
||||
|
||||
**General Tags:** [GET /tags](/api-reference/tags/list-tags)
|
||||
**General Tags:** [GET /tags](https://docs.polymarket.com/api-reference/tags/list-tags)
|
||||
|
||||
**Sports Tags & Metadata:** [GET /sports](/api-reference/sports/get-sports-metadata-information)
|
||||
**Sports Tags & Metadata:** [GET /sports](https://docs.polymarket.com/api-reference/sports/get-sports-metadata-information)
|
||||
|
||||
The `/sports` endpoint returns comprehensive metadata for sports including tag IDs, images, resolution sources, and series information.
|
||||
|
||||
|
|
@ -72,9 +72,9 @@ The `/sports` endpoint returns comprehensive metadata for sports including tag I
|
|||
|
||||
Once you have tag IDs, you can use them with the `tag_id` parameter in both markets and events endpoints.
|
||||
|
||||
**Markets with Tags:** [GET /markets](/api-reference/markets/list-markets)
|
||||
**Markets with Tags:** [GET /markets](https://docs.polymarket.com/api-reference/markets/list-markets)
|
||||
|
||||
**Events with Tags:** [GET /events](/api-reference/events/list-events)
|
||||
**Events with Tags:** [GET /events](https://docs.polymarket.com/api-reference/events/list-events)
|
||||
|
||||
### Additional Tag Filtering
|
||||
|
||||
|
|
@ -87,9 +87,9 @@ Once you have tag IDs, you can use them with the `tag_id` parameter in both mark
|
|||
|
||||
The most efficient approach is to use the `/events` endpoint and work backwards, as events contain their associated markets.
|
||||
|
||||
**Events Endpoint:** [GET /events](/api-reference/events/list-events)
|
||||
**Events Endpoint:** [GET /events](https://docs.polymarket.com/api-reference/events/list-events)
|
||||
|
||||
**Markets Endpoint:** [GET /markets](/api-reference/markets/list-markets)
|
||||
**Markets Endpoint:** [GET /markets](https://docs.polymarket.com/api-reference/markets/list-markets)
|
||||
|
||||
* `order=id` - Order by event ID
|
||||
* `ascending=false` - Get newest events first
|
||||
|
|
@ -129,9 +129,9 @@ Tags provide a powerful way to categorize and filter markets. You can discover a
|
|||
|
||||
### Discover Available Tags
|
||||
|
||||
**General Tags:** [GET /tags](/api-reference/tags/list-tags)
|
||||
**General Tags:** [GET /tags](https://docs.polymarket.com/api-reference/tags/list-tags)
|
||||
|
||||
**Sports Tags & Metadata:** [GET /sports](/api-reference/sports/get-sports-metadata-information)
|
||||
**Sports Tags & Metadata:** [GET /sports](https://docs.polymarket.com/api-reference/sports/get-sports-metadata-information)
|
||||
|
||||
The `/sports` endpoint returns comprehensive metadata for sports including tag IDs, images, resolution sources, and series information.
|
||||
|
||||
|
|
@ -139,9 +139,9 @@ The `/sports` endpoint returns comprehensive metadata for sports including tag I
|
|||
|
||||
Once you have tag IDs, you can use them with the `tag_id` parameter in both markets and events endpoints.
|
||||
|
||||
**Markets with Tags:** [GET /markets](/api-reference/markets/list-markets)
|
||||
**Markets with Tags:** [GET /markets](https://docs.polymarket.com/api-reference/markets/list-markets)
|
||||
|
||||
**Events with Tags:** [GET /events](/api-reference/events/list-events)
|
||||
**Events with Tags:** [GET /events](https://docs.polymarket.com/api-reference/events/list-events)
|
||||
```
|
||||
|
||||
Example 3 (unknown):
|
||||
|
|
@ -161,9 +161,9 @@ You can also:
|
|||
|
||||
The most efficient approach is to use the `/events` endpoint and work backwards, as events contain their associated markets.
|
||||
|
||||
**Events Endpoint:** [GET /events](/api-reference/events/list-events)
|
||||
**Events Endpoint:** [GET /events](https://docs.polymarket.com/api-reference/events/list-events)
|
||||
|
||||
**Markets Endpoint:** [GET /markets](/api-reference/markets/list-markets)
|
||||
**Markets Endpoint:** [GET /markets](https://docs.polymarket.com/api-reference/markets/list-markets)
|
||||
|
||||
### Key Parameters
|
||||
|
||||
|
|
@ -200,7 +200,7 @@ For large datasets, use pagination with `limit` and `offset` parameters:
|
|||
- Video Walkthrough
|
||||
- Placing a Market Order
|
||||
|
||||
Once you've [signed up](../get-started/how-to-signup) and [deposited funds](../get-started/how-to-deposit), you're ready to start trading on Polymarket. Here's a step-by-step guide to get you started.
|
||||
Once you've [signed up](https://docs.polymarket.com/polymarket-learn/get-started/how-to-signup) and [deposited funds](https://docs.polymarket.com/polymarket-learn/get-started/how-to-deposit), you're ready to start trading on Polymarket. Here's a step-by-step guide to get you started.
|
||||
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/1lFgkHLqo28?si=i7e61-roRsOVeRMW" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen />
|
||||
|
||||
|
|
@ -230,6 +230,6 @@ You'll also see a bet slip to share on social media. We love sending \$\$\$ to t
|
|||
</Steps.Step>
|
||||
</Steps>
|
||||
|
||||
Simple, right? If you think you've got the hang of it, it's time to learn about more advanced trading and order types. [Limit Orders](../trading/limit-orders/).
|
||||
Simple, right? If you think you've got the hang of it, it's time to learn about more advanced trading and order types. [Limit Orders](https://docs.polymarket.com/polymarket-learn/trading/limit-orders/).
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -107,7 +107,7 @@ While users cannot directly create their own markets, they are encouraged to sug
|
|||
To give your proposal the best chance of being listed, include as much information as possible, such as:
|
||||
|
||||
* What is the market title?
|
||||
* What is the [resolution source](../markets/how-are-markets-resolved)?
|
||||
* What is the [resolution source](https://docs.polymarket.com/polymarket-learn/markets/how-are-markets-resolved)?
|
||||
* Evidence of demand for trading that market
|
||||
|
||||
The best ways to propose a new market are:
|
||||
|
|
@ -388,7 +388,7 @@ Polymarket recognizes the importance of a trustworthy environment for managing y
|
|||
|
||||
### Your keys = your funds
|
||||
|
||||
A private key acts like a highly secure password, essential for managing and moving your assets without restrictions. You can export your private key at any time, ensuring sole access to your funds. Learn how to export your private key [here](../FAQ/how-to-export-private-key/).
|
||||
A private key acts like a highly secure password, essential for managing and moving your assets without restrictions. You can export your private key at any time, ensuring sole access to your funds. Learn how to export your private key [here](https://docs.polymarket.com/polymarket-learn/FAQ/how-to-export-private-key/).
|
||||
|
||||
### Keep your private keys private.
|
||||
|
||||
|
|
@ -484,7 +484,7 @@ If your exchange supports sending or withdrawing to Polygon, we recommend this o
|
|||
|
||||
For detailed instructions, check out our guides for purchasing and depositing USDC using popular exchanges:
|
||||
|
||||
* [Deposit from Coinbase](../deposits/coinbase) (recommended)
|
||||
* [Deposit from Coinbase](https://docs.polymarket.com/polymarket-learn/deposits/coinbase) (recommended)
|
||||
|
||||
<Note>
|
||||
If you decide to use an exchange to purchase and send (deposit) USDC to your Polygon deposit address, please ensure you're sending on Polygon Network. If you're unsure, please reach out to support on [Discord](https://discord.com/invite/polymarket).
|
||||
|
|
@ -492,11 +492,11 @@ For detailed instructions, check out our guides for purchasing and depositing US
|
|||
|
||||
### Deposit with Visa or Mastercard
|
||||
|
||||
MoonPay enables you to buy USDC (on Polygon) using your Visa, Mastercard, and select bank cards. Please be aware that payment options and transaction limits may vary depending on your region. [How to use MoonPay](../deposits/moonpay/).
|
||||
MoonPay enables you to buy USDC (on Polygon) using your Visa, Mastercard, and select bank cards. Please be aware that payment options and transaction limits may vary depending on your region. [How to use MoonPay](https://docs.polymarket.com/polymarket-learn/deposits/moonpay/).
|
||||
|
||||
### Depositing on Etheruem and Polygon
|
||||
|
||||
You can send USDC with your wallet on Ethereum or USDC.e on Polygon to your respective deposit addresses found on the Deposit page. [Learn more](../deposits/usdc-on-eth/).
|
||||
You can send USDC with your wallet on Ethereum or USDC.e on Polygon to your respective deposit addresses found on the Deposit page. [Learn more](https://docs.polymarket.com/polymarket-learn/deposits/usdc-on-eth/).
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -631,11 +631,11 @@ Source: https://docs.polymarket.com/polymarket-learn/trading/using-the-orderbook
|
|||
|
||||
Understanding the Order Book will help you become an advanced trader.
|
||||
|
||||
In the Getting Started tutorial on [Making your First Trade](../get-started/making-your-first-trade/), we learned about market orders.
|
||||
In the Getting Started tutorial on [Making your First Trade](https://docs.polymarket.com/polymarket-learn/get-started/making-your-first-trade/), we learned about market orders.
|
||||
|
||||
In a market order, your trade executes instantly at the current market price.
|
||||
|
||||
But what if you think the market price is too high and want to set a specific price that you would be willing to accept? These are called [Limit Orders](../trading/limit-orders/).
|
||||
But what if you think the market price is too high and want to set a specific price that you would be willing to accept? These are called [Limit Orders](https://docs.polymarket.com/polymarket-learn/trading/limit-orders/).
|
||||
|
||||
## Viewing the Order Book
|
||||
|
||||
|
|
@ -735,7 +735,7 @@ When your orders are earning rewards you’ll see a blue highlight around the cl
|
|||
|
||||
Rewards are paid out automatically every day at \~midnight UTC. Your history on your portfolio page will reflect rewards paid to your address.
|
||||
|
||||
To read more about the specific calculations and formulas that determine rewards, visit our [Rewards Documentation](/developers/rewards/overview).
|
||||
To read more about the specific calculations and formulas that determine rewards, visit our [Rewards Documentation](https://docs.polymarket.com/developers/rewards/overview).
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -866,7 +866,7 @@ In rare cases, circumstances occur that were not foreseen at a market’s creati
|
|||
|
||||
Source: https://docs.polymarket.com/polymarket-learn/get-started/making-your-first-trade
|
||||
|
||||
Once you've [signed up](../get-started/how-to-signup) and [deposited funds](../get-started/how-to-deposit), you're ready to start trading on Polymarket. Here's a step-by-step guide to get you started.
|
||||
Once you've [signed up](https://docs.polymarket.com/polymarket-learn/get-started/how-to-signup) and [deposited funds](https://docs.polymarket.com/polymarket-learn/get-started/how-to-deposit), you're ready to start trading on Polymarket. Here's a step-by-step guide to get you started.
|
||||
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/1lFgkHLqo28?si=i7e61-roRsOVeRMW" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen />
|
||||
|
||||
|
|
@ -895,7 +895,7 @@ You'll also see a bet slip to share on social media. We love sending \$\$\$ to t
|
|||
</Steps.Step>
|
||||
</Steps>
|
||||
|
||||
Simple, right? If you think you've got the hang of it, it's time to learn about more advanced trading and order types. [Limit Orders](../trading/limit-orders/).
|
||||
Simple, right? If you think you've got the hang of it, it's time to learn about more advanced trading and order types. [Limit Orders](https://docs.polymarket.com/polymarket-learn/trading/limit-orders/).
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -955,7 +955,7 @@ The prices probabilities displayed on Polymarket are the midpoint of the bid-ask
|
|||
|
||||
* When a market is created, there are initially zero shares and no pre-defined prices or odds.
|
||||
|
||||
* Market makers (a fancy term for traders placing limit orders) interested in buying YES or NO shares can place [Limit Orders](../trading/limit-orders) at the price they're willing to pay
|
||||
* Market makers (a fancy term for traders placing limit orders) interested in buying YES or NO shares can place [Limit Orders](https://docs.polymarket.com/polymarket-learn/trading/limit-orders) at the price they're willing to pay
|
||||
|
||||
* When offers for the YES and NO side equal \$1.00, the order is "matched" and that \$1.00 is converted into 1 YES and 1 NO share, each going to their respective buyers.
|
||||
|
||||
|
|
@ -1373,6 +1373,6 @@ Once in the verification process, UMA will review the transaction to ensure it w
|
|||
|
||||
Once a market is proposed for resolution it goes into a challenge period of 2 hours.
|
||||
|
||||
If you do not agree with a proposed resolution, you can [dispute the outcome](../markets/dispute).
|
||||
If you do not agree with a proposed resolution, you can [dispute the outcome](https://docs.polymarket.com/polymarket-learn/markets/dispute).
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -307,12 +307,12 @@ Welcome to the Polymarket Changelog. Here you will find any important changes to
|
|||
* **Comment Streaming**: Real-time updates for comment events including new comments, replies, and reactions
|
||||
* **Dynamic Subscriptions**: Add, remove, and modify subscriptions without reconnecting
|
||||
* **TypeScript Client**: Official TypeScript client available at [real-time-data-client](https://github.com/Polymarket/real-time-data-client)
|
||||
For complete documentation, see [RTDS Overview](/developers/RTDS/RTDS-overview).
|
||||
For complete documentation, see [RTDS Overview](https://docs.polymarket.com/developers/RTDS/RTDS-overview).
|
||||
</Update>
|
||||
|
||||
<Update label="September 15, 2025" description="WSS price_change event update">
|
||||
* There has been a significant change to the structure of the price change message. This update will be applied at 11PM UTC September 15, 2025. We apologize for the short notice
|
||||
* Please see the [migration guide](/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
* Please see the [migration guide](https://docs.polymarket.com/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
</Update>
|
||||
|
||||
<Update label="August 26, 2025" description="Updated /trades and /activity endpoints">
|
||||
|
|
@ -322,7 +322,7 @@ Welcome to the Polymarket Changelog. Here you will find any important changes to
|
|||
</Update>
|
||||
|
||||
<Update label="August 21, 2025" description="Batch Orders Increase">
|
||||
* The batch orders limit has been increased from from 5 -> 15. Read more about the batch orders functionality [here](/developers/CLOB/orders/create-order-batch).
|
||||
* The batch orders limit has been increased from from 5 -> 15. Read more about the batch orders functionality [here](https://docs.polymarket.com/developers/CLOB/orders/create-order-batch).
|
||||
</Update>
|
||||
|
||||
<Update label="July 23, 2025" description="Get Book(s) update">
|
||||
|
|
@ -339,11 +339,11 @@ Welcome to the Polymarket Changelog. Here you will find any important changes to
|
|||
</Update>
|
||||
|
||||
<Update label="June 3, 2025" description="New Batch Orders Endpoint">
|
||||
* We’re excited to roll out a highly requested feature: **order batching**. With this new endpoint, users can now submit up to five trades in a single request. To help you get started, we’ve included sample code demonstrating how to use it. Please see [Place Multiple Orders (Batching)](/developers/CLOB/orders/create-order-batch) for more details.
|
||||
* We’re excited to roll out a highly requested feature: **order batching**. With this new endpoint, users can now submit up to five trades in a single request. To help you get started, we’ve included sample code demonstrating how to use it. Please see [Place Multiple Orders (Batching)](https://docs.polymarket.com/developers/CLOB/orders/create-order-batch) for more details.
|
||||
</Update>
|
||||
|
||||
<Update label="June 3, 2025" description="Change to /data/trades">
|
||||
* We're adding a new `side` field to the `MakerOrder` portion of the trade object. This field will indicate whether the maker order is a `buy` or `sell`, helping to clarify trade events where the maker side was previously ambiguous. For more details, refer to the MakerOrder object on the [Get Trades](/developers/CLOB/trades/trades) page.
|
||||
* We're adding a new `side` field to the `MakerOrder` portion of the trade object. This field will indicate whether the maker order is a `buy` or `sell`, helping to clarify trade events where the maker side was previously ambiguous. For more details, refer to the MakerOrder object on the [Get Trades](https://docs.polymarket.com/developers/CLOB/trades/trades) page.
|
||||
</Update>
|
||||
|
||||
<Update label="May 28, 2025" description="Websocket Changes">
|
||||
|
|
@ -1267,7 +1267,7 @@ Instructions for placing multiple orders(Batch)
|
|||
|
||||
<Tip> This endpoint requires a L2 Header </Tip>
|
||||
|
||||
Polymarket’s CLOB supports batch orders, allowing you to place up to `15` orders in a single request. Before using this feature, make sure you're comfortable placing a single order first. You can find the documentation for that [here.](/developers/CLOB/orders/create-order)
|
||||
Polymarket’s CLOB supports batch orders, allowing you to place up to `15` orders in a single request. Before using this feature, make sure you're comfortable placing a single order first. You can find the documentation for that [here.](https://docs.polymarket.com/developers/CLOB/orders/create-order)
|
||||
|
||||
**HTTP REQUEST**
|
||||
|
||||
|
|
@ -1847,7 +1847,7 @@ Where a `OrderSummary` object is of the form:
|
|||
## price\_change Message
|
||||
|
||||
<div style={{backgroundColor: '#fff3cd', border: '1px solid #ffeaa7', borderRadius: '4px', padding: '12px', marginBottom: '16px'}}>
|
||||
<strong>⚠️ Breaking Change Notice:</strong> The price\_change message schema will be updated on September 15, 2025 at 11 PM UTC. Please see the [migration guide](/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
<strong>⚠️ Breaking Change Notice:</strong> The price\_change message schema will be updated on September 15, 2025 at 11 PM UTC. Please see the [migration guide](https://docs.polymarket.com/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
</div>
|
||||
|
||||
Emitted When:
|
||||
|
|
@ -2707,8 +2707,8 @@ The WebSocket connection supports:
|
|||
|
||||
The RTDS currently supports the following subscription types:
|
||||
|
||||
1. **[Crypto Prices](/developers/RTDS/RTDS-crypto-prices)** - Real-time cryptocurrency price updates
|
||||
2. **[Comments](/developers/RTDS/RTDS-comments)** - Comment-related events including reactions
|
||||
1. **[Crypto Prices](https://docs.polymarket.com/developers/RTDS/RTDS-crypto-prices)** - Real-time cryptocurrency price updates
|
||||
2. **[Comments](https://docs.polymarket.com/developers/RTDS/RTDS-comments)** - Comment-related events including reactions
|
||||
|
||||
## Message Structure
|
||||
|
||||
|
|
@ -2802,9 +2802,9 @@ https://polymarket.com/event/fed-decision-in-october?tid=1758818660485
|
|||
|
||||
### API Endpoints
|
||||
|
||||
**For Events:** [GET /events/slug/{slug}](/api-reference/events/list-events)
|
||||
**For Events:** [GET /events/slug/{slug}](https://docs.polymarket.com/api-reference/events/list-events)
|
||||
|
||||
**For Markets:** [GET /markets/slug/{slug}](/api-reference/markets/list-markets)
|
||||
**For Markets:** [GET /markets/slug/{slug}](https://docs.polymarket.com/api-reference/markets/list-markets)
|
||||
|
||||
### Examples
|
||||
|
||||
|
|
@ -2822,9 +2822,9 @@ Tags provide a powerful way to categorize and filter markets. You can discover a
|
|||
|
||||
### Discover Available Tags
|
||||
|
||||
**General Tags:** [GET /tags](/api-reference/tags/list-tags)
|
||||
**General Tags:** [GET /tags](https://docs.polymarket.com/api-reference/tags/list-tags)
|
||||
|
||||
**Sports Tags & Metadata:** [GET /sports](/api-reference/sports/get-sports-metadata-information)
|
||||
**Sports Tags & Metadata:** [GET /sports](https://docs.polymarket.com/api-reference/sports/get-sports-metadata-information)
|
||||
|
||||
The `/sports` endpoint returns comprehensive metadata for sports including tag IDs, images, resolution sources, and series information.
|
||||
|
||||
|
|
@ -2832,9 +2832,9 @@ The `/sports` endpoint returns comprehensive metadata for sports including tag I
|
|||
|
||||
Once you have tag IDs, you can use them with the `tag_id` parameter in both markets and events endpoints.
|
||||
|
||||
**Markets with Tags:** [GET /markets](/api-reference/markets/list-markets)
|
||||
**Markets with Tags:** [GET /markets](https://docs.polymarket.com/api-reference/markets/list-markets)
|
||||
|
||||
**Events with Tags:** [GET /events](/api-reference/events/list-events)
|
||||
**Events with Tags:** [GET /events](https://docs.polymarket.com/api-reference/events/list-events)
|
||||
|
||||
```bash theme={null}
|
||||
curl "https://gamma-api.polymarket.com/events?tag_id=100381&limit=1&closed=false"
|
||||
|
|
@ -2856,9 +2856,9 @@ You can also:
|
|||
|
||||
The most efficient approach is to use the `/events` endpoint and work backwards, as events contain their associated markets.
|
||||
|
||||
**Events Endpoint:** [GET /events](/api-reference/events/list-events)
|
||||
**Events Endpoint:** [GET /events](https://docs.polymarket.com/api-reference/events/list-events)
|
||||
|
||||
**Markets Endpoint:** [GET /markets](/api-reference/markets/list-markets)
|
||||
**Markets Endpoint:** [GET /markets](https://docs.polymarket.com/api-reference/markets/list-markets)
|
||||
|
||||
### Key Parameters
|
||||
|
||||
|
|
@ -2922,9 +2922,9 @@ curl "https://gamma-api.polymarket.com/markets?tag_id=100381&closed=false&limit=
|
|||
|
||||
## Related Endpoints
|
||||
|
||||
* [Get Markets](/developers/gamma-markets-api/get-markets) - Full markets endpoint documentation
|
||||
* [Get Events](/developers/gamma-markets-api/get-events) - Full events endpoint documentation
|
||||
* [Search Markets](/developers/gamma-markets-api/get-public-search) - Search functionality
|
||||
* [Get Markets](https://docs.polymarket.com/developers/gamma-markets-api/get-markets) - Full markets endpoint documentation
|
||||
* [Get Events](https://docs.polymarket.com/developers/gamma-markets-api/get-events) - Full events endpoint documentation
|
||||
* [Search Markets](https://docs.polymarket.com/developers/gamma-markets-api/get-public-search) - Search functionality
|
||||
|
||||
|
||||
# Gamma Structure
|
||||
|
|
@ -3266,7 +3266,7 @@ Source: https://docs.polymarket.com/polymarket-learn/FAQ/does-polymarket-have-an
|
|||
|
||||
Getting data from Polymarket
|
||||
|
||||
Yes! Developers can find all the information they need for interacting with Polymarket. This includes [documentation on market discovery, resolution, trading etc.](/quickstart/introduction/main)
|
||||
Yes! Developers can find all the information they need for interacting with Polymarket. This includes [documentation on market discovery, resolution, trading etc.](https://docs.polymarket.com/quickstart/introduction/main)
|
||||
|
||||
Whether you are an academic researcher a market maker or an indepedent developer, this documentation should provide you what you need to get started. All the code you find linked here and on our [GitHub](https://github.com/polymarket) is open source and free to use.
|
||||
|
||||
|
|
@ -3335,7 +3335,7 @@ Polymarket recognizes the importance of a trustworthy environment for managing y
|
|||
|
||||
### Your keys = your funds
|
||||
|
||||
A private key acts like a highly secure password, essential for managing and moving your assets without restrictions. You can export your private key at any time, ensuring sole access to your funds. Learn how to export your private key [here](../FAQ/how-to-export-private-key/).
|
||||
A private key acts like a highly secure password, essential for managing and moving your assets without restrictions. You can export your private key at any time, ensuring sole access to your funds. Learn how to export your private key [here](https://docs.polymarket.com/polymarket-learn/FAQ/how-to-export-private-key/).
|
||||
|
||||
### Keep your private keys private.
|
||||
|
||||
|
|
@ -3806,7 +3806,7 @@ If your exchange supports sending or withdrawing to Polygon, we recommend this o
|
|||
|
||||
For detailed instructions, check out our guides for purchasing and depositing USDC using popular exchanges:
|
||||
|
||||
* [Deposit from Coinbase](../deposits/coinbase) (recommended)
|
||||
* [Deposit from Coinbase](https://docs.polymarket.com/polymarket-learn/deposits/coinbase) (recommended)
|
||||
|
||||
<Note>
|
||||
If you decide to use an exchange to purchase and send (deposit) USDC to your Polygon deposit address, please ensure you're sending on Polygon Network. If you're unsure, please reach out to support on [Discord](https://discord.com/invite/polymarket).
|
||||
|
|
@ -3814,11 +3814,11 @@ For detailed instructions, check out our guides for purchasing and depositing US
|
|||
|
||||
### Deposit with Visa or Mastercard
|
||||
|
||||
MoonPay enables you to buy USDC (on Polygon) using your Visa, Mastercard, and select bank cards. Please be aware that payment options and transaction limits may vary depending on your region. [How to use MoonPay](../deposits/moonpay/).
|
||||
MoonPay enables you to buy USDC (on Polygon) using your Visa, Mastercard, and select bank cards. Please be aware that payment options and transaction limits may vary depending on your region. [How to use MoonPay](https://docs.polymarket.com/polymarket-learn/deposits/moonpay/).
|
||||
|
||||
### Depositing on Etheruem and Polygon
|
||||
|
||||
You can send USDC with your wallet on Ethereum or USDC.e on Polygon to your respective deposit addresses found on the Deposit page. [Learn more](../deposits/usdc-on-eth/).
|
||||
You can send USDC with your wallet on Ethereum or USDC.e on Polygon to your respective deposit addresses found on the Deposit page. [Learn more](https://docs.polymarket.com/polymarket-learn/deposits/usdc-on-eth/).
|
||||
|
||||
|
||||
# How to Sign-Up
|
||||
|
|
@ -3897,7 +3897,7 @@ Source: https://docs.polymarket.com/polymarket-learn/get-started/making-your-fir
|
|||
|
||||
How to buy shares.
|
||||
|
||||
Once you've [signed up](../get-started/how-to-signup) and [deposited funds](../get-started/how-to-deposit), you're ready to start trading on Polymarket. Here's a step-by-step guide to get you started.
|
||||
Once you've [signed up](https://docs.polymarket.com/polymarket-learn/get-started/how-to-signup) and [deposited funds](https://docs.polymarket.com/polymarket-learn/get-started/how-to-deposit), you're ready to start trading on Polymarket. Here's a step-by-step guide to get you started.
|
||||
|
||||
## Video guide
|
||||
|
||||
|
|
@ -3930,7 +3930,7 @@ screen shot.
|
|||
</Steps.Step>
|
||||
</Steps>
|
||||
|
||||
Simple, right? If you think you've got the hang of it, it's time to learn about more advanced trading and order types. [Limit Orders](../trading/limit-orders/).
|
||||
Simple, right? If you think you've got the hang of it, it's time to learn about more advanced trading and order types. [Limit Orders](https://docs.polymarket.com/polymarket-learn/trading/limit-orders/).
|
||||
|
||||
|
||||
# What is Polymarket?
|
||||
|
|
@ -3944,13 +3944,13 @@ Studies show prediction markets are often more accurate than pundits because the
|
|||
|
||||
## Quick Overview
|
||||
|
||||
* On Polymarket, you can [buy and sell shares](making-your-first-trade) representing future event outcomes (i.e. "Will TikTok be banned in the U.S. this year?")
|
||||
* On Polymarket, you can [buy and sell shares](https://docs.polymarket.com/polymarket-learn/get-started/making-your-first-trade) representing future event outcomes (i.e. "Will TikTok be banned in the U.S. this year?")
|
||||
|
||||
* Shares in event outcomes are [always priced](what-is-polymarket/#understanding-prices) between 0.00 and 1.00 [USDC](../FAQ/why-do-i-need-crypto/#why-usdc), and every pair of event outcomes (i.e. each pair of "YES" + "NO" shares) is fully collateralized by \$1.00 USDC.
|
||||
* Shares in event outcomes are [always priced](https://docs.polymarket.com/polymarket-learn/get-started/what-is-polymarket/#understanding-prices) between 0.00 and 1.00 [USDC](https://docs.polymarket.com/polymarket-learn/FAQ/why-do-i-need-crypto/#why-usdc), and every pair of event outcomes (i.e. each pair of "YES" + "NO" shares) is fully collateralized by \$1.00 USDC.
|
||||
|
||||
* Shares are created when [opposing sides come to an agreement on odds](../trading/limit-orders), such that the sum of what each side is willing to pay is equal to \$1.00.
|
||||
* Shares are created when [opposing sides come to an agreement on odds](https://docs.polymarket.com/polymarket-learn/trading/limit-orders), such that the sum of what each side is willing to pay is equal to \$1.00.
|
||||
|
||||
* The shares representing the *correct, final outcome* are paid out \$1.00 USDC each upon [market resolution](../markets/how-are-markets-resolved).
|
||||
* The shares representing the *correct, final outcome* are paid out \$1.00 USDC each upon [market resolution](https://docs.polymarket.com/polymarket-learn/markets/how-are-markets-resolved).
|
||||
|
||||
* Unlike sportsbooks, you are not betting against "the house" – the counterparty to each trade is another Polymarket user. As such:
|
||||
|
||||
|
|
@ -3968,7 +3968,7 @@ Prices = Probabilities.
|
|||
|
||||
These odds are determined by what price other Polymarket users are currently willing to buy & sell those shares at. Just how stock exchanges don't "set" the prices of stocks, Polymarket does not set prices / odds - they're a function of supply & demand.
|
||||
|
||||
[Learn more >](/docs/guides/trading/how-are-prices-calculated)
|
||||
[Learn more >](https://docs.polymarket.com/docs/guides/trading/how-are-prices-calculated)
|
||||
|
||||
### Making money on markets
|
||||
|
||||
|
|
@ -4091,7 +4091,7 @@ While users cannot directly create their own markets, they are encouraged to sug
|
|||
To give your proposal the best chance of being listed, include as much information as possible, such as:
|
||||
|
||||
* What is the market title?
|
||||
* What is the [resolution source](../markets/how-are-markets-resolved)?
|
||||
* What is the [resolution source](https://docs.polymarket.com/polymarket-learn/markets/how-are-markets-resolved)?
|
||||
* Evidence of demand for trading that market
|
||||
|
||||
The best ways to propose a new market are:
|
||||
|
|
@ -4149,7 +4149,7 @@ Once in the verification process, UMA will review the transaction to ensure it w
|
|||
|
||||
Once a market is proposed for resolution it goes into a challenge period of 2 hours.
|
||||
|
||||
If you do not agree with a proposed resolution, you can [dispute the outcome](../markets/dispute).
|
||||
If you do not agree with a proposed resolution, you can [dispute the outcome](https://docs.polymarket.com/polymarket-learn/markets/dispute).
|
||||
|
||||
|
||||
# Trading Fees
|
||||
|
|
@ -4230,7 +4230,7 @@ The prices probabilities displayed on Polymarket are the midpoint of the bid-ask
|
|||
|
||||
* When a market is created, there are initially zero shares and no pre-defined prices or odds.
|
||||
|
||||
* Market makers (a fancy term for traders placing limit orders) interested in buying YES or NO shares can place [Limit Orders](../trading/limit-orders) at the price they're willing to pay
|
||||
* Market makers (a fancy term for traders placing limit orders) interested in buying YES or NO shares can place [Limit Orders](https://docs.polymarket.com/polymarket-learn/trading/limit-orders) at the price they're willing to pay
|
||||
|
||||
* When offers for the YES and NO side equal \$1.00, the order is "matched" and that \$1.00 is converted into 1 YES and 1 NO share, each going to their respective buyers.
|
||||
|
||||
|
|
@ -4388,7 +4388,7 @@ When your orders are earning rewards you’ll see a blue highlight around the cl
|
|||
|
||||
Rewards are paid out automatically every day at \~midnight UTC. Your history on your portfolio page will reflect rewards paid to your address.
|
||||
|
||||
To read more about the specific calculations and formulas that determine rewards, visit our [Rewards Documentation](/developers/rewards/overview).
|
||||
To read more about the specific calculations and formulas that determine rewards, visit our [Rewards Documentation](https://docs.polymarket.com/developers/rewards/overview).
|
||||
|
||||
|
||||
# Market Orders
|
||||
|
|
@ -4398,7 +4398,7 @@ How to buy shares.
|
|||
|
||||
# Market Orders
|
||||
|
||||
Once you've [signed up](../get-started/how-to-signup) and [deposited funds](../get-started/how-to-deposit), you're ready to start trading on Polymarket. Here's a step-by-step guide to get you started.
|
||||
Once you've [signed up](https://docs.polymarket.com/polymarket-learn/get-started/how-to-signup) and [deposited funds](https://docs.polymarket.com/polymarket-learn/get-started/how-to-deposit), you're ready to start trading on Polymarket. Here's a step-by-step guide to get you started.
|
||||
|
||||
## Video Walkthrough
|
||||
|
||||
|
|
@ -4430,7 +4430,7 @@ Once you've [signed up](../get-started/how-to-signup) and [deposited funds](../g
|
|||
</Steps.Step>
|
||||
</Steps>
|
||||
|
||||
Simple, right? If you think you've got the hang of it, it's time to learn about more advanced trading and order types. [Limit Orders](../trading/limit-orders/).
|
||||
Simple, right? If you think you've got the hang of it, it's time to learn about more advanced trading and order types. [Limit Orders](https://docs.polymarket.com/polymarket-learn/trading/limit-orders/).
|
||||
|
||||
|
||||
# Does Polymarket Have Trading Limits?
|
||||
|
|
@ -4448,11 +4448,11 @@ Source: https://docs.polymarket.com/polymarket-learn/trading/using-the-orderbook
|
|||
|
||||
Understanding the Order Book will help you become an advanced trader.
|
||||
|
||||
In the Getting Started tutorial on [Making your First Trade](../get-started/making-your-first-trade/), we learned about market orders.
|
||||
In the Getting Started tutorial on [Making your First Trade](https://docs.polymarket.com/polymarket-learn/get-started/making-your-first-trade/), we learned about market orders.
|
||||
|
||||
In a market order, your trade executes instantly at the current market price.
|
||||
|
||||
But what if you think the market price is too high and want to set a specific price that you would be willing to accept? These are called [Limit Orders](../trading/limit-orders/).
|
||||
But what if you think the market price is too high and want to set a specific price that you would be willing to accept? These are called [Limit Orders](https://docs.polymarket.com/polymarket-learn/trading/limit-orders/).
|
||||
|
||||
## Viewing the Order Book
|
||||
|
||||
|
|
@ -4506,7 +4506,7 @@ Source: https://docs.polymarket.com/quickstart/introduction/definitions
|
|||
| **Token** | A token represents a stake in a specific Yes/No outcome in a Market. The price of a token can fluctuate between $0 - $1 based on the market belief in the outcome. When a market resolves, the token associated with the correct prediction can be redeemed for \$1 USDC. This is also sometimes called an *Asset Id* |
|
||||
| **Market** | A single event outcome. Corresponds to a pair of CLOB token IDs(Yes/No), a market address, a question ID and a condition ID. |
|
||||
| **Event** | A collection of related markets grouped under a common topic or theme. |
|
||||
| **SLUG** | A human readable identification for a market or event. Can be found in the URL of any Polymarket Market or Event. You can use this slug to find more detailed information about a market or event by using it as a parameter in the [Get Events](/developers/gamma-markets-api/get-events) or [Get Markets](/developers/gamma-markets-api/get-markets) endpoints. |
|
||||
| **SLUG** | A human readable identification for a market or event. Can be found in the URL of any Polymarket Market or Event. You can use this slug to find more detailed information about a market or event by using it as a parameter in the [Get Events](https://docs.polymarket.com/developers/gamma-markets-api/get-events) or [Get Markets](https://docs.polymarket.com/developers/gamma-markets-api/get-markets) endpoints. |
|
||||
| **Negative Risk (negrisk)** | A group of Markets(Event) in which only one Market can resolve as yes. For more detail see [Negrisk Details](https://docs.polymarket.com/developers/neg-risk/overview) |
|
||||
| **Central Limit Order Book** | The off-chain order matching system. This is where you place resting orders and market orders are matched with existing orders before being sent on-chain. |
|
||||
| **Polygon Network** | A scalable, multi-chain blockchain platform used by Polymarket to facilitate on-chain activities(contract creation, token transfers, etc) |
|
||||
|
|
@ -4521,7 +4521,7 @@ This section of the documentation will provide all the essential resources to he
|
|||
|
||||
Everything you need to start building with the Polymarket API is right here. Let’s get started.
|
||||
|
||||
[Not sure what to build next? Get inspired by checking out real examples from other developers using the API.](/quickstart/introduction/showcase)
|
||||
[Not sure what to build next? Get inspired by checking out real examples from other developers using the API.](https://docs.polymarket.com/quickstart/introduction/showcase)
|
||||
|
||||
|
||||
# API Rate Limits
|
||||
|
|
@ -4738,14 +4738,14 @@ After installing one of those you will be able to run the below code. Take the t
|
|||
#### In addition to detailed comments in the code snippet, here are some more tips to help you get started.
|
||||
|
||||
* See the Python example for details on the proper way to initialize a Py-Clob-Client depending on your wallet type. Three exhaustive examples are given. If using a MetaMask wallet or EOA please see the resources [here](https://github.com/Polymarket/py-clob-client?tab=readme-ov-file), for instructions on setting allowances.
|
||||
* When buying into a market you purchase a "Token" that token represents either a Yes or No outcome of the event. To easily get required token pairs for a given event we have provided an interactive endpoint [here](/developers/gamma-markets-api/get-markets).
|
||||
* When buying into a market you purchase a "Token" that token represents either a Yes or No outcome of the event. To easily get required token pairs for a given event we have provided an interactive endpoint [here](https://docs.polymarket.com/developers/gamma-markets-api/get-markets).
|
||||
* Common pitfalls:
|
||||
* Negrisk Markets require an additional flag in the OrderArgs `negrisk=False `
|
||||
* `invalid signature` error, likely due to one of the following.
|
||||
* Incorrect Funder and or Private Key
|
||||
* Incorrect NegRisk flag in your order arguments
|
||||
* `not enough balance / allowance`.
|
||||
* Not enough USDC to perform the trade. See the formula at the bottom of [this](/developers/CLOB/orders/orders) page for details.
|
||||
* Not enough USDC to perform the trade. See the formula at the bottom of [this](https://docs.polymarket.com/developers/CLOB/orders/orders) page for details.
|
||||
* If using Metamask / WEB3 wallet go [here](https://github.com/Polymarket/py-clob-client?tab=readme-ov-file), for instructions on setting allowances.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -96,8 +96,8 @@ The WebSocket connection supports:
|
|||
|
||||
The RTDS currently supports the following subscription types:
|
||||
|
||||
1. **[Crypto Prices](/developers/RTDS/RTDS-crypto-prices)** - Real-time cryptocurrency price updates
|
||||
2. **[Comments](/developers/RTDS/RTDS-comments)** - Comment-related events including reactions
|
||||
1. **[Crypto Prices](https://docs.polymarket.com/developers/RTDS/RTDS-crypto-prices)** - Real-time cryptocurrency price updates
|
||||
2. **[Comments](https://docs.polymarket.com/developers/RTDS/RTDS-comments)** - Comment-related events including reactions
|
||||
|
||||
All messages received from the WebSocket follow this structure:
|
||||
|
||||
|
|
|
|||
|
|
@ -113,7 +113,7 @@ Instructions for placing multiple orders(Batch)
|
|||
|
||||
<Tip> This endpoint requires a L2 Header </Tip>
|
||||
|
||||
Polymarket’s CLOB supports batch orders, allowing you to place up to `15` orders in a single request. Before using this feature, make sure you're comfortable placing a single order first. You can find the documentation for that [here.](/developers/CLOB/orders/create-order)
|
||||
Polymarket’s CLOB supports batch orders, allowing you to place up to `15` orders in a single request. Before using this feature, make sure you're comfortable placing a single order first. You can find the documentation for that [here.](https://docs.polymarket.com/developers/CLOB/orders/create-order)
|
||||
|
||||
`POST /<clob-endpoint>/orders`
|
||||
|
||||
|
|
@ -348,12 +348,12 @@ Welcome to the Polymarket Changelog. Here you will find any important changes to
|
|||
* **Comment Streaming**: Real-time updates for comment events including new comments, replies, and reactions
|
||||
* **Dynamic Subscriptions**: Add, remove, and modify subscriptions without reconnecting
|
||||
* **TypeScript Client**: Official TypeScript client available at [real-time-data-client](https://github.com/Polymarket/real-time-data-client)
|
||||
For complete documentation, see [RTDS Overview](/developers/RTDS/RTDS-overview).
|
||||
For complete documentation, see [RTDS Overview](https://docs.polymarket.com/developers/RTDS/RTDS-overview).
|
||||
</Update>
|
||||
|
||||
<Update label="September 15, 2025" description="WSS price_change event update">
|
||||
* There has been a significant change to the structure of the price change message. This update will be applied at 11PM UTC September 15, 2025. We apologize for the short notice
|
||||
* Please see the [migration guide](/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
* Please see the [migration guide](https://docs.polymarket.com/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
</Update>
|
||||
|
||||
<Update label="August 26, 2025" description="Updated /trades and /activity endpoints">
|
||||
|
|
@ -363,7 +363,7 @@ Welcome to the Polymarket Changelog. Here you will find any important changes to
|
|||
</Update>
|
||||
|
||||
<Update label="August 21, 2025" description="Batch Orders Increase">
|
||||
* The batch orders limit has been increased from from 5 -> 15. Read more about the batch orders functionality [here](/developers/CLOB/orders/create-order-batch).
|
||||
* The batch orders limit has been increased from from 5 -> 15. Read more about the batch orders functionality [here](https://docs.polymarket.com/developers/CLOB/orders/create-order-batch).
|
||||
</Update>
|
||||
|
||||
<Update label="July 23, 2025" description="Get Book(s) update">
|
||||
|
|
@ -380,11 +380,11 @@ Welcome to the Polymarket Changelog. Here you will find any important changes to
|
|||
</Update>
|
||||
|
||||
<Update label="June 3, 2025" description="New Batch Orders Endpoint">
|
||||
* We’re excited to roll out a highly requested feature: **order batching**. With this new endpoint, users can now submit up to five trades in a single request. To help you get started, we’ve included sample code demonstrating how to use it. Please see [Place Multiple Orders (Batching)](/developers/CLOB/orders/create-order-batch) for more details.
|
||||
* We’re excited to roll out a highly requested feature: **order batching**. With this new endpoint, users can now submit up to five trades in a single request. To help you get started, we’ve included sample code demonstrating how to use it. Please see [Place Multiple Orders (Batching)](https://docs.polymarket.com/developers/CLOB/orders/create-order-batch) for more details.
|
||||
</Update>
|
||||
|
||||
<Update label="June 3, 2025" description="Change to /data/trades">
|
||||
* We're adding a new `side` field to the `MakerOrder` portion of the trade object. This field will indicate whether the maker order is a `buy` or `sell`, helping to clarify trade events where the maker side was previously ambiguous. For more details, refer to the MakerOrder object on the [Get Trades](/developers/CLOB/trades/trades) page.
|
||||
* We're adding a new `side` field to the `MakerOrder` portion of the trade object. This field will indicate whether the maker order is a `buy` or `sell`, helping to clarify trade events where the maker side was previously ambiguous. For more details, refer to the MakerOrder object on the [Get Trades](https://docs.polymarket.com/developers/CLOB/trades/trades) page.
|
||||
</Update>
|
||||
|
||||
<Update label="May 28, 2025" description="Websocket Changes">
|
||||
|
|
@ -466,14 +466,14 @@ After installing one of those you will be able to run the below code. Take the t
|
|||
#### In addition to detailed comments in the code snippet, here are some more tips to help you get started.
|
||||
|
||||
* See the Python example for details on the proper way to initialize a Py-Clob-Client depending on your wallet type. Three exhaustive examples are given. If using a MetaMask wallet or EOA please see the resources [here](https://github.com/Polymarket/py-clob-client?tab=readme-ov-file), for instructions on setting allowances.
|
||||
* When buying into a market you purchase a "Token" that token represents either a Yes or No outcome of the event. To easily get required token pairs for a given event we have provided an interactive endpoint [here](/developers/gamma-markets-api/get-markets).
|
||||
* When buying into a market you purchase a "Token" that token represents either a Yes or No outcome of the event. To easily get required token pairs for a given event we have provided an interactive endpoint [here](https://docs.polymarket.com/developers/gamma-markets-api/get-markets).
|
||||
* Common pitfalls:
|
||||
* Negrisk Markets require an additional flag in the OrderArgs `negrisk=False `
|
||||
* `invalid signature` error, likely due to one of the following.
|
||||
* Incorrect Funder and or Private Key
|
||||
* Incorrect NegRisk flag in your order arguments
|
||||
* `not enough balance / allowance`.
|
||||
* Not enough USDC to perform the trade. See the formula at the bottom of [this](/developers/CLOB/orders/orders) page for details.
|
||||
* Not enough USDC to perform the trade. See the formula at the bottom of [this](https://docs.polymarket.com/developers/CLOB/orders/orders) page for details.
|
||||
* If using Metamask / WEB3 wallet go [here](https://github.com/Polymarket/py-clob-client?tab=readme-ov-file), for instructions on setting allowances.
|
||||
|
||||
**Examples:**
|
||||
|
|
@ -635,7 +635,7 @@ Where a `OrderSummary` object is of the form:
|
|||
## price\_change Message
|
||||
|
||||
<div style={{backgroundColor: '#fff3cd', border: '1px solid #ffeaa7', borderRadius: '4px', padding: '12px', marginBottom: '16px'}}>
|
||||
<strong>⚠️ Breaking Change Notice:</strong> The price\_change message schema will be updated on September 15, 2025 at 11 PM UTC. Please see the [migration guide](/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
<strong>⚠️ Breaking Change Notice:</strong> The price\_change message schema will be updated on September 15, 2025 at 11 PM UTC. Please see the [migration guide](https://docs.polymarket.com/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
</div>
|
||||
|
||||
* A new order is placed
|
||||
|
|
@ -685,7 +685,7 @@ Example 1 (unknown):
|
|||
## price\_change Message
|
||||
|
||||
<div style={{backgroundColor: '#fff3cd', border: '1px solid #ffeaa7', borderRadius: '4px', padding: '12px', marginBottom: '16px'}}>
|
||||
<strong>⚠️ Breaking Change Notice:</strong> The price\_change message schema will be updated on September 15, 2025 at 11 PM UTC. Please see the [migration guide](/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
<strong>⚠️ Breaking Change Notice:</strong> The price\_change message schema will be updated on September 15, 2025 at 11 PM UTC. Please see the [migration guide](https://docs.polymarket.com/developers/CLOB/websocket/market-channel-migration-guide) for details.
|
||||
</div>
|
||||
|
||||
Emitted When:
|
||||
|
|
|
|||
|
|
@ -0,0 +1,8 @@
|
|||
# TimescaleDB Docs Contributing(外链)
|
||||
|
||||
本仓库未在 `assets/skills/timescaledb/references/` 内维护完整贡献指南原文。
|
||||
|
||||
请参考官方贡献指南(Docs 仓库):
|
||||
|
||||
- https://github.com/timescale/docs/blob/latest/CONTRIBUTING.md
|
||||
|
||||
|
|
@ -0,0 +1,14 @@
|
|||
# twscrape:账号管理(参考)
|
||||
|
||||
本文件为 `twscrape` 的账号管理参考页。
|
||||
|
||||
## 推荐阅读顺序
|
||||
|
||||
1. `assets/skills/twscrape/references/installation.md`
|
||||
2. `assets/skills/twscrape/SKILL.md`(包含账号池、登录、轮换等完整示例)
|
||||
3. `assets/skills/twscrape/references/examples.md`
|
||||
|
||||
## 入口
|
||||
|
||||
- 账号添加/登录的核心示例:`assets/skills/twscrape/SKILL.md`
|
||||
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
# twscrape:API 方法(参考)
|
||||
|
||||
本文件为 `twscrape` 的 API 方法参考页(仓库内精简版)。
|
||||
|
||||
## 入口
|
||||
|
||||
- 完整方法速查与示例:`assets/skills/twscrape/SKILL.md`
|
||||
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
# twscrape:CLI 用法(参考)
|
||||
|
||||
本文件为 `twscrape` 的命令行使用参考页。
|
||||
|
||||
## 入口
|
||||
|
||||
- CLI 相关命令示例:`assets/skills/twscrape/SKILL.md`
|
||||
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
# twscrape:代理配置(参考)
|
||||
|
||||
本文件为 `twscrape` 的代理配置参考页。
|
||||
|
||||
## 入口
|
||||
|
||||
- 代理参数示例:`assets/skills/twscrape/SKILL.md`
|
||||
|
||||
|
|
@ -0,0 +1 @@
|
|||
占位,这里即将存放对于指定任务中合适的成熟工具的使用方法,提供给 agent 进行操作
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue