Pricing overview

REFUGE Restrooms operates on a completely free pricing model, offering its API services without any direct costs to developers or organizations. This approach aligns with the project's foundational mission to provide a vital, accessible resource for marginalized communities, particularly transgender, intersex, and gender non-conforming individuals, along with persons with disabilities seeking safe restroom facilities. The project is sustained by donations and volunteer efforts, making the data and API endpoints available as a public good rather than a commercial offering. There are no premium features, paid tiers, or usage-based fees associated with accessing the REFUGE Restrooms API.

The absence of a pricing structure means that developers can integrate the restroom directory into their applications, websites, or services without financial barriers. This includes accessing data for location-based searches, filtering by accessibility and gender-neutrality, and contributing new restroom listings. The project emphasizes community contribution and open access, contrasting with typical commercial API providers that often implement complex tiered pricing based on request volume, data usage, or feature sets. For a detailed reference on API capabilities, consult the REFUGE Restrooms API documentation.

Plans and tiers

REFUGE Restrooms does not offer traditional pricing plans or tiers. All users receive the same level of API access and functionality. This single-tier model simplifies integration for developers, as there is no need to consider different subscription levels, feature limitations, or potential cost escalations based on usage. The API provides endpoints for searching restrooms by location (latitude and longitude), retrieving individual restroom details, and filtering results based on criteria such as gender-neutrality, accessibility, and user-submitted verification status. The design objective is maximal availability and utility for its specific social impact purpose.

Unlike commercial APIs where different tiers might gate advanced features like batch processing, higher request limits, or dedicated support, REFUGE Restrooms provides its full suite of capabilities uniformly. This also means that there are no enterprise-level agreements or custom pricing options; the service is consistently free for all users, whether an individual developer building a small personal project or a non-profit organization integrating the data into a larger community resource platform. The operational costs are covered through donations, volunteer work, and grants, ensuring the service remains freely accessible to support its social mission.

REFUGE Restrooms API Access Comparison
Plan/Tier Price Key Features & Limits Best For
Standard Access Free
  • Full API access to restroom data
  • Search by location, filter by attributes
  • Contribute new listings
  • Community-driven data updates
  • Rate limiting enforced (unspecified, but common for free APIs)
  • Transgender and gender non-conforming individuals
  • Community resource applications
  • Advocacy projects
  • Developers integrating public service data

Free tier and limits

The entire REFUGE Restrooms API operates as a comprehensive free tier. There are no paid upgrades or premium features. Developers gain full access to the crowdsourced database of restrooms, including their locations, accessibility details, and gender-neutral status. This includes the ability to perform geographic searches, filter results, and view details for specific restroom facilities. The API responds with JSON data, which is standard for modern RESTful services, making it straightforward for developers to parse and integrate into various programming environments.

While the service is free, there are implied operational limits common to most publicly available APIs, even those without explicit pricing. These limits are primarily related to rate limiting to prevent abuse and ensure service availability for all users. The REFUGE Restrooms API documentation does not specify exact rate limits (e.g., requests per second or per hour), but developers should anticipate and implement sensible request pacing in their applications. Exceeding an unstated rate limit might result in temporary IP blocking or error responses, a common practice to maintain service stability for community resources. Best practices for API consumption, such as implementing exponential backoff for retries and caching results where appropriate, are recommended to ensure reliable access and minimize strain on the service, irrespective of explicit rate limits.

The project relies on community contributions for data updates and moderation. While developers can access the data freely, contributing new restroom listings or updates typically involves interaction with the main web application or specific API endpoints designed for submission, which are also part of the free offering. The emphasis is on collective responsibility for maintaining the quality and currency of the data.

Real-world cost examples

Given the free nature of the REFUGE Restrooms API, the direct cost for using the service is consistently zero, regardless of the scale of implementation or the number of requests made (within reasonable rate limits). However, developers should account for other potential costs inherent in building and deploying any application that consumes an API.

  • Small Application (e.g., personal project, local guide): A developer integrating REFUGE Restrooms data into a small mobile app for a local community would incur no direct API costs. Their primary expenses would be for application development tools, hosting for the application itself (e.g., Firebase, Netlify, or AWS Amplify for a static site), and potentially other mapping APIs (like Google Maps or Mapbox) if a visual map is required. For instance, displaying 100 restroom locations on a map for 1,000 monthly active users would mean zero cost for the restroom data itself.
  • Medium-Sized Application (e.g., non-profit resource directory): A non-profit organization building a larger web portal to consolidate various community resources, including safe restroom locations, would also face no direct REFUGE Restrooms API charges. Their costs would primarily stem from server infrastructure (e.g., AWS Free Tier or similar cloud provider), database hosting (if managing user data), and development team salaries. If the portal serves 10,000 unique visitors monthly, each making several API calls to find restrooms, the REFUGE Restrooms component remains free, allowing the organization to allocate its budget to other operational needs.
  • Large-Scale Integration (e.g., national advocacy platform): Even a national advocacy group incorporating REFUGE Restrooms data into a platform serving hundreds of thousands of users would find the API to be free. Their significant costs would revolve around high-availability hosting, content delivery networks (CDNs), extensive development and maintenance, and potentially premium support for other integrated services (e.g., Twilio for SMS notifications, Salesforce for CRM). The REFUGE Restrooms API serves as a foundational, zero-cost data layer for such initiatives, enabling them to focus resources on user experience and outreach rather than data acquisition fees.

In all these scenarios, the financial implication of using REFUGE Restrooms specifically is negligible. The project's commitment to open access removes a common variable cost for developers, allowing projects with social impact goals to allocate resources to development, infrastructure, and user engagement rather than API licensing.

How the pricing compares

Comparing REFUGE Restrooms's pricing model to commercial alternatives highlights its distinct positioning as a public service API. Most mapping and location-based APIs, such as Google Maps Platform, HERE Technologies, or Mapbox, operate on consumption-based pricing models. These models typically charge per map load, geocoding request, routing calculation, or specific API call, often with a free tier that limits usage before charges apply.

  • Google Maps Platform: Offers a free tier with a monthly credit, but usage beyond this credit incurs charges based on specific SKU consumption (e.g., Dynamic Maps, Geocoding API, Places API). Costs can scale significantly with high usage, requiring developers to monitor API calls and optimize usage to stay within budget. For example, the Google Maps Embed API usage and billing documentation details these consumption metrics.
  • Mapbox: Provides a free tier for a certain number of map loads and API requests, with subsequent usage billed monthly. Mapbox's flexible API access involves costs for map displays, geocoding, and other services, as outlined in their Mapbox billing documentation.
  • Here Technologies: Also employs a freemium model, offering a set number of transactions within a free plan before moving to paid tiers that charge per transaction or data unit.

In contrast, REFUGE Restrooms has no direct charges, no tiers, and no consumption-based billing. This fundamental difference means that projects integrating REFUGE Restrooms data do not need to factor in escalating API costs as their user base grows. While commercial alternatives offer broader geographic coverage, more detailed mapping features, and often dedicated enterprise support, REFUGE Restrooms's unique value proposition is its specific, socially-driven dataset provided entirely free of charge. For developers whose primary need is access to safe, gender-neutral, and accessible restroom data, the REFUGE Restrooms API eliminates a significant financial barrier compared to using commercial mapping services for a similar purpose or trying to build such a dataset from scratch through paid data acquisition.