diff --git a/api-keys-rate-limits.md b/api-keys-rate-limits.md
index 13a1382..24890d3 100644
--- a/api-keys-rate-limits.md
+++ b/api-keys-rate-limits.md
@@ -1,10 +1,12 @@
 # API keys and rate limits
 
+_Note: This page is deprecated and has been removed from the documentation on https://mapzen.com/ as of May 2017. For more information, see the [Mapzen developer overview](https://mapzen.com/documentation/overview/)._
+
 ## Get started
 
-The Mapzen Search service requires an API key. In a request, you must append your own API key to the URL, following `&api_key=` at the end.
+The Mapzen Search service requires an API key. In a request, you must append your own API key to the URL, following `?api_key=`.
 
-See the [Mapzen developer overview](https://mapzen.com/documentation/overview/#mapzen-search) for more on API keys and rate limits.
+See the [Mapzen developer overview](https://mapzen.com/documentation/overview/) for more on API keys and rate limits.
 
 ## Caching to improve performance
 
diff --git a/http-status-codes.md b/http-status-codes.md
index f817b88..6dcc7bf 100644
--- a/http-status-codes.md
+++ b/http-status-codes.md
@@ -12,8 +12,3 @@ The following status codes are returned from the geocoding service:
 - `502 Bad Gateway`: Connection was lost to the Elasticsearch cluster.
 
 In all cases above, the response body will be valid GeoJSON.
-
-## Rate limiter
-The rate limiter returns the status codes `403 Forbidden` and `429 Too Many Requests`.
-
-See [API keys and rate limits](api-keys-rate-limits.md) for more information.