{"id":3391,"date":"2026-03-30T11:24:57","date_gmt":"2026-03-30T15:24:57","guid":{"rendered":"https:\/\/freerdps.com\/blog\/?p=3391"},"modified":"2026-03-30T11:25:11","modified_gmt":"2026-03-30T15:25:11","slug":"run-telegram-trading-bots-on-one-rdp","status":"publish","type":"post","link":"https:\/\/freerdps.com\/blog\/run-telegram-trading-bots-on-one-rdp\/","title":{"rendered":"How to Run 100+ Telegram Trading Bots on ONE RDP Without Crashing"},"content":{"rendered":"\n<p>Imagine this nightmare: you finally have 87 Telegram trading bots running, each auto-buying dips on different pairs\u2026 and suddenly your RDP screen turns into a slideshow. Windows screams about low memory, half the bots freeze, and you lose 3 hours of trading while rebooting everything. Sound familiar?<\/p>\n\n\n\n<p>I\u2019ve been there. Back when I was scaling my first grid of crypto snipers, I thought \u201cjust open more windows\u201d was the move. Spoiler: it\u2019s not. Double-clicking 100 .exe files will murder your RDP with RAM spikes, GDI handle limits, and brutal CPU throttling.<\/p>\n\n\n\n<p>The real fix? Ditch the GUI-centric mindset completely and go full process-centric architecture. Run everything headless, isolate each bot, and manage them like a pro orchestra conductor from one clean dashboard. That\u2019s exactly what this monster guide delivers, beginner-friendly, real-talk steps I wish I had when I started.<\/p>\n\n\n\n<p>Whether you\u2019re a solo trader tired of babysitting 20 bots or a degen scaling to 200+, you\u2019re about to learn the exact setup that lets one single RDP (yes, even on a <a href=\"https:\/\/freerdps.com\/blog\/best-openclaw-vps-hosting\/\">$40\/month VPS<\/a>) handle 100+ Telegram trading bots 24\/7 without breaking a sweat.<\/p>\n\n\n\n<p><strong>Let\u2019s kill the chaos together.<\/strong><\/p>\n\n\n\n<div id=\"affiliate-style-95c0f6c3-a9d0-42e6-a197-74f029183d49\" class=\"wp-block-affiliate-booster-ab-tableof-content affiliate-toc-align-left affiliate-toc-columns-1 affiliate-toc-collapse affiliate-block-95c0f6c3\" data-scroll=\"true\" data-offset=\"30\" data-delay=\"800\"><div class=\"affiliate-toc-inner affiliate-toc-islist affiliate-toc-align-\"><div class=\"affiliate-toc-wrap\"><div class=\"affiliate-toc-title-wrap\"><div class=\"affiliate-toc-title\">Table Of Contents<\/div><div class=\"affiliate-toc-collapsible-wrap affiliate-table-of-contents-toggle affiliate-toc-collapsed\"><a class=\"affiliate-collapsible-text affiliate-toc-close-text\" href=\"javascript:;\">Hide<\/a><a class=\"affiliate-collapsible-text affiliate-toc-open-text\" href=\"javascript:;\">Show<\/a><\/div><\/div><div class=\"affiliate-toc-list-wrap\"><ul class=\"affiliate-toc-list desktop1 tablet1 mobile1\"><li><a href=\"#1--choosing-the-right-hardware-minimum-specs-for-100-bots-\">Choosing the Right Hardware: Minimum Specs for 100+ Bots<\/a><ul class=\"affiliate-toc-list\"><li><a href=\"#2--the-silent-killer-why-standard-rdp-sessions-fail-at-scale-\">The &#8220;Silent Killer&#8221;: Why Standard RDP Sessions Fail at Scale<\/a><\/li><\/ul><\/li><li><a href=\"#3--architecture-strategy-choosing-your-management-engine-\">Architecture Strategy: Choosing Your Management Engine<\/a><ul class=\"affiliate-toc-list\"><li><a href=\"#4--method-a-the-pm2-approach-best-for-nodepython-\">Method A: The PM2 Approach (Best for Node\/Python)<\/a><\/li><li><a href=\"#5--method-b-docker-containers-best-for-isolation-\">Method B: Docker Containers (Best for Isolation)<\/a><\/li><li><a href=\"#6--method-c-the-master-slave-bot-controller-\">Method C: The &#8220;Master-Slave&#8221; Bot Controller<\/a><\/li><\/ul><\/li><li><a href=\"#7--step-by-step-guide-setting-up-the-infrastructure-\">Step-by-Step Guide: Setting Up the Infrastructure<\/a><ul class=\"affiliate-toc-list\"><li><a href=\"#8--step-1-rdp-optimization-\">Step 1: RDP Optimization<\/a><\/li><li><a href=\"#9--step-2-proxy-integration-\">Step 2: Proxy Integration<\/a><\/li><li><a href=\"#10--step-3-centralized-logging-\">Step 3: Centralized Logging<\/a><\/li><li><a href=\"#11--step-4-automated-restarts-\">Step 4: Automated Restarts<\/a><\/li><\/ul><\/li><li><a href=\"#12--centralized-monitoring-how-to-watch-100-bots-at-once-\">Centralized Monitoring: How to Watch 100 Bots at Once<\/a><\/li><li><a href=\"#13--security-best-practices-for-high-volume-rdps-\">Security Best Practices for High-Volume RDPs<\/a><\/li><li><a href=\"#14--troubleshooting-common-scaling-issues-\">Troubleshooting Common Scaling Issues<\/a><\/li><li><a href=\"#15--conclusion-from-chaos-to-247-automation-\">Conclusion: From Chaos to 24\/7 Automation<\/a><\/li><\/ul><\/div><\/div><\/div><\/div>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"572\" height=\"385\" src=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-4.jpg\" alt=\"\" class=\"wp-image-3392\" srcset=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-4.jpg 572w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-4-300x202.jpg 300w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-4-400x269.jpg 400w\" sizes=\"auto, (max-width: 572px) 100vw, 572px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"1--choosing-the-right-hardware-minimum-specs-for-100-bots-\"><strong>Choosing the Right Hardware: Minimum Specs for 100+ Bots<\/strong><\/h2>\n\n\n\n<p>Let\u2019s do the \u201cResource Math\u201d right now so you don\u2019t waste money on the wrong box.<\/p>\n\n\n\n<p>Here\u2019s a quick table I made from real tests (Python Telethon bots vs Node.js Telegraf vs compiled C++):<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Bot Type<\/strong><\/td><td><strong>RAM per bot<\/strong><\/td><td><strong>CPU per bot (idle\/spike)<\/strong><\/td><td><strong>Max bots on 32GB\/8-core VPS<\/strong><\/td><\/tr><tr><td>Python (Telethon)<\/td><td>80-120MB<\/td><td>2%\/12%<\/td><td>180+<\/td><\/tr><tr><td>Node.js<\/td><td>60-90MB<\/td><td>1%\/8%<\/td><td>220+<\/td><\/tr><tr><td>Compiled C++<\/td><td>35-55MB<\/td><td>0.5%\/5%<\/td><td>350+<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>You need at least 16GB RAM (32GB is the sweet spot) and NVMe SSDs because 100+ bots mean constant I\/O streams, logs, WebSocket pings, screenshot grabs if you keep any GUI. <a href=\"https:\/\/freerdps.com\/blog\/best-free-windows-vps\/\">Regular HDDs will choke hard<\/a>.<\/p>\n\n\n\n<p>For the operating system? Windows Server 2022 wins for pure performance and higher process limits. Windows 10\/11 works fine for compatibility with some bot builders, but Server 2022 lets you push way more background sessions before things get weird.<\/p>\n\n\n\n<p>I run my main 140-bot farm on a <a href=\"https:\/\/freerdps.com\/blog\/best-netherlands-vps-hosting\/\">32GB \/ 8 vCPU \/ NVMe VPS<\/a> from a budget provider. <\/p>\n\n\n\n<p>Monthly cost? $38.<\/p>\n\n\n\n<p><strong>That\u2019s it. No fancy <a href=\"https:\/\/freerdps.com\/blog\/best-dedicated-servers-miami\/\">dedicated server<\/a> nonsense.<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"572\" height=\"337\" src=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-5.jpg\" alt=\"\" class=\"wp-image-3393\" srcset=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-5.jpg 572w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-5-300x177.jpg 300w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-5-400x236.jpg 400w\" sizes=\"auto, (max-width: 572px) 100vw, 572px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"2--the-silent-killer-why-standard-rdp-sessions-fail-at-scale-\"><strong>The &#8220;Silent Killer&#8221;: Why Standard RDP Sessions Fail at Scale<\/strong><\/h3>\n\n\n\n<p>Windows has this hidden GDI Objects Limit \u2014 basically it only lets you render about 10,000 \u201cwindows\u201d or graphical objects total. Open 100 Telegram windows? Boom, new ones stop appearing and your bots look dead.<\/p>\n\n\n\n<p>Desktop Heap Issues are the next killer. The registry default is tiny, so background processes fight for memory space and randomly crash. One quick registry tweak fixes 80% of mysterious \u201cbot stopped responding\u201d errors.<\/p>\n\n\n\n<p>Network Congestion hits when 100+ WebSocket connections hammer the same IP. Telegram starts throwing FloodWait errors left and right and eventually IP-bans you. <\/p>\n\n\n\n<p>The fix is simple: rotate proxies every 5-10 bots.<\/p>\n\n\n\n<p>I learned this the hard way during a 2025 bull run, lost 40 bots in 20 minutes because I ignored the silent killers. Don\u2019t be me.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"3--architecture-strategy-choosing-your-management-engine-\"><strong>Architecture Strategy: Choosing Your Management Engine<\/strong><\/h2>\n\n\n\n<p>You\u2019ve got three killer ways to run this. Pick based on your comfort level.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"4--method-a-the-pm2-approach-best-for-nodepython-\"><strong>Method A: The PM2 Approach (Best for Node\/Python)<\/strong><\/h3>\n\n\n\n<p>PM2 is a process manager that keeps your bots alive forever. One command and it auto-restarts crashed bots, shows live logs, and scales like crazy.<\/p>\n\n\n\n<p>Command example:<\/p>\n\n\n\n<p>pm2 start bot.js &#8211;name &#8220;Bot_001&#8221; &#8211;watch<\/p>\n\n\n\n<p>Then pm2 list shows you 100+ bots in one terminal. Super clean for beginners.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"5--method-b-docker-containers-best-for-isolation-\"><strong>Method B: Docker Containers (Best for Isolation)<\/strong><\/h3>\n\n\n\n<p>This is my personal favorite. Each bot lives in its own lightweight container with a strict 100MB RAM cap. If one bot leaks memory, the others don\u2019t care.<\/p>\n\n\n\n<p>You run them headless (no GUI at all) so Windows doesn\u2019t waste resources drawing pretty windows. Benefits? Resource capping, easy updates, and you can spin up 50 new bots in 30 seconds.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"573\" height=\"430\" src=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-6.jpg\" alt=\"\" class=\"wp-image-3394\" srcset=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-6.jpg 573w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-6-300x225.jpg 300w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-6-400x300.jpg 400w\" sizes=\"auto, (max-width: 573px) 100vw, 573px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"6--method-c-the-master-slave-bot-controller-\"><strong>Method C: The &#8220;Master-Slave&#8221; Bot Controller<\/strong><\/h3>\n\n\n\n<p>Build one \u201cMaster\u201d bot that talks to the other 99 via internal Redis or a tiny API. Want to stop all bots? Just send one command from the master. Perfect for emergency pauses during flash crashes.<\/p>\n\n\n\n<p>I combine B and C \u2014 <a href=\"https:\/\/freerdps.com\/blog\/cheap-docker-hosting\/\">Docker<\/a> + Master-Slave \u2014 and it feels like cheating.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"7--step-by-step-guide-setting-up-the-infrastructure-\"><strong>Step-by-Step Guide: Setting Up the Infrastructure<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"8--step-1-rdp-optimization-\"><strong>Step 1: RDP Optimization<\/strong><\/h3>\n\n\n\n<p>First thing after logging in: disable all visual effects, animations, background apps, and Windows Update. Right-click This PC \u2192 Properties \u2192 Advanced \u2192 Performance Settings \u2192 Adjust for best performance. Boom, instant 30% less RAM usage.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"9--step-2-proxy-integration-\"><strong>Step 2: Proxy Integration<\/strong><\/h3>\n\n\n\n<p>Never run more than 8-10 bots on the same IP. <a href=\"https:\/\/freerdps.com\/blog\/best-cheap-rotating-proxies\/\">I use residential proxies rotated automatically<\/a>. One line in your bot code switches proxy every 30 minutes. Telegram almost never bans when you do this right.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"10--step-3-centralized-logging-\"><strong>Step 3: Centralized Logging<\/strong><\/h3>\n\n\n\n<p>Stop opening 100 log files. Install a simple ELK Stack (or even just Logtail) and everything funnels into one beautiful dashboard. Spot a broken bot in 3 seconds instead of hunting.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"573\" height=\"332\" src=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-8.jpg\" alt=\"\" class=\"wp-image-3396\" srcset=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-8.jpg 573w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-8-300x174.jpg 300w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-8-400x232.jpg 400w\" sizes=\"auto, (max-width: 573px) 100vw, 573px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"11--step-4-automated-restarts-\"><strong>Step 4: Automated Restarts<\/strong><\/h3>\n\n\n\n<p>Write a tiny Watchdog PowerShell script that pings your bots every 60 seconds. If no heartbeat? Auto-restart that container. Set it to run on login and you\u2019re golden.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"12--centralized-monitoring-how-to-watch-100-bots-at-once-\"><strong>Centralized Monitoring: How to Watch 100 Bots at Once<\/strong><\/h2>\n\n\n\n<p>Forget switching between 100 windows. Build (or steal) a Grafana dashboard that shows live P&amp;L, uptime, error count, and balance for every single bot.<\/p>\n\n\n\n<p>I have one big screen with a custom web UI (FreqUI style) that refreshes every 5 seconds. Green = printing money, red = needs attention.<\/p>\n\n\n\n<p>Even better? Create a private Telegram \u201cCommand Center\u201d group. Your master bot listens for \/status, \/stopall, \/restart_042, etc. Type once and all 140 bots obey instantly.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"573\" height=\"301\" src=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-7.jpg\" alt=\"\" class=\"wp-image-3395\" srcset=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-7.jpg 573w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-7-300x158.jpg 300w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-7-400x210.jpg 400w\" sizes=\"auto, (max-width: 573px) 100vw, 573px\" \/><\/figure>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"439\" src=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-9.jpg\" alt=\"\" class=\"wp-image-3397\" srcset=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-9.jpg 533w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-9-300x247.jpg 300w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-9-400x329.jpg 400w\" sizes=\"auto, (max-width: 533px) 100vw, 533px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"13--security-best-practices-for-high-volume-rdps-\"><strong>Security Best Practices for High-Volume RDPs<\/strong><\/h2>\n\n\n\n<p>Never store API keys or .env files in plain text. Use Windows Credential Manager or encrypt everything with a simple script.<\/p>\n\n\n\n<p>Change the default RDP port from 3389 to something random like 54231. Enable 2FA with Duo or Microsoft Authenticator. Whitelist only your home IP (or use WireGuard VPN).<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"573\" height=\"322\" src=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-10.jpg\" alt=\"\" class=\"wp-image-3398\" srcset=\"https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-10.jpg 573w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-10-300x169.jpg 300w, https:\/\/freerdps.com\/blog\/wp-content\/uploads\/2026\/02\/image-10-400x225.jpg 400w\" sizes=\"auto, (max-width: 573px) 100vw, 573px\" \/><\/figure>\n\n\n\n<p>One breach and you lose everything \u2014 treat your trading RDP like a bank vault.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"14--troubleshooting-common-scaling-issues-\"><strong>Troubleshooting Common Scaling Issues<\/strong><\/h2>\n\n\n\n<p>High Latency\/Ping? <a href=\"https:\/\/freerdps.com\/blog\/best-free-rdp-for-mining\/\">Choose the RDP location closest<\/a> to your exchange (Tokyo for ByBit, London for Binance, Singapore for many others). 20ms difference = thousands in extra profit.<\/p>\n\n\n\n<p>FloodWait Errors when 100 bots alert at once? Add staggered delays (random 200-800ms) in your code. Simple but saves lives.<\/p>\n\n\n\n<p>Memory Leaks? Schedule a weekly \u201cRDP Purge\u201d script that restarts all containers every Sunday 4 AM. Fresh and clean.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"15--conclusion-from-chaos-to-247-automation-\"><strong>Conclusion: From Chaos to 24\/7 Automation<\/strong><\/h2>\n\n\n\n<p>You now have the complete playbook: right hardware, headless architecture, PM2 or <a href=\"https:\/\/freerdps.com\/blog\/how-to-update-n8n-in-docker\/\">Docker<\/a>, centralized monitoring, and iron-clad security. The old GUI nightmare is dead. One single RDP can genuinely run 100+ Telegram trading bots profitably 24\/7.<\/p>\n\n\n\n<p>Start small, get 10 bots rock-solid using the Docker method above. Then scale to 50, then 100. You\u2019ll laugh at how easy it feels once the plumbing is right.<\/p>\n\n\n\n<p>I\u2019ve packaged all the scripts, Docker Compose files, PM2 templates, watchdog, and Grafana JSON dashboard into a free starter kit. Comment \u201cSEND KIT\u201d below or drop your email and I\u2019ll shoot it over instantly.<\/p>\n\n\n\n<p>You\u2019ve got the knowledge. Now go turn that single RDP into your personal money printer.<\/p>\n\n\n\n<p>From total chaos to peaceful 24\/7 automation, that\u2019s the real flex in 2026.<\/p>\n\n\n\n<p>Let me know in the comments: how many bots are you running right now? I\u2019ll reply with personalized tweaks for your setup. <\/p>\n\n\n\n<p>Let\u2019s scale together!<\/p>\n","protected":false},"excerpt":{"rendered":"Imagine this nightmare: you finally have 87 Telegram trading bots running, each auto-buying dips on different pairs\u2026 and&hellip;","protected":false},"author":1,"featured_media":3467,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"split","csco_page_load_nextpost":"","footnotes":""},"categories":[5],"tags":[],"class_list":{"0":"post-3391","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-guides","8":"cs-entry"},"_links":{"self":[{"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/posts\/3391","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/comments?post=3391"}],"version-history":[{"count":2,"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/posts\/3391\/revisions"}],"predecessor-version":[{"id":3468,"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/posts\/3391\/revisions\/3468"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/media\/3467"}],"wp:attachment":[{"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/media?parent=3391"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/categories?post=3391"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/freerdps.com\/blog\/wp-json\/wp\/v2\/tags?post=3391"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}