Find open-source API docs you can contribute to

Tired of checking repo after repo for one that fits? DocScout checks new projects every day and lists the ones that pass:

If someone's already working on a project, it's flagged so you don't duplicate their work.

39 projects in the last 7 days · updated 17 Oct, 23:29 UTC

  1. It looksSelf-hosted apps, GitHub searches and maintainers asking for docs help.
  2. It measuresIt reads each API spec and docs page, and counts what's missing.
  3. Gemma decidesGemma 4 reviews every candidate: it turns away the ones that aren't real apps with an API, checks nobody is already on the gap, and explains where to start.

Picks from the last 7 days

The top 3 are free. Subscribers see all 39.
  1. 1

    smaramwbc/statewave

    Open-source memory runtime for AI agents — reproducible, provenance-tagged context bundles instead of query-time retrieval. Apache-2.0, self-hosted on Postgres + pgvector, Python + TypeScript SDKs.

    • Python
    • ★ 283
    • Medium job
    • Docs published
    • Maintainers asked for help
    • Not claimed
    • 23 outside PRs merged lately
    • Found 16 Oct

    What needs doing

    19/19 endpoints have no response example

    REST API docs only in prose

    Gemma: Developers building AI agents need clear documentation on how to interact with the memory runtime's API to store and retrieve provenance-tagged context.

    Where to start

    First steps

    1. Create a comprehensive OpenAPI specification to standardize the API definition.
    2. Add request and response examples for all 19 endpoints to help developers integrate quickly.
    3. Clarify authentication requirements for each endpoint in the documentation.

    The gaps DocScout counted

    • 2/19 endpoints have no description (e.g. GET /healthz, GET /health)
    • 18/19 endpoints have no request example (e.g. POST /v1/receipts/{id}/replay, GET /healthz and 16 more)
    • 19/19 endpoints have no response example (e.g. POST /v1/receipts/{id}/replay, GET /install and 17 more)
    • 18/19 endpoints list no status or error codes (e.g. GET /install, GET /healthz and 16 more)
    • 16/19 endpoints don't say how to authenticate (e.g. GET /install, GET /healthz and 14 more)

    Add what each endpoint is missing: a description, request and response examples, status codes and auth.

    Before you start

    • Commits need sign-off (DCO) ("We use the **Developer Certificate of Origin** ([DCO](https://developercertificate." in CONTRIBUTING.md)
    • Maintainers asked for help: #481 [Docs][personal-assistant]: README badge and OpenAPI metadata say MIT, LICENSE and pyproject say Apache-2.0
    • API docs in Markdown on GitHub (the README)
    • Separate docs repo: smaramwbc/statewave-docs
    • Check manually: The README mentions Swagger UI, ReDoc or an OpenAPI URL, so a spec may be generated when the app runs
    • Check manually: Project website: statewave.ai
    • Check manually: Separate docs repo: smaramwbc/statewave-docs
    • Running it locally: easy (docker-compose)
  2. 2

    bretzel-app/crumbs

    Crumbs by Bretzel - a self-hosted, privacy-first Google Keep alternative. Capture your thoughts, ideas and notes. Built with SvelteKit.

    • New
    • TypeScript
    • ★ 127
    • Big job
    • Not claimed
    • 6 outside PRs merged lately
    • Found 17 Oct

    What needs doing

    47/47 operations have no summary or description

    REST API spec with gaps: static/api/openapi.json

    Gemma: Developers wanting to build third-party integrations or custom clients for this note-taking app would benefit from a documented API.

    Where to start

    First steps

    1. Add summaries and descriptions to all 47 API operations in the OpenAPI specification.
    2. Provide request and response examples for each endpoint to clarify expected data formats.
    3. Document the error responses and authentication schemes to help developers handle failures and and authenticate requests.

    The gaps DocScout counted

    • 47/47 operations have no summary or description (e.g. GET /api/admin/users, POST /api/admin/users and 45 more)
    • 22/47 operations have parameters without descriptions (e.g. DELETE /api/admin/users/{id}, PATCH /api/admin/users/{id} and 20 more)
    • 47/47 operations have no request or response examples (e.g. GET /api/admin/users, POST /api/admin/users and 45 more)
    • 47/47 operations have no schema for a successful response (e.g. GET /api/admin/users, POST /api/admin/users and 45 more)
    • 47/47 operations document no error responses (e.g. GET /api/admin/users, POST /api/admin/users and 45 more)
    • The API overview (info.description) is missing or very short

    This spec is generated: improve the descriptions and examples in the code annotations it's generated from, not the file itself.

    Before you start

    • Running it locally: easy (docker-compose)
  3. 3

    Chnapy/PKVault

    Centralized Pokemon storage management & Pokedex app

    • New
    • TypeScript
    • ★ 344
    • Big job
    • Docs published
    • Not claimed
    • 12 outside PRs merged lately
    • Found 17 Oct

    What needs doing

    51/51 operations have no summary or description

    REST API spec with gaps: PKVault.Core/swagger.json

    Gemma: Developers wanting to integrate with PKVault's storage management system can use the API, but the lack of descriptions and examples makes it difficult to understand how to interact with the endpoints.

    Where to start

    First steps

    1. Add summaries and descriptions to all 51 API operations in the OpenAPI specification.
    2. Add request and response examples to each endpoint to demonstrate expected data formats.
    3. Document the error responses for each operation to help users handle API failures.

    The gaps DocScout counted

    • 51/51 operations have no summary or description (e.g. GET /api/backup, PUT /api/backup and 49 more)
    • 23/51 operations have parameters without descriptions (e.g. PUT /api/backup, DELETE /api/backup and 21 more)
    • 51/51 operations have no request or response examples (e.g. GET /api/backup, PUT /api/backup and 49 more)
    • 51/51 operations document no error responses (e.g. GET /api/backup, PUT /api/backup and 49 more)
    • The API overview (info.description) is missing or very short
    • 7 operation groups (tags) have no description (e.g. Backup, Dex and 5 more)

    Fill in the missing descriptions, examples and responses in the spec.

    Before you start

    • Docs website: chnapy.github.io
    • Running it locally: easy (docker-compose)

36 more projects to choose from

Subscribe to see every pick DocScout and Gemma find.

  • Every pick from the last 7 days, checked every day for anyone already on it
  • Newest first, to see what was just found
  • Gemma's first steps for each project
  • Nothing to install, and cancel anytime
$2
per month

Test mode: no real charge. Card 4242 4242 4242 4242, any future date, any CVC.