Breaknorm
Sign inStart free

Product

SignalsPeopleCompaniesLocal businessesMCP and API

Plays

Post engagersTeam build-outChampion movedHiring surgeNewly fundedLookalikesAll plays

Data

Coverage by countryHiring dataJob changesEmail verificationCompanies by toolWho is hiringMarket mapsOutboundCompany profilesCompare
PricingDatasetsDocsSign in
Compare · api specs data formats

Agent2Agent (A2A) Protocol VS JSON

As of 30 October 2026, JSON is named by 4,803 companies and Agent2Agent (A2A) Protocol by 340; Agent2Agent (A2A) Protocol skews to companies under 200 people (25% vs 48%), JSON to companies over 1,000 (28% vs 55%).

As of 30 October 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.

The website-and-DNS footprint is not comparable between a marketing suite and a CRM: Agent2Agent (A2A) Protocol's script and mail records show on hundreds of thousands of small sites, JSON rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.

Agent2Agent (A2A) Protocol: 2–200 employees
25%
JSON: 2–200 employees
48%
Agent2Agent (A2A) Protocol: 1,000+ employees
55%
JSON: 1,000+ employees
28%
Postings per company, 90 days
3.5 · 3.5
Website or DNS footprint
0 · 0
340companies name Agent2Agent (A2A) Protocol
4,803companies name JSON
34name both
1,194 · 16,649postings in 90 days, Agent2Agent (A2A) Protocol · JSON
02Side by side

Who chooses which

Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.

By company size
SegmentAgent2Agent (A2A) ProtocolshareJSONshareLeans
Self-employed21%441%even
2-10 employees154%3016%even
11-50 employees216%93219%JSON
51-200 employees4914%1,09223%JSON
201-500 employees288%63413%JSON
501-1000 employees3711%46310%even
1001-5000 employees7221%73115%Agent2Agent (A2A) Protocol
5001-10000 employees309%2014%Agent2Agent (A2A) Protocol
10,001+ employees8625%4058%Agent2Agent (A2A) Protocol
By industry
SegmentAgent2Agent (A2A) ProtocolshareJSONshareLeans
Technology & software16950%2,41050%even
Business & finance services6720%98921%even
Manufacturing & industry4112%4429%Agent2Agent (A2A) Protocol
Media & content154%1192%even
Utilities & infrastructure113%1152%even
Commerce & trade93%1363%even
Public, community & associations82%1112%even
Health care62%882%even
Property & construction62%902%even
Consumer services & leisure51%1152%even
Transport, logistics & rental21%862%even
Automotive10%521%even
By country
SegmentAgent2Agent (A2A) ProtocolshareJSONshareLeans
United States22165%2,74857%Agent2Agent (A2A) Protocol
United Kingdom299%3247%even
Germany175%2716%even
France124%1343%even
Canada113%1413%even
Spain51%571%even
India51%2766%JSON
Netherlands41%691%even
Portugal41%––outside top 12
Singapore41%––outside top 12
Australia31%832%even
Austria21%––outside top 12
Italy––561%outside top 12
Poland––551%outside top 12
Switzerland––511%outside top 12
Postings by team (share of each tool's postings)
SegmentAgent2Agent (A2A) ProtocolshareJSONshareLeans
Data & AI62841%1,7837%Agent2Agent (A2A) Protocol
Software engineering24216%10,47143%JSON
IT operations & business systems15310%2,37610%even
Product, program & project management483%5152%even
Unclassified372%1771%even
Sales242%6163%even
General management & consulting101%––outside top 12
Engineering (non-software)91%5672%even
Business development & strategy81%––outside top 12
Finance & accounting70%2251%even
Customer service & success60%3261%even
Construction and civil30%––outside top 12
Quality, safety & environment––2111%outside top 12
Marketing & communications––1741%outside top 12
Skilled trades and field service––1361%outside top 12
Cite this

Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.

JSON is named by 4,803 companies in job postings and Agent2Agent (A2A) Protocol by 340; 34 name both. (Breaknorm, 30 October 2026, https://breaknorm.co/compare/a2a-protocol-vs-json)
How we know

Read from the source, not self-reported

Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →

  • Job postingsRead hourly from career sites. A tool counts when the employer's own text names it as the team's system; both tools can count for one company.
  • Website and DNSScripts and embeds on the company's pages, plus SPF, DKIM, MX and CNAME records of its domain that point at the vendor.
  • SegmentsCountry, size and industry from the company profile built from its website.
  • Not a reviewNo ratings, prices or feature claims. For those, read the vendors.
FAQ

Agent2Agent (A2A) Protocol vs JSON: questions

Which is more used, Agent2Agent (A2A) Protocol or JSON?

By companies naming it in their own job postings, JSON (4,803) over Agent2Agent (A2A) Protocol (340). By website-and-DNS footprint, JSON (0 vs 0), because its scripts and mail records sit on many small company sites.

Who chooses Agent2Agent (A2A) Protocol?

25% of Agent2Agent (A2A) Protocol companies have 2 to 200 employees, against 48% for JSON. 55% of Agent2Agent (A2A) Protocol companies have over 1,000 employees, against 28% for JSON.

Do companies run both?

34 companies name both in their postings, usually Agent2Agent (A2A) Protocol in marketing and JSON in sales, or during a migration.

Where do these numbers come from?

From the employer's own text in job postings read hourly from career sites, and from scripts found on company websites in our crawl. No vendor data, no surveys.

Companies and people

Get either list your way

The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.

Every company on either tool,
with the person who owns it

Filter on Agent2Agent (A2A) Protocol or JSON. Start free, no card.

  1. 01Sign up, no card
  2. 02Connect Claude, ChatGPT or an API key
  3. 03Ask for your market