Markbase vs. ngrok and request bins: Let your coding agent see the webhooks it is building against.
A tunnel or a request bin may be all you need to see a webhook yourself. Markbase hands each request straight to the coding agent that is building the integration.
[ Which fits? ]
Start with the work you need to do.
When a tunnel or request bin fits
Choose a tunnel when the request has to reach a server running on your machine, or a request bin when you want to read requests in a browser yourself.
When Markbase fits
Choose Markbase temporary webhooks when your agent should make the URL, register it or hand it to you, and read each request itself, with nothing to install or run.
[ Side by side ]
Markbase vs. ngrok and request bins, side by side.
| What matters | a tunnel or request bin | Markbase |
|---|---|---|
| Setting it up | Install and run a tunnel client, or open a request bin page, then copy the URL into the service. | Ask your agent for a webhook URL. It makes one over its Markbase connection and registers it itself or gives it to you to paste. |
| Who reads the request | Your local server receives it through the tunnel, or you read it in the bin’s web page and copy what matters to your agent. | The agent that made the URL receives each request as it arrives, with its method, path, headers and parsed JSON. |
| How long it lasts | Depends on the tool and plan; paid plans typically keep URLs permanently. | Each URL expires on its own, after 30 minutes by default and at most six hours. The content is deleted an hour later. |
| Who can see it | Depends on the tool’s account and sharing settings. | Only the person who asked for the URL, in their agent and on their dashboard. An optional secret limits who can send to it. |
| Forwarding to localhost | A tunnel’s core job: requests reach the port you choose on your machine. | Not offered. Markbase receives and holds the request for the agent; it never forwards it anywhere. |
Product references: ngrok pricing · Webhook.site. Checked October 8, 2026.
[ Pricing ]
Compare what you already pay for.
Temporary webhooks are on every Markbase plan, including Free, with no daily allowance. If you already pay for a tunnel or request bin, keep it for the jobs it does well.
A tunnel: ngrok
Free includes up to 3 online endpoints, and 20k HTTP/S requests. Hobbyist is $10 a month; Pay-as-you-go is $20 a month plus usage.
A request bin: Webhook.site
Free URLs expire and accept a limited number of requests. Paid accounts start from $7.50 a month and keep URLs permanently.
Examples of each kind of tool, not a price for the whole category or a feature-equivalent Markbase plan. Figures checked October 24, 2026: ngrok’s pricing page.
Your agent provider bills the agent’s work separately, whichever tool delivers the webhook.
Markbase Free
$0a month
One person
3 workspaces, 200 documents each. 500 MB of storage.
Markbase Pro
$20a month
or $192 a year
Includes 5 seats
25 workspaces, 1,000 documents each. 25 GB of storage.
Markbase Team
$40a month
or $384 a year
Includes 10 seats, then $5 each
100 workspaces, 5,000 documents each. 250 GB of storage.
Markbase prices are USD before tax. Team’s extra seats are $5 each per month or $48 each per year, up to 100 members total. Enterprise and private deployments are quoted separately. Coding agents and model usage are not included. Full plans and limits
[ In practice ]
Try it on one integration.
The starting point
You are adding a Stripe webhook handler. You start a tunnel, paste its URL into Stripe, trigger a test event, then copy the payload from the inspector into your agent so it can write the handler.
With a shared workspace
Ask your agent for a webhook URL. It gives you the URL and when it expires; you paste it into Stripe and send a test event. The agent reads the real payload and writes the handler against it.
Provider signatures such as Stripe-Signature reach the agent as headers but aren’t checked by Markbase.
Read the temporary webhooks guide[ Getting started ]
Try it with one piece of work.
- 01
Connect your coding agent to Markbase.
- 02
Ask it for a webhook URL while it works on an integration.
- 03
Send one real event and compare what the agent does with it.
[ Questions ]
A few practical questions.
- Can we use both?
- Yes. Keep a tunnel for testing a server running on your machine end to end, and use a temporary webhook when the agent needs to see what a service sends.
- Does it start an agent when nobody is working?
- No. A temporary webhook feeds the agent that made it. For a standing URL that starts an agent when an event arrives, use Dispatch.
- Is it on the free plan?
- Yes. Temporary webhooks are on every plan, with no daily allowance. Each person can have up to 20 live at once.
[ More comparisons ]