Skip to main content

agent-readable

CI PyPI

Stop coding agents from hallucinating Python APIs. agent_help(target) reads the live public API surface from any Python class, module, function, or method and renders compact, agent-oriented Markdown with current signatures and docstring summaries. When a library opts in, it can also return class-level usage rules such as lifecycle order, preconditions, and anti-patterns.

To let your coding agent automatically call agent_help() before using an unfamiliar API, install the companion skill:

npx skills add zydo/skills --skill agent-readable

logging.Logger compared with agent_help() and help()
agent_help vs help

Quickstart

See Getting started for installation, one-off CLI usage with uvx, uv tool run, or pipx, and full CLI examples.

from agent_readable import agent_help
import logging

print(agent_help(logging.Logger))

agent_help() works on plain Python objects with no setup required. It returns a curated public API list from runtime introspection, so agents see what exists in the installed version instead of guessing from stale training data.

Library authors can optionally add usage rules next to the code:

class Sensor:
    """Reads a value from a hardware sensor."""

    def read(self) -> float:
        """Read the current sensor value."""

    @classmethod
    def __agent_notes__(cls) -> str:
        return """
## Do

- Call `calibrate()` once during setup, before `read()`.

## Do not

- Do not call `read()` before calibration on first use.
"""

Docs

  • Getting started: installation, quickstart, CLI usage, and other language implementations.
  • Why it matters: the API hallucination problem, token efficiency, and how this compares to other agent-doc patterns.
  • Examples: wrapping existing classes, inherited notes, duck typing, plain classes, modules, functions, and methods.
  • Authoring guide: __agent_help__, __agent_notes__, class docstring hints, freshness guidance, and API reference.
  • FAQ: common questions about agent skills, docstrings, AGENTS.md, third-party libraries, and constrained decoding.
  • Benchmark: methodology and harness measuring whether agent_help() context reduces hallucinated-API failures.

Other Languages

License

MIT

Release files for agent-readable 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agent-readable 0.3.0
File Size Uploaded
agent_readable-0.3.0.tar.gz 51.2 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for agent-readable 0.3.0
File Interpreter ABI Platform
agent_readable-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 51.2 MB

Release files / agent_readable-0.3.0.tar.gz

Download URL agent_readable-0.3.0.tar.gz
Size 51.2 MB
Tags Source
SHA-256 checksum
How to use checksums
77df1359606c9cbc4a00187236d7ab31f5ae60c2eb106e48e845c27348e09f46
BLAKE2b-256 checksum
How to use checksums
05162853876c46473dbee9763c16f35dfa68dc0ddef3f3649fd120906cf5ec64
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 23, 2026.

Transparency log

Release files / agent_readable-0.3.0-py3-none-any.whl

Download URL agent_readable-0.3.0-py3-none-any.whl
Size 13.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
69d638b563c476f796b3fe82e26e9e3aa1a548345cb116014a078fc9881d78b3
BLAKE2b-256 checksum
How to use checksums
9092d440e73770b2621ee795552247b537cec9bf1e6337826c2ebc600ba4c913
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 23, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.1

2 release files

This release

0.3.0 This release

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page