Proa documentation SDK and CLI
Official, dependency-free Python client for the public Proa documentation API. Python 3.11+; no credentials required. It reads documentation, while the separate Proa CLI scaffolds and builds applications.
uv add proa-docs
uvx proa-docs search streaming --limit 5
uvx proa-docs get /docs/core/html-rendering --markdown
from proa_docs import ProaDocs
docs = ProaDocs()
matches = docs.search("streaming", limit=5)
if matches["results"]:
page = docs.get(matches["results"][0]["path"])
print(page["markdown"])
for page in docs.documents():
print(page["path"])
search and list return typed dictionaries with results, total, and
next_cursor. Pass the returned cursor with the same query and restart after
a documentation deployment. get returns metadata and complete Markdown.
Configure ProaDocs(base_url="http://localhost:5555", timeout=15) for local
development. Timeouts are in seconds. ProaApiError exposes status, problem,
and retry_after seconds. There are no automatic retries: correct 400/404
inputs, respect 429 retry_after, and use bounded backoff for network or 5xx
failures. The server's 600 requests/minute budget is shared per instance.
Do not send secrets or private source code in search queries. CLI results are
JSON by default, errors go to stderr, and failures return a nonzero exit code.
Global CLI options (--base-url, --timeout) go before the command.
Development: uv run pytest, uv run ruff check, uv run ty check, uv build.
The contract is at https://proa.so/openapi.json; MCP clients can connect
directly to https://proa.so/mcp.
Metadata
Release files for proa-docs 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| proa_docs-0.1.0.tar.gz | 8.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| proa_docs-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.1 kB
Release files / proa_docs-0.1.0.tar.gz
| Download URL | proa_docs-0.1.0.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7324792782b8182be5012022cff602117220548a055b9802dc06223beaf54801
|
|
BLAKE2b-256 checksum How to use checksums |
b9ac5f2d542d70c49440e7db4cc2cb4a7c5dc01b05a1a03421707952f8de6890
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / proa_docs-0.1.0-py3-none-any.whl
| Download URL | proa_docs-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55cb4a9b441d4d84a5ab58fd47bc25f5b5efc620d28f0452ed55fe7067df5638
|
|
BLAKE2b-256 checksum How to use checksums |
345c8ce9a8a4beb4a4b41a2b918591fd5dd817c4d3b08f3d024efb92bbc1295f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for proa-docs 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.