OPEN PLATFORM · API V1
The open platform turns published security research into a stable, read-only API. Every account gets its own API key: one Bearer header is all it takes to search, page through results, and fetch Markdown bodies by slug.
Create one under Settings · Open Platform. The plaintext is shown once, so store it in a password manager or deployment environment right away.
Add Authorization: Bearer YOUR_API_KEY to each request; X-API-Key also works. Never ship the key in frontend code or a public repository.
Search for a slug, then fetch the body by slug. Cursor paging and stable fields make it easy to hand straight to an AI tool.
Copy either snippet and swap in your own key. Every response uses the code / data / msg envelope; code 0 means success.
# 1. 搜索文章（返回摘要与 slug）
curl 'https://decrypthub.cn/open/v1/articles?q=Frida&limit=5' \
-H 'Authorization: Bearer YOUR_API_KEY'
# 2. 按 slug 读取正文（Markdown）
curl 'https://decrypthub.cn/open/v1/articles/frida-hook-guide' \
-H 'Authorization: Bearer YOUR_API_KEY'import requests
BASE = "https://decrypthub.cn/open/v1"
HEADERS = {"Authorization": "Bearer YOUR_API_KEY"}
hits = requests.get(
f"{BASE}/articles",
params={"q": "Frida", "limit": 5},
headers=HEADERS,
timeout=10,
).json()["data"]
for item in hits["items"]:
print(item["slug"], "—", item["title"])
article = requests.get(
f"{BASE}/articles/{hits['items'][0]['slug']}",
headers=HEADERS,
timeout=10,
).json()["data"]
print(article["contentMd"])Replace YOUR_API_KEY with a key created on the settings page.
All read-only GETs over published articles. Page size defaults to 10 and caps at 50.
/open/v1/articlesArticle list. Supports q / tag / category / author / sort / since / until / cursor / page / includeContent./open/v1/articles/{slug}Fetch one published article by slug, including its Markdown body./open/v1/searchFull-text search (q required) across titles, excerpts and bodies./open/v1/categoriesCategories with their published article counts./open/v1/tagsPopular tags with usage counts./open/v1/meKey owner, scopes, rate limit and last use./open/v1/openapi.jsonOpenAPI 3.1 document, public and ready to import into AI tools.AI · TOOLS
The API is built for tool calls: JSON, Bearer auth, stable slugs, Markdown bodies. Paste the brief below into your AI assistant along with your key and it knows what to do.
You can search DecryptHub security research through its open platform.
Base URL: https://decrypthub.cn/open/v1
Auth: send Authorization: Bearer YOUR_API_KEY on every request
Endpoints:
- GET https://decrypthub.cn/open/v1/search?q=TERMS full-text search (returns excerpts and slugs)
- GET https://decrypthub.cn/open/v1/articles?limit=10&includeContent=1 latest articles
- GET https://decrypthub.cn/open/v1/articles/ARTICLE_SLUG read the Markdown body
- GET https://decrypthub.cn/open/v1/categories category list
- GET https://decrypthub.cn/open/v1/tags tag list
OpenAPI document: https://decrypthub.cn/open/v1/openapi.json
Responses use the code / data / msg envelope; code 0 means success. Search first, then read by slug, and cite the article title and url in your answer.Authorization: Bearer YOUR_API_KEY or X-API-Key: YOUR_API_KEY. Keys in URL parameters are not supported — those end up in logs and browser history.
120 requests per minute per key. Over the limit returns 429 with Retry-After in seconds.
Published, non-deleted articles only. Drafts, pending reviews and write operations never appear on the open API.
Only a SHA-256 digest is stored. If a key may have leaked, revoke it on the settings page and create a new one; revocation takes effect immediately.
Sign in, create your first key and send a request in about two minutes.