Shipvane · 4 AE roles
Marco E. · joined Cargolio
Fleetora · first roles in DEJSON alternatives_
As of 4 November 2026, 39 api specs data formats are named by companies instead of JSON: XML by 5,264 companies, Model Context Protocol by 4,892, GraphQL by 4,089.
As of 4 November 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.
- JSON, companies in postings
- 6,396
- Most used alternative
- XML · 5,264
- Fastest hiring, 90 days
- Model Context Protocol
- Alternatives ranked
- 39
- Catalogue
- T-1.0.1-prov
api specs data formats companies choose instead of JSON
Companies naming each tool in their own postings, and postings in the last 90 days. Bars are relative to the category leader.
| # | Alternative | Companies | companies | vs JSON | postings, 90 d | Compare |
|---|---|---|---|---|---|---|
| 1 | XMLW3C | 5,264 | 82% | 12,841 | JSON vs XML → | |
| 2 | Model Context ProtocolAnthropic | 4,892 | 76% | 16,002 | JSON vs Model Context Protocol → | |
| 3 | GraphQLGraphQL Foundation | 4,089 | 64% | 12,076 | JSON vs GraphQL → | |
| 4 | SOAPW3C | 3,661 | 57% | 10,243 | JSON vs SOAP → | |
| 5 | gRPCCloud Native Computing Foundation | 1,753 | 27% | 4,571 | JSON vs gRPC → | |
| 6 | OpenAPIOpenAPI Initiative | 1,432 | 22% | 3,245 | JSON vs OpenAPI → | |
| 7 | YAMLYAML Language Development Team | 1,029 | 16% | 2,569 | JSON vs YAML → | |
| 8 | Microsoft GraphMicrosoft | 942 | 15% | 2,115 | JSON vs Microsoft Graph → | |
| 9 | ODataOASIS | 844 | 13% | 3,073 | JSON vs OData → | |
| 10 | XSLTW3C | 820 | 13% | 1,501 | JSON vs XSLT → | |
| 11 | CSVIETF | 782 | 12% | 1,180 | JSON vs CSV → | |
| 12 | SAP IDocSAP | 722 | 11% | 2,746 | JSON vs SAP IDoc → | |
| 13 | Apache ParquetApache Software Foundation | 690 | 11% | 1,246 | JSON vs Apache Parquet → | |
| 14 | Protocol BuffersGoogle | 566 | 9% | 1,102 | JSON vs Protocol Buffers → | |
| 15 | Agent2Agent (A2A) ProtocolLinux Foundation | 443 | 7% | 1,572 | JSON vs Agent2Agent (A2A) Protocol → | |
| 16 | PDFAdobe | 405 | 6% | 839 | JSON vs PDF → | |
| 17 | ANSI X12ASC X12 | 371 | 6% | 761 | JSON vs ANSI X12 → | |
| 18 | 337 | 5% | 585 | JSON vs Markdown → | ||
| 19 | 291 | 5% | 551 | JSON vs XML Schema (XSD) → | ||
| 20 | Apache AvroApache Software Foundation | 280 | 4% | 560 | JSON vs Apache Avro → | |
| 21 | ISO 20022ISO | 272 | 4% | 763 | JSON vs ISO 20022 → | |
| 22 | WSDLW3C | 256 | 4% | 511 | JSON vs WSDL → | |
| 23 | UN/EDIFACTUnited Nations | 253 | 4% | 406 | JSON vs UN/EDIFACT → | |
| 24 | RDFW3C | 221 | 3% | 813 | JSON vs RDF → | |
| 25 | 216 | 3% | 703 | JSON vs Web Ontology Language → | ||
| 26 | JSON SchemaJSON Schema organization | 169 | 3% | 301 | JSON vs JSON Schema → | |
| 27 | H.264ITU-T / ISO | 160 | 3% | 327 | JSON vs H.264 → | |
| 28 | XBRLXBRL International | 152 | 2% | 294 | JSON vs XBRL → | |
| 29 | RedfishDMTF | 137 | 2% | 661 | JSON vs Redfish → | |
| 30 | H.265ITU-T | 126 | 2% | 244 | soon | |
| 31 | RSSRSS Advisory Board | 122 | 2% | 321 | soon | |
| 32 | Apache ORCApache Software Foundation | 118 | 2% | 235 | soon | |
| 33 | tRPCtRPC contributors | 106 | 2% | 188 | soon | |
| 34 | RAMLMuleSoft | 105 | 2% | 187 | soon | |
| 35 | Schema.orgSchema.org | 103 | 2% | 148 | soon | |
| 36 | JSON-LDW3C | 99 | 2% | 146 | soon | |
| 37 | DITAOASIS | 96 | 2% | 197 | soon | |
| 38 | YANGIETF | 89 | 1% | 286 | soon | |
| 39 | OpenUSDAlliance for OpenUSD | 88 | 1% | 291 | soon |
Filter on any of them, or on JSON users who also name an alternative, and open the person who owns the stack.
Free plan: 1,000 records, no card. The first 20 are above; e-mails are verified at the mail server when you open them.
Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.
39 api specs data formats are named by companies instead of JSON: XML by 5,264 companies, Model Context Protocol by 4,892, GraphQL by 4,089, measured from their own job postings. (Breaknorm, 4 November 2026, https://breaknorm.co/tools/json/alternatives)
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 →
- RankingCompanies whose own postings name the tool as the team's system, from the Breaknorm technology catalogue T-1.0.1-prov. Editions are folded into their parent product.
- 90-day postingsOpen postings first seen or posted in the last 90 days that name the tool.
- Not includedRatings, prices, feature claims, sponsored positions.
JSON alternatives: questions
What is the most used alternative to JSON?
XML: 5,264 companies name it in their own job postings, against 6,396 for JSON.
How is this list ranked?
By the number of companies whose own postings name the tool as the team's system (Breaknorm technology catalogue T-1.0.1-prov), then by postings in the last 90 days. No ratings, no vendor input, no sponsored positions.
Does this say which is better?
No. It says who uses what, by company size, industry and country, so you can see which tools companies like yours choose. For features and prices, read the vendors.
Can I get the companies on any of these?
Yes: click the tool, see the first 20 companies, and sign up for the full list with verified e-mails. Counting is free.
Get these companies 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 JSON
or on what replaces it
Connect the MCP server, filter on any tool, and get 1,000 records free.