Validate A2A Agents From Your Terminal
Catch broken agent cards and failed signatures before they hit production.
Use the capiscio CLI to validate A2A agent cards, test live endpoints, and run the same agent identity and integrity checks your guards enforce at runtime.
CLI secures your pipeline. Guard secures your runtime.
Get started in 30 seconds
npm install -g capisciopip install capisciocapiscio validate ./agent-card.jsonStop These Developer Failures
We've been on the receiving end of broken agents. The CLI exists so you don't have to be.
"It worked on my machine..."
β Every developer at 2 AM
You committed an agent card with a bad transport URL or missing field. CI passed. Production broke.
capiscio validate ./agent-card.json"Their agent stopped responding..."
β Platform engineer monitoring 3rd parties
You depend on a third party agent. They changed schema or broke their endpoint. Your users see failures first.
capiscio validate https://thirdparty.com/agent-card.json --test-live"CI says pass, prod says fail"
β DevOps lead with broken pipeline
Your tests only check JSON shape. They don't check that signatures verify or that the transport responds.
uses: capiscio/validate-a2a@v1Four Ways to Use the CLI
Choose the workflow that fits your needs
npm install -g capisciocapiscio validate ./agent-card.json- β’ Local development workflow
- β’ Pre-commit validation hooks
- β’ Quick agent card debugging
- uses: capiscio/validate-a2a@v1 with: agent-card: ./agent.json test-live: true- β’ GitHub Actions / GitLab CI
- β’ Pull request validation
- β’ Deployment gating
capiscio validate https://external-agent.comβ Agent card: valid
β Signature: valid (Ed25519)
β Endpoint: 200 OK- β’ Vetting partner agents
- β’ Registry submissions
- β’ Due diligence on new integrations
# Every 6 hours0 */6 * * * capiscio validate \https://agent.com --json \> /var/log/agent-health.logon: schedule: - cron: '0 */6 * * *'- β’ Periodic health checks
- β’ Catching signature failures early
- β’ Detecting transport issues
Why use the capiscio CLI?
Production-ready validation for AI agents
- β’ Uses same verification semantics as Guard
- β’ Agent Identity (Ed25519 signatures)
- β’ Payload integrity (body hash)
- β’ Freshness (timestamp checks)
- β’ Validates A2A agent cards against spec
- β’ Checks endpoints behave as declared
- β’ Supports HTTP/A2A today
- β’ JSON-RPC/gRPC evolving with spec
- β’ Hit declared HTTP transport
- β’ Ensure correct response behavior
- β’ Verify not just JSON shape
- β’ Real connectivity checks
- β’ JSON output for pipelines
- β’ Clear exit codes
- β’ GitHub Action available
- β’ Plug straight into CI
Usage Examples
Common validation scenarios
capiscio validate ./agent-card.jsoncapiscio validate https://example.com/agent-card.json --test-liveClear, Actionable Output
Human friendly in the terminal, machine friendly in CI.
Frequently Asked Questions
Everything you need to know
Need real-time enforcement, not just validation?
The CLI is perfect for development and CI/CD. For live production traffic, use the Capiscio Guard to enforce the same agent identity and integrity checks at the HTTP boundary.
- Enforce agent identity - Plus payload integrity and replay protection
- Drop-in Guard - Python SDK or Go sidecar
- Built on core semantics - Same checks as the CLI
from capiscio_sdk import secure, SecurityConfig
agent = secure(
MyAgentExecutor(),
SecurityConfig.production()
)
# β
Every request validated
# β‘ <2ms overhead
# π 100% compliantReady to validate and harden your AI agents?
Start with the capiscio CLI to validate A2A agents and test live endpoints. Then add the Guard when you are ready to enforce checks at runtime.
Open source β’ Built on capiscio-core β’ Designed for production