generated: '2026-08-12' method: searched source: >- https://federatedwireless.ai/services-definition/ + https://federatedwireless.ai/products/6ghz/ + FCC OET public notices + live probes description: >- Federated Wireless is a regulated spectrum-coordination operator, so its meaningful conformance is to radio-regulatory and Wireless Innovation Forum (WInnForum) specifications rather than to web-API standards. It is one of the FCC-certified CBRS Spectrum Access System administrators and one of the seven 6 GHz Automated Frequency Coordination systems the FCC Office of Engineering and Technology approved for commercial operation in February 2024. Against web-API standards the posture is thin: the only conformant surfaces are the OAuth 2.1 / RFC 8414 / RFC 9728 metadata documents that front the MCP server, and there is no OpenAPI, AsyncAPI, GraphQL, JSON:API or RFC 9457 surface anywhere public to assess. standards: - id: fcc-part-96 name: FCC 47 CFR Part 96 — Citizens Broadband Radio Service conforms: true evidence: >- Federated Wireless is an FCC-certified CBRS Spectrum Access System administrator; the company's own Services Definition page states compliance with FCC Part 96 and WINNF specifications. source: https://federatedwireless.ai/services-definition/ - id: winnf-ts-0016-sas-cbsd name: WInnForum WINNF-TS-0016 — SAS to CBSD Technical Specification conforms: true evidence: >- Operating a certified SAS requires implementing the SAS-CBSD protocol (registration, spectrum inquiry, grant, heartbeat, relinquishment, deregistration). Federated Wireless markets a "Deregistration API" — a named operation from this protocol — on its CBRS product page, and states its platform "works with any CBSD". The company runs sas.federatedwireless.com for it. source: https://federatedwireless.ai/products/cbrs/ note: >- Conformance is asserted from the FCC certification and the company's own claims. The interface itself refuses connections from the public internet, so it was NOT independently verified here. - id: winnf-afc-system-device-interface name: WInnForum AFC System to AFC Device Interface (6 GHz) conforms: true evidence: >- On 2024-02-23 the FCC OET announced approval of seven 6 GHz band AFC systems for commercial operation, Federated Wireless, Inc. among them, covering U-NII-5 (5.925–6.425 GHz) and U-NII-7 (6.525–6.875 GHz) for standard-power access points and fixed clients. Approval required passing the WInnForum/Wi-Fi Alliance test vectors reviewed by OET. source: https://www.fcc.gov/document/oet-announces-approval-seven-6-ghz-band-afc-systems - id: oauth2 name: OAuth 2.1 authorization code with PKCE conforms: true evidence: >- federatedwireless.ai advertises authorization_code + refresh_token grants, response_type code, and code_challenge_methods_supported ["S256"] with public clients. source: https://federatedwireless.ai/.well-known/oauth-authorization-server - id: rfc8414-oauth-as-metadata name: RFC 8414 — OAuth 2.0 Authorization Server Metadata conforms: true evidence: A valid JSON metadata document is served at /.well-known/oauth-authorization-server (HTTP 200). source: https://federatedwireless.ai/.well-known/oauth-authorization-server - id: rfc9728-oauth-protected-resource-metadata name: RFC 9728 — OAuth 2.0 Protected Resource Metadata conforms: true evidence: >- A valid protected-resource document is served at /.well-known/oauth-protected-resource, and the MCP endpoint returns a spec-correct 401 challenge carrying www-authenticate: Bearer realm=... resource_metadata=... source: https://federatedwireless.ai/.well-known/oauth-protected-resource - id: mcp name: Model Context Protocol conforms: true evidence: >- A live MCP server over HTTP/JSON-RPC 2.0 at https://federatedwireless.ai/wp-json/mcp/mcp-oauth-server, discoverable via RFC 9728 metadata. tools/list is auth-gated (401), so protocol-version conformance was not assessed. source: mcp/federated-wireless-mcp.yml - id: llms-txt name: llms.txt conforms: true evidence: >- https://federatedwireless.ai/llms.txt returns HTTP 200 text/plain, 92,643 bytes, generated by All in One SEO v5.0.0.1. It is a sitemap-shaped link index of posts, pages and categories — machine-readable, but it documents the marketing site, not an API. source: llms/federated-wireless-llms.txt - id: openapi conforms: false evidence: >- No OpenAPI or Swagger document was found. Probed /openapi.json, /openapi.yaml, /swagger.json, /v1/openapi.json, /api-docs, /redoc and /swagger-ui.html against federatedwireless.ai, federatedwireless.com, spectrum.federatedwireless.com and all three spectrum-{api,iam,kpi}.federatedwireless.com API Gateway hosts. Results were 404, HTML soft-200, or 403 MissingAuthenticationTokenException. - id: asyncapi conforms: false evidence: No AsyncAPI document, event catalog or webhook reference is published on any host. - id: graphql conforms: false evidence: No /graphql endpoint was found on any Federated Wireless host. - id: rfc9457-problem-details conforms: false evidence: >- No application/problem+json was observed. The API Gateway hosts return the AWS default {"message": "Missing Authentication Token"} envelope; the MCP server returns the WordPress REST {"code":..., "message":..., "data":{"status":...}} envelope. - id: rfc9116-security-txt conforms: false evidence: /.well-known/security.txt returns 404 on federatedwireless.ai and is a soft-200 elsewhere. - id: rfc9727-api-catalog conforms: false evidence: /.well-known/api-catalog returns 404 on federatedwireless.ai. - id: a2a conforms: false evidence: >- Both /.well-known/agent-card.json and the legacy /.well-known/agent.json were probed on every host; no valid agent card was returned. - id: fedramp conforms: unknown evidence: >- Federated Wireless sells a Government Solutions line and its page discusses Risk Management Framework (RMF) and Authority to Operate (ATO), but names no FedRAMP, DoD IL, SOC 2 or ISO 27001 authorization. No trust center, compliance page or certification listing was found on any host, so no compliance program is recorded and no `Compliance` pointer is emitted. source: https://federatedwireless.ai/products/gov/ x-evidence: fetched: '2026-08-12' probes: - url: https://federatedwireless.ai/.well-known/oauth-authorization-server status: 200 - url: https://federatedwireless.ai/llms.txt status: 200 - url: https://federatedwireless.ai/openapi.json status: 404 - url: https://spectrum-api.federatedwireless.com/openapi.json status: 403 - url: https://federatedwireless.ai/services-definition/ status: 200 - url: https://federatedwireless.ai/products/gov/ status: 200