Foundation47 questions · 60–90 min
Build the common vocabulary
Prerequisite: Basic web or API familiarity.
Purpose: Read requirements, HTTP, JSON, OAuth, and privacy without mixing their boundaries.
A2A and API Design Quizzes
Practice decisions about trust, authorization, retries, logging, and TLS
Five-minute design check
What can you actually trust in this A2A or API integration?
These questions test five situations that regularly appear in implementation and design review. They do not ask you to memorize RFC numbers; each answer explains the governing decision and what to study next.
- 5 questionsMultiple choice
- About 5 minExplanation for every answer
- PrerequisiteBasic web and API knowledge
Peer discoveryOperation authoritySafe retriesLogs and privacyTLS boundaries
Starter path
49 questions · about 60–90 minutes
Five RFCs for a shared foundation
Choose your level
Times are approximate; explanations are included
Courses by experience and review depth
Practitioner52 questions · 75–105 min
Make deployment and trust decisions
Prerequisite: Foundation course or API security experience.
Purpose: Review JWT, metadata, TLS, proof-of-possession, and current OAuth security guidance.
Specialist38 questions · 60–90 min
Review composed security evidence
Prerequisite: Authentication, cryptography, or protocol-review experience.
Purpose: Keep channel binding, signatures, attestation, identity, and authorization as separate proofs.
After the check
Learn only as deeply as you need
Open a course to choose quizzes by topic. RFC numbers remain visible as the supporting references, not as the starting point.
FoundationSafe web and API foundationsPrerequisite: Basic web and API knowledge47 questions · 60–90 min
Keep the roles of HTTP, JSON, OAuth, TLS, and privacy distinct.
PractitionerDeployment and trust decisionsPrerequisite: Foundation-level knowledge or API security work52 questions · 75–105 min
Review JWT, metadata, TLS, proof-of-possession, and current OAuth security.
SpecialistSeparate composed security evidencePrerequisite: Authentication, cryptography, or protocol review38 questions · 60–90 min
Treat channels, signatures, attestation, identity, and authorization as distinct evidence.
Eight-stage learning mapSee how the supporting RFCs fit A2A design
RFC learning map for A2A design
RFCs for designing and reviewing communication between AI agents
A2A (Agent-to-Agent) defines how AI agents exchange requests, progress, and results. An implementation also needs sound decisions about HTTP, authentication and authorization, peer verification, replay, and privacy. This page organizes the supporting RFCs into an eight-stage learning path.
What you can verify with this guide
- How to retrieve and update an Agent Card, the public description of an agent's endpoint and capabilities
- How to verify that a request reaches the intended agent and that the agent has authority for the requested operation
- How to review failures involving replay, connection changes, streaming, logging, and privacy
How this guide differs from the official A2A specification
This page is not a replacement for the A2A specification. It teaches the RFC-based design decisions needed during implementation and review.
- A2A 1.0, JSON-RPC 2.0, Server-Sent Events, gRPC, and Protocol Buffers are not RFCs, so read the official A2A specification alongside this guide.
- RFC 9457 is general HTTP API error guidance; it is not A2A 1.0's normative error-body format.
- Agents Secure Binding is a related draft, not a normative requirement of A2A 1.0.
Eight-stage learning path
Named by A2A 1.0
Normative reference in related draft
Informative reference in related draft
Open quiz
Quiz not yet available
Review guidance
Browse every RFC quizSearch by number, title, or keyword
Pick a quiz (English or Japanese). Use search to filter by RFC number, title, or keyword.
0