Federated Wireless
Federated Wireless, founded in 2012 and headquartered in Arlington, Virginia, is a shared- and unlicensed-spectrum coordination company. It is one of the FCC-certified CBRS Spectrum Access System (SAS) administrators for the 3.5 GHz band, operates a nationwide Environmental Sensing Capability (ESC) network, and is one of the seven 6 GHz Automated Frequency Coordination (AFC) systems the FCC Office of Engineering and Technology approved for commercial operation in February 2024. Its cloud-native platform — the Spectrum Controller, the Automated Network Planner (ANP) and the Spectrum AI physical-AI platform announced in June 2026 — assigns, monitors and optimizes spectrum for carriers, broadband providers, enterprises running private 5G/LTE, and government agencies. The programmable surface is real but almost entirely private: the regulated SAS-CBSD (WInnForum WINNF-TS-0016) and 6 GHz AFC device interfaces run on hosts that refuse public connections, and the Spectrum Controller's external SAS, IAM and KPI/analytics APIs are AWS API Gateway endpoints that return 403 to every anonymous request. Federated Wireless publishes no developer portal, no API reference and no machine-readable contract. The one openly discoverable agent surface is a remote Model Context Protocol server on federatedwireless.ai, advertised through RFC 8414 and RFC 9728 metadata, which fronts the company's WordPress content estate rather than its spectrum platform.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Federated Wireless the way a machine reads it — 12 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Federated Wireless scores 30.2/100 (thin), with a separate agent-readiness read of 27/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Federated Wireless ships real APIs and names them itself, but every one is behind a customer wall: the Spectrum Controller external SAS, IAM and KPI endpoints — whose base URLs the company's own public configuration.js discloses — return HTTP 403 MissingAuthenticationTokenException from AWS API Gateway, the MyFederated Zendesk help center 403s to anonymous visitors and exposes only six FAQ articles about course logins, and the regulated SAS-CBSD and 6 GHz AFC hosts resolve to company AWS infrastructure that refuses TCP 443 from the public internet. There is no developer portal, no docs subdomain and no machine-readable contract anywhere public.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Federated Wireless's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://spectrum-api.federatedwireless.com/v1→ HTTP 403https://spectrum-kpi.federatedwireless.com/v2.0→ HTTP 403https://myfederated.federatedwireless.com/hc/en-us→ HTTP 403https://federatedwireless.ai/openapi.json→ HTTP 404https://federatedwireless.ai/.well-known/oauth-protected-resource→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Federated Wireless's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/federated-wireless/"
title="Federated Wireless on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/federated-wireless.svg"
alt="Federated Wireless Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/federated-wireless/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/federated-wireless/"
title="Federated Wireless on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/federated-wireless/card.svg"
alt="Federated Wireless Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Federated Wireless
Each block below is one kind of artifact we hold for Federated Wireless. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Spectrum Controller External SAS API
The external API of the Federated Wireless Spectrum Controller, the cloud platform that manages CBRS spectrum assignment, CBSD lifecycle, monitoring and compliance. The Spectrum...
Spectrum IAM API
The identity and access-management service behind the Federated Wireless Spectrum Controller, called by the web application as IAM_BASE_URL. It backs account administration and ...
Spectrum KPI Analytics and Reporting API
The analytics and reporting service behind the Spectrum Controller, called by the web application as both ANALYTICS_BASE_URL and REPORTING_BASE_URL. It backs the spectrum analyt...
SAS-CBSD Interface
The regulated Spectrum Access System to CBSD protocol interface Federated Wireless operates as an FCC-certified SAS administrator. The protocol — registration, spectrum inquiry,...
6 GHz AFC Device Interface
The Automated Frequency Coordination system interface Federated Wireless operates for the 6 GHz band. On 2024-02-23 the FCC Office of Engineering and Technology approved seven A...
Federated Wireless MCP Server
A remote Model Context Protocol server published on federatedwireless.ai, advertised through RFC 8414 OAuth authorization-server metadata and RFC 9728 protected-resource metadat...
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
federated-wireless-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Federated Wireless Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Federated Wireless — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/federated-wireless · machine-readable index on apis.io
This is an independent, third-party profile of Federated Wireless, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.