# Arcadian Infracom

**Canonical:** https://apis.io/providers/arcadian-infracom/  
**Website:** https://arcadianinfra.com/  
**APIs profiled:** 1

Arcadian Infracom, founded in 2018 and headquartered in St. Louis, Missouri, builds diverse, long‑haul fiber routes to bridge the digital divide. The company develops, constructs, and operates information infrastructure, connecting major data centers and providing low‑cost backhaul to rural and tribal communities across the United States. Its mission is to lay the foundation for next‑generation digital services, supporting hyperscalers, content providers, and underserved regions.

## Kin Score — 11.3 / 100 (emerging)

Scored 2026-10-23 under rubric 0.25.0. Trend: flat (+0.0 from 11.3).

| Facet | Score |
|---|---|
| Discoverability | 53.6 |
| Contract Quality | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 9.5 |
| Access Clarity | 21.1 |

Regulatory layer — **Horizontal (data, software, accessibility, platform)**: 13.7 (matched via fallback).

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |
| Delegated Identity | no |
| Protected Resource Metadata | no |
| Dynamic Client Registration | no |
| Agentic Commerce | no |
| Pagination Ratio | na |
| Operation Distinctiveness | na |

## APIs (1)

- **Arcadian Infracom API** — Arcadian Infracom | Who We Are

## Security (1)

- **Arcadian Infracom Domain Security** — TLSv1.3 · DMARC

## Tags

Infrastructure, Fiber, Broadband, Rural Connectivity, St. Louis

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/arcadian-infracom/). Scores are computed from the provider's own public artifacts under a published rubric.
