Skip to main content

a2a-lint

Lint your A2A agents — validate agent cards against the spec, run live conformance probes in CI, and earn a conformance badge. Playground UI included.

Built for the A2A (Agent2Agent) protocol: the open standard (Google → Linux Foundation) that lets AI agents discover and delegate work to each other. Your agent speaks A2A the moment its card and endpoints conform — a2a-lint makes sure they do, and keep doing so on every push.

Why a2a-lint

Inspecting an agent once is easy (the official a2a-inspector does it well). Staying conformant is the hard part: a renamed skill, a card whose advertised url only resolves inside your compose network, a message/send that stopped returning Tasks — all invisible until another agent fails against yours. a2a-lint is built around continuous conformance:

  • CLI with CI-friendly exit codes — wire it into any pipeline
  • GitHub Action — every push checks the card and does a live round trip
  • Live badge — your README shows your current conformance grade
  • Playground — when something fails, debug it interactively with full wire-level detail

Quick start

docker compose up --build -d      # playground on http://localhost:8090

Paste any agent's base URL: you get its Agent Card rendered and graded (field-by-field findings with fix hints), an interactive JSON-RPC message/send console, tasks/get inspection, an SSE message/stream viewer, and shareable permalinks of inspection snapshots.

Inspecting agents that run on your host from inside the container? Use http://host.docker.internal:<port> (mapped via extra_hosts).

CLI

pip install git+https://github.com/vivek24290/a2a-lint@develop   # PyPI release coming
a2a-lint https://my-agent.example.com --live
✔ Weather Agent — card at https://my-agent.example.com/.well-known/agent-card.json (12 ms)
✔ live message/send round trip in 48 ms
GRADE B — 0 error(s), 1 warning(s)
  WARN  url: Endpoint URL is plain http.
        ↳ Use https in production; A2A messages can carry sensitive content.
Flag Effect
--live also send a real message/send and verify the result is a Task/Message; if the card declares streaming: true, message/stream SSE conformance is checked too
--strict warnings fail the lint too
--json machine-readable output

Exit codes: 0 conformant · 1 findings · 2 unreachable/not A2A.

--live catches the classic deployment bug: a card that advertises a URL its consumers can't reach (e.g. a container-internal hostname on a public card).

GitHub Action

jobs:
  a2a-conformance:
    runs-on: ubuntu-latest
    steps:
      - uses: vivek24290/a2a-lint@v1
        with:
          url: https://my-agent.example.com
          live: "true"
          strict: "false"

Conformance badge

Live-graded SVG (5-minute cache) served by your playground instance:

![A2A conformance](https://<your-playground-host>/api/badge?url=https://my-agent.example.com)

What gets checked

Required card fields (name, description, url, version, capabilities, defaultInputModes/OutputModes, skills and per-skill fields), transport declarations, deprecated card paths, http-vs-https, missing tags/examples, undeclared auth — each finding carries a level (error/warn/info) and a concrete fix hint. Grades: A (clean) → F. See server/card_validator.py; the same core powers the CLI, the Action, the badge, and the playground.

a2a-watch monitor (MVP)

Open /status.html on your playground instance: register any agent and it gets probed on a schedule (card fetch + validation + live message/send — the same check the CLI runs). You get UP/DOWN state, 24h uptime, conformance grade, latency, and a webhook alert (JSON down/recovered events — point it at Slack/Discord/anything) the moment an agent breaks or recovers.

curl -X POST localhost:8090/api/monitor/agents -H 'Content-Type: application/json' \
  -d '{"url": "https://my-agent.example.com", "intervalSeconds": 300,
       "webhook": "https://hooks.slack.com/services/..."}'

History lives in data/monitor.db. If an agent's card advertises an unreachable url, the monitor falls back to the registered URL and reports the bad card instead of a false DOWN.

Architecture

a2a_lint/              the pip-installable package (shared core)
├── client.py          A2A client: card discovery, message/send, tasks/get, streaming
├── validator.py       spec checks -> structured findings
└── cli.py             the a2a-lint command (exit codes 0/1/2)
server/
├── main.py            FastAPI: playground API, SSE proxy, permalinks, badge, monitor API
├── monitor.py         a2a-watch core: scheduler, uptime history, webhook alerts
└── static/            playground UI (index.html) + monitor UI (status.html)
action.yml             GitHub Action wrapping the CLI

No LLM calls, no telemetry, no external services. Permalink snapshots and monitor history are SQLite files under ./data/.

Roadmap

  • pip install a2a-lint packaging (PyPI publish via .github/workflows/publish.yml)
  • message/stream conformance checks in the CLI
  • Security-scheme validation
  • a2a-watch monitor MVP: scheduled probes, uptime history, webhook alerts
  • Hosted a2a-watch: accounts, public status pages, e-mail alerts, paid tiers
  • Public playground instance (VPS + domain)

License

MIT

Metadata

Release files for a2a-lint 0.1.1

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

Source distribution (sdist)

Source distribution for a2a-lint 0.1.1
File Size Uploaded Provenance
a2a_lint-0.1.1.tar.gz 23.9 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for a2a-lint 0.1.1
File Interpreter ABI Platform
a2a_lint-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 36.8 kB

Release files / a2a_lint-0.1.1.tar.gz

Download URL a2a_lint-0.1.1.tar.gz
Size 23.9 kB
Tags Source
SHA-256 checksum
How to use checksums
1b2faffca975a26d35a236ea889355b7816c56e4051d5659c11bb45d9d27080d
BLAKE2b-256 checksum
How to use checksums
d17410b90fcbaf086d41c35c3e1a2699bfb9874f5a0c9166df3c11c5d350bb6c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 11, 2026.

Transparency log

Release files / a2a_lint-0.1.1-py3-none-any.whl

Download URL a2a_lint-0.1.1-py3-none-any.whl
Size 13.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5fd045cc30de72ceece3c54853b49400b9d185e2efce3b464c2ec1bdc9cae95e
BLAKE2b-256 checksum
How to use checksums
8b043b189c8c532867dcb55a50e1189856a24edb3e63e184fe0a02fccc6804a2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 11, 2026.

Transparency log

Security for a2a-lint 0.1.1

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.

Select from 2 files

Attestation for a2a_lint-0.1.1.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 Jul 11, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files Full provenance

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