# How to use this guide

Read it once end to end — it is about twenty minutes — then keep two parts open
while you build.

## If you are starting now

Sections 1 to 3 in order. They decide your architecture: the pipeline's shape,
why you are on the asynchronous endpoint, and how to poll. Getting these wrong
is a rewrite; getting the rest wrong is an edit.

## If you already have something working

Two sections earn their keep at review time:

- **Section 5, Read the result honestly.** Three mistakes are close to
  universal: re-sorting `candidates`, treating `items: []` as an error, and
  shipping copy that says "identified" or "found". Any of the three is a
  correctness bug, and the last one is a promise your product cannot keep.
- **Section 10, the checklist.** Ten lines. Run it before you ship.

## If something is failing

Section 8 maps every error you can get to whether you should retry it, whether
you were charged, and whether it is yours to fix. Start there rather than in the
endpoint reference — the reference tells you what a `404` is, this tells you why
it will not tell you more.

## What it assumes

That you have a key and have run one read. If not, start with the platform's own
quickstart at `https://inspired.jetskibay.com/docs`, then come back. Code is
`bash` plus `curl` and `jq`, because that translates to whatever you actually
use; a finished client is the `inspired` CLI published beside this guide.