ApiConsultor
Consultor offline de APIs Python y documentación local. Indexa docstrings y
ficheros (.txt, .md, .rst, .zip) en SQLite y responde con un LLM local vía
Ollama (qwen3:8b + bge-m3), citando las fuentes.
Instalación
Requisitos: Python 3.12+, uv y Ollama en marcha.
uv tool install api-consultor
api setup # descarga los modelos y ofrece indexar la biblioteca estándar
Actualizar: uv tool upgrade api-consultor (y api setup si cambió el Modelfile).
Uso
api index requests rich # paquetes del entorno de la herramienta
api index pygame -p .venv # ... o de un entorno virtual de tu proyecto
api index --stdlib # biblioteca estándar
api index-docs [CARPETA] # documentación local
api ask # entra en chat interactivo
api ask -s requests "..." # pregunta solo sobre una fuente (repetible)
api sources # qué hay indexado (--update, --remove, --relocate)
api --help y api COMANDO --help describen todas las opciones.
Configuración
api config muestra los valores efectivos, las rutas de datos y, si no existe, ofrece
crear un config.toml comentado. Solo hace falta indicar lo que cambies:
[models] # chat, embed, embed_dim
[paths] # db, docs
[retrieval] # k, candidates, max_per_symbol, max_distance
[display] # width
[links] # url, p. ej. "vscode://file/{path}:{line}"
Documentación avanzada
- Uso detallado: todos los comandos, entornos
--python, estados de las fuentes. - Configuración: rutas, opciones de
config.toml, enlaces a editores,Modelfile. - Cómo funciona: indexado, recuperación híbrida, citas, integridad del índice y limitaciones.
- Evaluar la recuperación:
api eval, métricas y formato de los casos. - Desarrollo: calidad, CI y publicación en PyPI.
Desarrollo
git clone https://github.com/isidro-rodriguez/api-consultor
cd api-consultor
uv sync && uv run pre-commit install
uv run pytest # ruff, ty y pytest también corren en pre-commit / pre-push
Las versiones se publican en PyPI al subir una etiqueta vX.Y.Z. Detalles en
AGENTS.md y
CHANGELOG.md.
Metadata
Release files for api-consultor 0.4.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 | |
|---|---|---|---|---|
| api_consultor-0.4.0.tar.gz | 145.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| api_consultor-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 210.7 kB
Release files / api_consultor-0.4.0.tar.gz
| Download URL | api_consultor-0.4.0.tar.gz |
|---|---|
| Size | 145.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be94d57f47bef605827a7ec1bd59ddbfa0f98079dbbc780c5a827ee1eedd3ed7
|
|
BLAKE2b-256 checksum How to use checksums |
3630c13578583bca2321afe0fd7d298ae565e4665e6308d2dcfe70bd5035699e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / api_consultor-0.4.0-py3-none-any.whl
| Download URL | api_consultor-0.4.0-py3-none-any.whl |
|---|---|
| Size | 65.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d7d416c2bb3f768726fd308409840eaffbd564c294d2b2f2f72932d3a28f7a01
|
|
BLAKE2b-256 checksum How to use checksums |
4aec5e240a69f2dbf3d62d1e0c5f1a78533052e69e2a4ace1089148de7f1c662
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for api-consultor 0.4.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for api_consultor-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA 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.