API monitoring for small teams

Check your API the way your customers use it.

Wrenbeacon runs short request checks, confirms a failure from a second location, then pages only the engineer on call.

Free during early access.

The problem

A green health check is not a working API.

A basic uptime check asks one question: did the server answer? Your customers need the whole request to work.

  1. 200

    Checkout breaks behind a 200

    The status endpoint answers while the request customers need is failing.

  2. failed ping

    One blip wakes everyone

    A single failed ping from one place pages the whole channel at night.

  3. support email

    Customers notice first

    Often the first sign of an outage is a support email from a customer.

What changes

When it pages you, it has a reason.

  1. Real requests

    Test what customers do

    Chain a few calls and check what comes back, not just the status.

  2. Second opinion

    Confirm before paging

    A failure runs again from a second location before anyone hears about it.

  3. One person

    Page with the evidence

    The engineer on call gets the failed request and its response.

How it works

From a short check file to one clear page.

  1. 01

    Write the check

    Describe the requests a customer makes in one short check file.

  2. 02

    Wrenbeacon runs it

    It runs your checks and reruns every failure from a second location.

  3. 03

    One person is paged

    The engineer on call gets the failing step and a timeline to share.

Samplechecks/checkout-flow.yml
check: checkout-flowsteps:  - request: POST /v1/session    expect: status 201  - request: POST /v1/cart/items    expect: body.items not empty  - request: POST /v1/checkout    expect: status 200confirm: second-locationpage: on-call

FAQ

Questions teams ask first

Will one flaky check page us?

No. Someone is paged only after a second location sees the same failure.

How long does setup take?

We are measuring this with early-access teams. We will share a number once we have one.

Where do alerts go?

To the engineer on call by chat or phone. Those integrations are still in early access.

What happens to our responses and keys?

Each alert carries the failed request and its response. We show you what is stored before you connect an API.

What does it cost?

Free during early access. We share pricing before any charge.

Early access

Run your first check with us.

Tell us what you watch today. We reply with a time to set up your first check together.

Concept site: nothing you type is sent or stored.

Privacy

  1. This concept site collects nothing. The form sends no data, and no analytics script is loaded.

  2. A live version would collect only the form fields you submit and cookieless page-view counts. They would be used to reply to you and to see which sections are read.