GET ipfs.io HTTP 200112 ms8.4 KB$0.000036 captured Aug 7, 2026
ipfs.io, as data
One API turns any ipfs.io page into markdown, structured JSON, its link graph or a screenshot, and crawls the whole site the same way. The panel shows the real response we captured.
- Render mode
- Plain HTTP, no browser needed
- Response
- HTTP 200 in 112 ms
- Page size
- 8.4 KB of markdown, 90 lines
- Fields
- Business Name, Address, Phone, Category and 1 more
- Captured
- Aug 7, 2026
Free balance on signup, no card. This ipfs.io page cost $0.000036 to fetch.
The ipfs.io/dweb.link public gateways are maintained by Interplanetary Shipyardon behalf of the IPFS Foundation. The funds are contributed by a range of donorswho wish to support digital public infrastructure.Join them, all contributions are welcome!What's the relationship between gateways and other IPFS instances?Running IPFS directly is more efficient, but not all users are able to do it today.Gateways are an interim solution. Longer term, the IPFS project aims to increase direct support foripfs:// in browsers and applications.There will always be a role for gateways, but we anticipate that role will shrink as directIPFS support becomes more prevalent.How does the gateway ensure whether the data they return matches the Content ID (CID) in the request? Can I access the gateways in a trustless way?The ipfs.io gateway is one of the first that verifies the data against the requested CID before beingreturned to users. We do however recommend that clients implement their own verification as that is afoundational part of IPFS. To simplify this, gateways supportthat enable verifiable retrieval. What Spider does on ipfs.io
Same key, five endpoints. The numbers under a cell were measured on this page.
Page to markdown
Clean text for RAG and LLM context, boilerplate removed. The lane that runs without a key.
112 ms · $0.000036Page to JSON
Spider reads the page and names the fields. Pass your own schema when you need exact keys.
Rendered capture
Real Chromium, full-page PNG. The same call also returns the rendered HTML.
The call behind the panel
This request produced the response above. Paste it with your key and you get the same bytes.
curl -X POST https://api.spider.cloud/scrape \
-H "Authorization: Bearer $SPIDER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://ipfs.io/", "return_format": "markdown"}' from spider import Spider
app = Spider()
params = {"return_format": "markdown"}
page = app.scrape_url("https://ipfs.io/", params=params)
print(page[0]["content"]) import { Spider } from "@spider-cloud/spider-client";
const app = new Spider();
const [page] = await app.scrapeUrl("https://ipfs.io/", {
return_format: "markdown",
});
console.log(page.content); What ipfs.io costs
Multiplied from the measured 8.4 KB page. Estimates round to the cent.
1 GB of transfer costs $1, plus $0.001 per CPU minute, and failed requests cost $0. Crawling daily? The Unlimited plan is a flat monthly rate.
Point this at the rest of ipfs.io.
The capture above took 112 ms and cost $0.000036. The same call takes any URL on ipfs.io.