# Introduction

Source: https://solidhooks.com/docs

> SolidHooks receives inbound webhooks, verifies them, stores them as a system of record and delivers them to your services with retries.

SolidHooks sits between the services that send you webhooks and the services that act on them. A provider such as Stripe or GitHub posts to a SolidHooks URL instead of your server. SolidHooks checks the signature, stores the request exactly as it arrived, and delivers it to every destination that should see it, retrying until each one acknowledges it.

Nothing is lost along the way. Every request is stored before it is delivered, including the ones that fail verification, so you can always answer "did that webhook arrive, and what happened to it?"

## Start here

- [Quickstart](https://solidhooks.com/docs/quickstart): Create a source, point it at a destination and watch your first delivery land.

- [How SolidHooks works](https://solidhooks.com/docs/how-it-works): The pipeline from provider to destination, and the objects along the way.

## The pipeline

```text
provider → source (verified) → event stored → connections matched → deliveries → destination
```

* A [source](https://solidhooks.com/docs/sources) is an inbound endpoint with its own URL. It knows how its provider signs requests.
* A [destination](https://solidhooks.com/docs/destinations) is an HTTP endpoint you own: a public URL, or a service inside a private network.
* A [connection](https://solidhooks.com/docs/connections) routes a source to a destination, optionally filtered by event type.
* An [event](https://solidhooks.com/docs/events) is one stored inbound request.
* A [delivery](https://solidhooks.com/docs/deliveries) is one event sent to one destination, with its full attempt history.

## Go deeper

- [Receiving](https://solidhooks.com/docs/verification): Verify signatures, deduplicate retries from the provider, and receive email as events.

- [Delivering](https://solidhooks.com/docs/retries): Retries, signing what your endpoint receives, throughput, and delivery into private networks.

- [Operating](https://solidhooks.com/docs/replay): Replay and retry during an incident, tail activity live, and rotate secrets without downtime.

- [Access](https://solidhooks.com/docs/api-keys): API keys, Agent Auth, plans and usage, and every error code.

## Built for people and agents

Everything the dashboard does is also an HTTP API call. AI agents can hold their own delegated identity instead of a shared key.

- [API reference](https://api.solidhooks.com/v1/): Every endpoint, generated from the OpenAPI spec the API serves.

- [Agent Auth](https://solidhooks.com/docs/agent-auth): Register an agent, get it approved by a human, and act within what was granted.

- [Agent guide](https://api.solidhooks.com/llms-full.txt): The whole API surface in one Markdown file, written for agents.