100 incoming requests per day across your guest scope
Up to 256 KiB per request
History available while the endpoint is active
Coming soon
Pro
For higher limits and automation when it becomes available.
$5 /month — planned price
When paid subscriptions launch: 14-day money-back guarantee on your first Pro purchase. Read the Refund Policy.
Planned limits
25 active endpoints
Intended to remain active while your Pro subscription is active
Requests kept for 30 days
Latest 5,000 requests stored per endpoint
25,000 incoming requests per day across your account
Up to 5 MiB per request
History available while the endpoint is active
Compare plans
Feature
Anonymous
Developer
Pro · Planned
Features and usage limits by plan
Feature
Anonymous
Developer
Pro · Planned
Endpoints & usage
Active endpoints
1
5
Planned · 25
Initial endpoint lifetime
1 day
7 days
Planned · Active while the Pro subscription is active
Extend an active endpoint
Not available
Available · 7 days; unlimited renewals
Planned
Request retention from receipt
1 day
7 days
Planned · 30 days
Stored request count
50 newest requests · New endpoints
500 newest requests · New endpoints
Planned · 5,000 / endpoint
Daily incoming quota
100 admitted arrivals / day · Shared creator-IP scope
2,500 admitted arrivals / day · Account total
Planned · 25,000 / account / day
Maximum raw incoming body
256 KiB
1 MiB
Planned · 5 MiB
Inspection & export
Method, path, query, headers & raw body
Available
Available
Planned
Live arrivals
Available
Available
Planned
Filter loaded requests
Available · Requests loaded in the browser
Available · Requests loaded in the browser
Planned
Copy request as cURL
Available
Available
Planned
JSON / NDJSON export
Available · Authorized, bounded export
Available · Authorized, bounded export
Planned
Built-in Send test request
Not available
Available
Planned
HTTP responses
Custom status
Available
Available
Planned
Custom response headers
Available · Allowed names only
Available · Allowed names only
Planned
Custom response body
Available
Available
Planned
Fixed response delay
Not available
Planned · Up to 5 seconds
Planned · Up to 30 seconds
Random response delay
Not available
Not available
Planned
Conditional response rules
Not available
Planned · 1 rule
Planned · 10 rules
Replay & forwarding
Outbound replay with editing
Not available
Available when enabled · Runtime, worker and source guards apply; 20/day is roadmap only
Planned · 500/day
Automatic forwarding
Not available
Planned · 1 rule, 500/month
Planned · 5 rules, 10,000/month
Response passthrough
Not available
Not available
Planned · No date
Integrations
API key management
Not available
Available · Create, replace and revoke
Planned
API-key-authorized application API
Not available
Planned · 500 calls/day target
Planned · 10,000 calls/day target
CLI
Not available
Planned · Basic integration
Planned · Advanced integration
MCP
Not available
Available · Account API key
Planned · Advanced integration
Local tunnel
Not available
Planned · 1 tunnel
Planned · 3 tunnels
Browser tools
JSON, Base64, URL & JWT tools
Available · Processed locally in your browser · No account required
Available · Processed locally in your browser · No account required
Available · Processed locally in your browser · No account required
How limits work
Endpoint lifetime: the address stops receiving and history access ends at expiry. Account renewals use max(current expiry, now + 7 days); they never revive expired addresses.
Retention: 1 day for Anonymous / 7 days for Developer from receipt, subject to earlier expiry, loss of access or count eviction. Stored requests: only the newest 50 / 500 for endpoints created after activation. Existing endpoints keep their uncapped count policy, including after claim.
Incoming quota: Active quotas count admitted arrivals before body read, not successful captures. Oversized bodies, disconnects, later failures and built-in tests consume a unit. Resets at midnight UTC. Guest endpoints share their creator-IP quota, including behind NAT; accounts share one aggregate quota. Clear, delete and new cookies do not reset it. Legacy guest attribution uses session or endpoint until expiry or claim.
Raw body bytes count even without Content-Length. Independent safety and edge limits apply; no throughput guarantee. Storage quota is unspecified. Read usage limits.
Free developer tools for everyone
Tool data processing runs locally in your browser, with no account required.
Yes. Anonymous and Developer are $0 with no credit card. Independent abuse restrictions apply; aggregate storage quota is unspecified.
Do I need an account?
No. Start with a guest session. A free Developer account gives you account ownership, more capacity and unlimited renewals of active endpoints. Keep guest management access private: a public receiving URL authorizes sending only.
How long can I access my requests?
New admissions retain requests for 1 day on Anonymous and 7 days on Developer. Requests admitted before the correction keep their original 30-day deadline. History is available only while the endpoint is active and you have management access. New Anonymous endpoints keep the newest 50 requests; new Developer endpoints keep the newest 500 requests; older count-uncapped endpoints remain uncapped, including after claim. Count eviction or deletion can end access earlier. Renewal, claim and account deletion never reset a capture’s deadline. Expired captures are hidden immediately; physical cleanup normally runs hourly and can be delayed.
What happens when an endpoint expires?
It stops receiving and history access ends. An expired address cannot be renewed. Developer accounts can renew active addresses for free, including existing endpoints above the new count limit. Renewal preserves the URL and uses the later of the existing expiry and seven days from now; days do not accumulate. Existing endpoint dates stay unchanged.
What happens when I reach a limit?
Creation is blocked at 1 active endpoint per guest session or 5 per account. Existing excess endpoints stay usable. Oversized bodies return 413 without capture. Daily limits are 100 admitted arrivals per day shared across endpoints in the guest creator-IP scope and 2,500 admitted arrivals per day across an account, reset at midnight UTC. Admission counts before body read, with no refund for oversize, disconnect or persistence failure; built-in tests count too. Shared networks behind NAT share the guest quota. Legacy guest attribution uses session or endpoint. Clearing, deletion, recreation and cookie changes do not reset the supported scope. Claim changes only future admissions. On 429, follow Retry-After. Configured 429 responses are captured normally.
Can I customize responses?
Yes. Both free plans support custom status, allowed response headers and body. Delays, conditional rules and forwarding are planned separately. Edited replay requires an account and runtime, worker and source availability.
When will Pro launch?
No launch date is announced. Pro is coming soon at a planned $5/month. All Pro service limits and capabilities are planned, with no checkout. Pro endpoints are intended to remain active for the duration of an active Pro subscription, subject to security, abuse, legal and service availability rules.
Who can read my captured requests?
History requires guest management access or the owning account. Use synthetic data and avoid real credentials, cookies and sensitive personal data. Captures are stored without automatic secret redaction. Browser tools process data locally with no account.