Comparison
PNTR vs webhook.site
Both capture inbound HTTP requests so you can inspect the method, headers, and body. The difference is what the URL is: webhook.site issues a random UUID, while PNTR gives you a hostname you pick and keep, with DNS records and a catch-all inbox on that same name. webhook.site is the more mature product and does several things PNTR does not — those are listed below rather than left out.
PNTR compared with webhook.site
| Feature | PNTR | webhook.site |
|---|---|---|
| Endpoint URL | A name you choose — yourname.pntr.dev — kept while the account is active | A random UUID, e.g. webhook.site/8f3c…, not chosen by you |
| Free retention | 48 hours | 7 days |
| Free request volume | 1,000 stored per subdomain, 500/hour ingest | 500 requests total per URL, for the life of that URL |
| Custom response (status code, content type, body) | Included on the free tier | Supported, with rule-based Custom Actions on paid plans |
| Rule-based dynamic responses | Not supported — one static response per subdomain | Custom Actions can branch on the request, on paid plans |
| DNS records on the same name | A, AAAA, CNAME, TXT, MX | None — it is not a DNS product |
| Catch-all email inbox | Included on the subdomain | A temporary address is included |
| MCP server for Claude / Cursor | Yes — listed in the official MCP registry as dev.pntr/pntr | None published |
| Cheapest paid plan | $5/month or $48/year | $9/month or $90/year (Basic) |
| Longest retention available | 90 days on Premium | 365 days on higher plans |
| Use without signing up | Yes — guests get one subdomain | Yes — a URL is generated on page load |
webhook.site pricing and limits last checked on . Check their site for current terms.
Choose PNTR when
- You want a URL you can read out loud and reuse across projects, instead of pasting a fresh UUID into a provider's dashboard each time.
- You want to set the response status and body without paying — returning a 500 to exercise a sender's retry logic is on PNTR's free tier.
- You need DNS records and webhook capture on the same hostname — pointing a CNAME at your app and catching callbacks on the same name.
- You want to inspect captured requests from Claude or Cursor over MCP rather than opening a browser tab.
- You are testing a signup or OTP flow that sends both a webhook and an email, and want both on one name.
- Your paid budget is $5/month rather than $9/month.
Choose webhook.site when
- You need the response to vary by request — matching on a path or payload and answering differently. PNTR serves one static response per subdomain; webhook.site's Custom Actions can branch.
- You need request history older than 90 days. webhook.site sells up to 365 days; PNTR stops at 90.
- You want more than 48 hours of retention without paying. webhook.site's free tier keeps requests for 7 days.
- You want a service with a longer operating history and much larger scale — webhook.site reports 400,000 monthly active users and around 700 million requests per day.
- You need SAML SSO or a shared team workspace. PNTR has no team accounts.
Questions
- Is PNTR a drop-in replacement for webhook.site?
- For inspecting inbound requests and controlling what comes back, yes — you get the method, headers, and body of each delivery, and you can set the response status, content type, and body. It is not a replacement if you rely on Custom Actions to vary the response per request, since PNTR serves one static response per subdomain.
- Does the PNTR URL expire?
- The subdomain does not expire while the account is active — that is the main structural difference. Individual captured requests are purged after 48 hours on the free tier and 90 days on Premium.
- What happens when webhook.site's free request limit is reached?
- A free webhook.site URL accepts 500 requests over its lifetime, and deleting requests does not reset that counter — you create a new URL. PNTR caps stored requests at 1,000 per subdomain and rolls the oldest off, so the same hostname keeps working.
- Can I use both?
- Yes, and it is a reasonable setup. Use webhook.site when the response has to vary per request, and a PNTR subdomain when you want a stable hostname that also carries DNS and email.
- Do I need an account to try PNTR?
- No. Guests get one subdomain with request capture. Signing in with GitHub raises that to three.