01 / CONNECT
Point DevForge at the repository.
Start where your API actually lives. DevForge focuses the scan on relevant routes, controllers, types, and schemas.
github.com/acme/api-service
GITHUB → HOSTED API DOCS
Turn code into living API docs.
DevForge scans your GitHub repository, extracts the API shape, and turns it into accurate documentation your users can actually use.
Structured API extractionHosted documentationBuilt for developer teams
docs.devforge.io/acme/projects
POST/api/projects
Create a project and return its generated identifier.
REQUESTRESPONSE
Authorizationrequired
{
"name": "API reference",
"visibility": "public"
}
"name": "API reference",
"visibility": "public"
}
THE DOCUMENTATION PIPELINE
The repo is the source of truth.
Instead of writing docs from memory after every release, give your implementation a direct line to the documentation your customers read.
02 / EXTRACT
Parse structure before writing prose.
Deterministic signals shape the docs. AI helps explain the interface with clarity.
03 / PUBLISH
Ship documentation with your API.
Review, refine, and publish a hosted reference that gives every endpoint a clear home.
ALWAYS IN MOTION
Documentation that keeps up with your codebase.
FOR THE API YOU ALREADY SHIP
Useful docs begin with accurate details.
DevForge turns important implementation signals into a clear reference—paths, methods, inputs, auth requirements, schemas, and example responses.
- Endpoint-aware: documents routes and operations in a format developers expect.
- Schema-forward: carries request and response shape into the documentation.
- Reviewable output: keeps the human expert in control before publishing.
ENDPOINTS / 24SYNCED NOW
GET
/api/projects
List your projects
POST
/api/projects
Create a project
PATCH
/api/projects/:id
Update project details
Documentation reference generated from repository context.
FAQ
Keep your API reference moving.
BUILD. AUTOMATE. SCALE.