Skip to main content

Confirm

Are you sure?

Changelog · July 2, 2026

Request caching with max_age

Ask for the same page twice and pay once.

By · Last updated: July 2026

TL;DR

Every successful result is now stored, and an identical request inside your freshness window is answered from it instead of visiting the page again. max_age sets that window — "2 hours", "3 days" or seconds — defaulting to 7 days and capped at 30. Cache hits are free and are never refused for quota; max_age: 0 always fetches fresh.

Free plan, no credit card. 1,000 credits a month.

Identical means the same operation, the same normalized URL and the same options. A hit is served in milliseconds and spends nothing. max_age: 0 skips the lookup and fetches the page again, and still stores the fresh result for later requests.

Accept a result up to 2 hours old
curl -X POST https://urlpipe.dev/markdown \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com", "max_age": "2 hours", "sync": true}'

Stored results are kept for 30 days and belong to the organization that asked for them.

FAQ

Frequently asked questions

What is the default max_age?
7 days. It can be set anywhere from 0 to 30 days.
Do cache hits cost credits?
No. A cache hit is free and is never refused for quota.
How do I force a fresh fetch?
Send max_age: 0. The fresh result is stored for later requests.

Try it on the free plan.

Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.