v1.2.6 • New: Live Transport Validation

Capiscio CLI

A2A Protocol Validator with JWS Signature Verification

CLI tool that validates A2A protocol compliance and verifies JWS signatures. Tests live JSONRPC, GRPC, and REST endpoints to catch integration issues before deployment. Includes cryptographic verification of agent authenticity.

🔐 Verified
Cryptographic
70%+ Coverage
Test Quality
Node 16+
Compatible

Choose Your Installation Method

Multiple ways to get started - pick what works for you

Node.js Package
npm install -g
capiscio-cli
Requires Node.js 16+
Most popular choice
Python Package
pip install
capiscio
Requires Python 3.7+
Cross-platform compatibility
Standalone Binary
Download
No dependencies required
Ready to run anywhere
View on GitHub

Quick Start

Get up and running in under 60 seconds

1
Choose Install Method
Pick npm, pip, or standalone binary
npm install -g capiscio-cli
pip install capiscio
or download binary
2
Validate
Run validation on your agent
capiscio validate ./agent-card.json
Deploy
Ship with confidence
✅ Ready for production

Why Choose Capiscio CLI?

Production-ready validation for AI agents

🔒
NEW
Cryptographic Verification
  • • JWS signature validation (RFC 7515)
  • • JWKS endpoint verification
  • • Secure by default architecture
Live Transport Testing
  • • JSONRPC, GRPC, REST validation
  • • Real connectivity checks
  • • Cross-transport consistency
  • • Production health validation
Developer Friendly
  • • Rich CLI experience
  • • JSON output for CI/CD
  • • Extensible architecture
A2A Protocol Expert
  • • Official A2A v0.3.0 compliance
  • • Legacy format support
  • • Future-proof updates

Usage Examples

Common validation scenarios

Basic Agent Validation
Validate agents from URLs or local files
# Works with both npm and pip installations
capiscio validate https://your-agent.com
# Validate local file
capiscio validate ./agent-card.json
# Auto-detect in current directory
capiscio validate
💡 Installation Options:
• npm: npm install -g capiscio-cli
• pip: pip install capiscio

Validation Output

Clear, actionable feedback

Successful Validation
✅ A2A AGENT VALIDATION PASSED
Agent: https://api.example.com
Score: 100/100
Version: 0.3.0 (Strictness: progressive)
🔍 VALIDATION SUMMARY:
📊 3 checks performed: 3 passed, 0 failed, 0 warnings
⏱️ Completed in 245ms
🏆 Perfect! Your agent passes all validations.
🚀 Your agent is ready for deployment!
✕
Failed Validation
❌ A2A AGENT VALIDATION FAILED
Agent: ./agent-card.json
Score: 65/100
Version: 0.3.0 (Strictness: progressive)
🔍 VALIDATION SUMMARY:
📊 3 checks performed: 2 passed, 1 failed, 1 warnings
⏱️ Completed in 89ms
🔍 ERRORS FOUND (2):
❌ ENDPOINT_UNREACHABLE: Primary endpoint not accessible
❌ MISSING_SECURITY_SCHEME: No security scheme defined

Perfect For

Built for the AI agent ecosystem

AI/LLM Developers
Building agent-based applications

Validate your AI agents before deployment and ensure they meet A2A protocol standards.

DevOps Teams
Validating in CI/CD pipelines

Integrate validation into your deployment pipeline with JSON output and error codes.

Registry Operators
Ensuring protocol compliance

Validate agent submissions and ensure registry quality with comprehensive checks.

AI Researchers
Agent-to-agent communication

Ensure your research agents conform to interoperability standards.

Product Teams
Deploying AI agents to production

Ship AI agents with confidence using production-ready validation.

Platform Builders
Creating agent ecosystems

Build platforms that require validated, compliant AI agents.

Frequently Asked Questions

Everything you need to know

What is JWS signature verification and why should I use it?

JWS (JSON Web Signature) verification validates that an agent card hasn't been modified and comes from a trusted source. Useful for verifying third-party agents and maintaining integrity in production deployments.

# Runs automatically - signatures verified if present
capiscio validate ./agent-card.json

Implementation: RFC 7515 compliant, HTTPS-only JWKS fetching, detached signature support.

What is the A2A Protocol?

The Agent-to-Agent (A2A) protocol is a standardized specification for AI agent discovery, communication, and interoperability. It defines how AI agents expose their capabilities, endpoints, and metadata through standardized agent card files.

How do I validate my AI agent for production?
capiscio validate ./agent-card.json --strict

Use --strict mode to ensure full protocol compliance.

Can I use this in CI/CD pipelines?
capiscio validate ./agent-card.json --json --errors-only

Yes! The --json flag outputs structured results perfect for CI/CD integration.

Can I validate live agent endpoints?

Yes! Capiscio CLI can validate both local files and live web endpoints. Simply provide a URL instead of a file path:

capiscio validate https://api.example.com

This is perfect for testing deployed agents, monitoring endpoint health, and validating production configurations.

What's the difference between validation modes?
  • Progressive (default): Balanced validation with helpful warnings
  • Strict: Full compliance required - perfect for production
  • Conservative: Minimal validation - ideal for development

Ready to Validate Your AI Agents?

Join the growing ecosystem of A2A protocol compliant AI agents

View Documentation

MIT Licensed • Zero Dependencies • Production Ready