{"id":"adriannoes-asap-protocol","name":"asap-protocol","af_score":70.0,"security_score":77.8,"reliability_score":48.8,"what_it_does":"asap-protocol provides an agent-to-agent communication and task coordination protocol with stateful orchestration (state machine + snapshotting/resumability), schema-first interoperability (Pydantic/JSON Schema), and support for tool execution/coordination via MCP in a single message envelope. It also includes observability identifiers and multiple security options (Bearer auth, OAuth2/JWT, Ed25519 signed manifests, optional mTLS, replay prevention, rate limiting) plus CLI utilities and a compliance harness.","best_when":"You need reliable agent-to-agent coordination with persistence/resume semantics and cross-agent schema compatibility, optionally with MCP tool-calling and strong identity/signing.","avoid_when":"You only need direct point-to-point requests and do not benefit from stateful orchestration, metering, or signature-based trust.","last_evaluated":"2026-03-30T15:41:04.045750+00:00","has_mcp":true,"has_api":true,"auth_methods":["Bearer auth","OAuth2/JWT","Ed25519 signed manifests","optional mTLS"],"has_free_tier":false,"known_gotchas":["Misaligned schema versions across agents can break interoperability if schema migration guidance is not followed.","Security configuration mismatches (OAuth/JWT trust levels, manifest signature verification, optional mTLS) can cause handshake failures.","State drift can occur if agents do not correctly persist/restore workflow snapshots during long-running coordination."],"error_quality":0.0}