API documentation writing
Documents endpoints from the code that implements them, not from what the last doc said. Every parameter gets its real type, requiredness, default and constraints, and every error the endpoint can return is documented with what triggers it — the half that's usually missing and the half developers need. Discrepancies between existing docs and current behaviour are listed separately as bugs.
Published by Oasis Platform · Free to add
Connect these once. Oasis holds the connection, and every agent you build after this can reuse it.
Claude Managed AgentIt lands in your Oasis
API Docs Writer is created in your workspace with its instructions and settings already filled in.
You connect its apps
Sign in to GitHub once and it has everything it needs.
You make it yours
Rewrite the instructions, swap the model, add files and skills. It is a starting point, not a lock-in.
Turns merged pull requests into release notes people actually read. Each user-visible change is translated into what it means for someone using the product, never the PR title or commit message, and internal refactors and dependency bumps are dropped. Breaking changes lead, with the migration step attached.
Oasis PlatformEngineeringReviews pull requests like a senior engineer who read the whole diff. It hunts for what actually breaks in production — unhandled failure paths, race conditions, N+1 queries, missing authorization checks, behaviour the tests don't cover — and states the concrete inputs that would fail. Style and formatting are skipped entirely, because a review full of nitpicks buries the real bug.
Oasis PlatformEngineeringRuns in your terminal on a repo you actually have checked out, and answers the questions a new engineer wastes a week on. It starts from the entry points and follows the real call path rather than guessing from directory names, because directory names lie and imports don't. You get the layout, the request path with file references, the conventions the code really follows, and which parts are risky to touch.
Oasis PlatformEngineeringDuring an incident it keeps the picture straight so the responder can keep working. It assembles what alerted, the blast radius, what deployed or changed in the hours before — the thing everyone forgets under pressure — and maintains a running timeline of what's been tried. Status updates come drafted in both internal and customer-facing registers, and it changes nothing in production.
Oasis PlatformEngineeringAdd it to your Oasis, connect its apps, and hand it the first task. Everything about it stays editable.
© 2026 Oasis, Inc.
Add to your Oasis