# Posting explains from tools (and not web browsers)

DevFeed: [Posting explains from tools (and not web browsers)](<https://devfeed.tech/articles/posting-explains-from-tools-and-not-web-browsers-33690.md>)

Original publisher: [Read original article](<https://www.depesz.com/2026/06/25/posting-explains-from-tools-and-not-web-browsers/>)

Author: depesz

Published: 2026-06-25T14:56:17Z

Content type: tutorial

Language: en

Sources: [select \* from depesz;](<https://devfeed.tech/sources/select-from-depesz.md>)

Topics: [cURL](<https://devfeed.tech/topics/curl.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Website](<https://devfeed.tech/topics/website.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [cli](<https://devfeed.tech/tags/cli.md>), [curl](<https://devfeed.tech/tags/curl.md>), [data](<https://devfeed.tech/tags/data.md>), [explain-depesz-com](<https://devfeed.tech/tags/explain-depesz-com.md>), [json](<https://devfeed.tech/tags/json.md>), [tools](<https://devfeed.tech/tags/tools.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

## AI overview

This article explains how to post execution plans to explain.depesz.com using a tool such as curl and obtain JSON containing the information needed to extract a delete_key for later deletion.

## Source excerpt

Some time ago (well, a month ago) someone called zam6ak reached to me and asked about extraction of delete_key from plans posted using tool, and not website. Specifically they were doing something like: curl --silent --include \ --request "POST" "https://explain.depesz.com/" \ --data-urlencode "title=sample" \ --data-urlencode "plan@sample-plan.txt" \ --data-urlencode "query@sample-query.sql" \ --data-urlencode "is_public=0" Which worked, and ... Continue reading "Posting explains from tools (and not web browsers)"