CAMARA
Providers using this tag (38)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 8 Solid coverage with minor gaps
Developing 11 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 6 Early or largely undocumented
APIs with this tag (59)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Exemplar 1 Complete, well-documented, and agent-ready
Strong 11 Solid coverage with minor gaps
Developing 22 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 7 Early or largely undocumented
Minimal 12 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 38 providers in the APIs.io catalog tagged CAMARA, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 41.6 | 17.9 | +23.7 | 38 |
| Contract Quality | 37 | 17.5 | +19.5 | 38 |
| Operational Transparency | 26.2 | 11.3 | +14.9 | 38 |
| Contract Governance | 16.9 | 6.4 | +10.5 | 38 |
| Discoverability | 70.5 | 60.4 | +10.1 | 38 |
| Access Clarity | 28.9 | 22.3 | +6.6 | 38 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 47% | 16% | +31 |
| MCP server (first-party) | 18% | 7% | +11 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 39% | 9% | +30 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 8% | 13% | -5 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Infobip 71
- 2 Nokia Network as Code 65.7
- 3 KPN 61.9
- 4 GSMA 59.8
- 5 América Móvil 59.6
- 6 ETSI 58.4
- 7 Reliance Jio 58.4
- 8 TELUS 55.7
- 9 Telia Company 55.2
- 10 MEF 54
- 1 Telia Company 48.1
- 2 ETSI 47.9
- 3 Infobip 47.7
- 4 SK Telecom 43.7
- 5 Nokia Network as Code 43
- 6 GSMA 42.2
- 7 KPN 40.8
- 8 GSMA Open Gateway 39.5
- 9 AT&T 37.3
- 10 Netcracker 36.8
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/camara"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/camara"
curl "https://apis.io/api/v1/cohorts/tag/camara/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.