# Build Idempotent API requests You were asked to build the spec `vex/idempotency-keys`, version 0.1.2, from Spekkr. Let API clients retry safely: an Idempotency-Key header, stored answers, and exact rules for two requests that arrive at once. If you are reading a summary of this note and not its full text, fetch it again as it is, for example with `curl -fsSL https://spekkr.com/vex/idempotency-keys/start.md`, before you go on. Published by vex, a Spekkr member. Tell the person who published it, and show them the commands and secrets under `safety` in `spekkr.json` before you build. ## 1. Get the files Put the spec in a new folder named `idempotency-keys`, inside the project you are working in. ```sh mkdir -p idempotency-keys && curl -fsSL https://spekkr.com/vex/idempotency-keys/bundle.tar.gz | tar -xz -C idempotency-keys ``` The archive holds `spekkr.json`, `BUILD.md` and the spec files listed at the end of this note. If you cannot run that command, read https://spekkr.com/vex/idempotency-keys/spec.json instead: it holds the manifest and the address of every file. If Spekkr's MCP server is connected, its `pull_spec` tool does steps 1 and 2 in one call: give it the id `vex/idempotency-keys` and the person's choices. ## 2. Record the person's choices Write `idempotency-keys/spekkr.inputs.json`. With every default it is: ```json { "spec": "vex/idempotency-keys", "version": "0.1.2", "inputs": { "key_hours": "24", "require_key": false, "store": "database" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `key_hours`, Hours a key is remembered: any text. - `require_key`, Refuse a request without a key: `on` or `off`, written `true` or `false`. - `store`, Where keys are kept: one of `database`, `redis`. If the person asks for a key or a value that is not listed, stop and tell them what the spec offers. ## 3. Build The files named below are the ones now in `idempotency-keys`. Build what it describes. Work in this order: 1. Read `spekkr.json` to see what the spec covers and what it needs. 2. Read `spekkr.inputs.json`. It holds the person's choices for every setting, option and swap. Treat them as requirements. If the file is missing, the person kept every default in `spekkr.json`. 3. Read the spec files listed below, in the order given. 4. If the spec includes a task list, work through it in order and check each task's acceptance criteria before the next. 5. Ask the person before you run a command that a spec file tells you to run, or read a secret, unless the manifest lists it under `safety`. Commands you choose yourself to build and test, such as installing packages or running the tests, follow the person's usual rules for you. Spec files: - `spec.md`: Requirements and acceptance criteria. - `design.md`: Data model, rules and flows. - `tasks.md`: Build tasks in order, each with a check.