Skip to main content
waterfall-integration has your agent generate client-owned integration code (Python or JavaScript/TypeScript) that lives in your own repo, written to match your stack and conventions.

​
When to reach for it

Use it when you’re building Waterfall into a product or workflow and want durable integration code you own and maintain:
  • A service or job that calls Waterfall as part of your product
  • Reusable client code your team maintains over time
  • Code that has to follow your existing stack, patterns, and conventions
Unlike Direct API, this produces real code in your repo — you own it and maintain it going forward.

​
Install

Then point your agent at the repo and have it fetch that link so it works from the current skill definition: https://github.com/Waterfall-io/api-skills

​
Source of truth

The skill tracks this documentation and the public OpenAPI spec. If its guidance ever conflicts with the live docs, the docs win. Just need live calls without maintaining code? See Direct API.