The CAMARA Standard

About this paper

CAMARA is the only sector-wide API standard I have scored that an industry built for itself with nobody forcing it. Banking got open APIs because legislators demanded them. Healthcare got FHIR because compliance required it. Telecom decided on its own — and the GSMA’s own Head of Future Networks told me why, plainly: OneAPI was a spectacular failure, and this time the industry stopped writing specifications as documentation and started writing them as code.

The form was right. This report is about the distance between the specification and the endpoint. Ninety-three repositories in which nothing has graduated. Every server declaration a template variable. Twenty-six operators signed up and exactly one publishing a contract you can actually call. And a coalition of 1,369 people from 487 organizations doing genuinely good work behind all of it.

What's inside

1. Executive summary — the ratio that frames everything
2. What CAMARA is, and what it is not
3. The origin — 'this is not our first rodeo'
4. What the body publishes — 93 repositories, 8 categories, 64 APIs
5. The maturity ladder — a stage with nothing in it
6. The coalition — who staffs it, who steers it, who does the work
7. The adoption gap — category by category
8. Conformance — a programme whose results a machine cannot read
9. The regulatory layer — five regimes, none compelling
10. The scoring caveat — why 27.9 is the wrong instrument
11. What would have to be true
12. The investable thesis
13. Where this is going

What you get for $500.00