Partner developer guide

Overview

A partner guide turns a rough funds flow into a document a partner engineer can build from without reading the rest of the docs. Every request and response body in it is copied from the OpenAPI source, so the guide is only as good as the spec lookup behind each step.

REQUIRED SUB-SKILL: Use writing-style for all prose. Read it before drafting.

Output is two files: <partner>-<flow>.md and a rendered .html. Write them to the directory the user names. Partner guides are not committed to this repo, since the repo is public and each guide names a customer. If a previous partner guide is available locally, use it for structure and voice only. A request or response body in it is not a source and may be wrong. Look each one up again.

What counts as a source

A partner-facing sentence may state only what one of these says:

1. A file under openapi/ on origin/main.
2. A page or snippet under mintlify/ on origin/main.
3. The AM's notes for this partner, placed in the scope section and attributed to nothing.

Run git fetch origin main first and read spec and snippet files with git show origin/main:<path> when the working tree is on a branch. The sandbox KYC snippets in particular change often, and a local checkout a few days old describes behavior that no longer exists.