Access the FedRAMP Marketplace at marketplace.fedramp.gov; for programmatic use, use the JSON data export endpoint or download the marketplace data file from the GSA/marketplace-fedramp-gov-data GitHub repository.
Parse the JSON export to build a lookup indexed by CSO (Cloud Service Offering) name and provider name; key fields include authorization_status (Authorized, In Process, Ready), the authorizing agency, and the impact level (Low, Moderate, High).
Automate periodic refresh of the data (recommended: daily or weekly) since FedRAMP authorization statuses change as new services are authorized or as existing authorizations are revoked or expire.
Integrate the lookup into your vendor procurement or third-party risk management workflow: before issuing an ATO for a cloud service, confirm the service appears with FedRAMP Authorized status at the required impact level.
Cross-reference the marketplace status with the specific agency ATO requirement: FedRAMP authorization is necessary but not sufficient — each agency must still issue its own ATO based on the package on file.
Alert on any vendor in your active portfolio whose marketplace status changes from Authorized to In Process or is removed entirely, as this may indicate a lapsed authorization requiring immediate risk management action.
Known gotchas
FedRAMP Marketplace listing as Authorized confirms a security package exists and was reviewed; it does not confirm the package is current, that the CSP has remediated all open POA&M items, or that the specific configuration you are deploying matches the authorized boundary.
The marketplace data export JSON schema is not versioned with a formal API contract; field names or structure may change with marketplace updates — add schema validation and alerting to your ingestion pipeline.
FedRAMP does not grant ATOs; an authorized marketplace status only enables an agency to issue its own ATO more efficiently. Telling stakeholders that a service is FedRAMP-authorized as if that equates to an agency ATO is a compliance misrepresentation.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp