# Try DamageBDD: URL to an executable Gherkin test

Start verifying API behaviour from a public HTTPS URL. Generate a Gherkin scenario, optionally run an approved first check, review a shareable report and schedule more tests.

Canonical HTML: <https://damagebdd.com/quickstart.html>


<a id="verify-a-public-api-endpoint-in-minutes"></a>


## Verify a public API endpoint in minutes

Do not have a feature file yet? Open the [instant API verification page](https://run.damagebdd.com/try),
paste a public HTTPS URL such as `https://example.com/health`, and choose
**Generate test**. The draft contains runnable DamageBDD HTTP steps. You can
review, copy or download it without creating an account.

```gherkin
Feature: First API verification

  Scenario: GET endpoint returns HTTP 200
    Given I am using server "https://example.com"
    When I make a GET request to "/health"
    Then the response status must be "200"
```

The example is illustrative, not evidence that a test has passed. Replace the
URL and assertion with the behaviour expected of your actual service.

<a id="first-execution-evidence-and-scheduling"></a>


## First execution, evidence and scheduling

The current quickstart generates a deterministic scenario without contacting
its target. A **separate Run click** performs a single read-only HTTP status
check, **only if** the server operator has enabled free trials and approved that
exact HTTPS hostname and path. Otherwise, generation and download still work,
but free execution is unavailable.

Eligible trials can produce a time-limited, shareable verification report.
Reports describe the observed response; they do not establish full application
correctness. Do not put private information or credentials in the URL or share
sensitive paths. The MVP supports HTTPS port 443 and simple paths without URL
credentials, query strings or fragments.

For continuing regression checks, sign in to the [DamageBDD dashboard](https://run.damagebdd.com/)
and schedule the generated scenario. Recurring execution uses normal account
authorisation, execution credits and domain policies; a free first check does
not grant free scheduled runs.

<a id="participate-in-verification"></a>


## Participate in verification

For programmatic testing, use the
[Python quickstart for humans, bots and LLM agents](python-quickstart.md).
It covers keypairs, authentication, DAMAGE funding through the Lightning API
or Coinstore, paid execution and report inspection. The account and settlement
requirements for paid execution are separate from an approved free trial.

Test writers can explore the [user manual](manual.md) and the
[step-module reference](modules/index.md). Operators can
[install a Damage node](https://run.damagebdd.com/install) to help provide
verification capacity. Source code is available from
[the DamageBDD repository](https://github.com/DamageBDD/DamageBDD).