domain: rain-4.gitbook.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request an API key from the Rain team for the environment needed (MOCK is self-serve; STAGE and PROD require contacting Rain)
Open the interactive Swagger/OpenAPI reference to browse available endpoints, request/response schemas, and try live calls
Authenticate requests using the issued API key
Use the documented add/update/get/delete operations for supported resources
For catalog and product data, use the FTP submission path instead of the API, since catalog details can't be added or updated through the API
Validate responses against the Swagger examples, since the documentation regenerates automatically with each backend release
Known gotchas
Catalog and product data is a documented exception — it must go through an FTP file submission, not the REST API, so don't assume full CRUD coverage
MOCK, STAGE, and PROD are separate environments with separate credentials — testing against MOCK doesn't guarantee STAGE/PROD behavior matches
Because docs regenerate automatically with each release, confirm the exact endpoint/schema close to build time rather than trusting cached documentation
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?